| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
There is no meaningful reason to focus on individual lines, since they
are unactionable.
|
|
|
|
|
| |
This allows users to use a custom domain in automatically generated
Message-ID headers instead of the local hostname.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- allows users to use $XDG_CONFIG_HOME, as well
- stores information in single places.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the following bug:
To reproduce::
- Don't define `template_dir` in the user configuration file, such that
the default value is used.
- Run: :compose --template=foobar
Problem:
Displays error: `no template directory: $XDG_CONFIG_HOME/alot/templates`
|
|\
| |
| | |
thread mode message indentation
|
| | |
|
|/
|
|
|
| |
which will be interpreted just like 'search.exclude_tags' in the notmuch
config.
|
|\
| |
| | |
optional linewise focussing in thread mode
|
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces a new config option 'thread_focus_linewise',
(defaults to True), which determines if the message texts are
split into individually focussable lines in thread mode.
fixes #645
|
|/
|
|
|
| |
It currently lists "terminal_command" in relation to "editor_spawn" but
the config option is actually "terminal_cmd".
|
|
|
|
|
| |
There have been several people asking about text selection with the mouse
setting activated so it seems reasonable to mention it here.
|
|\
| |
| | |
Default to not handling mouse
|
| |
| |
| |
| |
| |
| | |
As discussed elsewhere, handling the mouse was not done before, and
breaks work flows that include using the mouse for other things
(middle-click paste). This only changes the default option to False.
|
|/
|
|
|
|
|
|
| |
This creates a deferred that runs on a user configurable timer and is
provided the ui. This deferred will re-fire after the number of seconds
specified by the timer are eclipsed. By default this is 300 seconds.
Fixes #522
|
|
|
|
|
|
|
|
|
|
| |
Mouse support is enabled by default. To disable mouse support, set
```
handle_mouse = False
```
in your config file.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Default value 'first_message' lists authors in the order they joined the
conversation. Value 'latest_message' order authors by their latest
message, which makes it easier to see which authors who wrote the most
recent messages.
Note that authors with duplicate emails were previously filtered. We now
keep all authors where name + email is unique. This is behavior is
desired for some email notification services. For example, Jira will
set the From header to "Joe User <jira@company.com>" meaning you will
only see one author if you only keep unique email addresses.
|
|
|
|
|
|
|
| |
Auto-detect the '--list' for you automagically when you just ':reply'
on a list, it is based on a config param that give you the control,
by default it is off, you have to setup your config file, like:
auto_replyto_mailinglist = True
|
|
|
| |
that variable is called *terminal_cmd*, not *terminal_command*
|
|
|
|
|
|
|
| |
this has been replaced long ago by setting `search.threadline.parts`
in theme-files.
cf issue #631
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
alot/commands/thread.py
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
Add a body_mimetype global configuration option to choose the default message
part to return as body in extract_body when types is None. Parts of the
preferred type will be returned if present, all text/* parts will be returned if
none parts of the preferred type exist. The default is "text/html", which should
result in the same behavior as before.
|
| |
|
| |
|
|
this is done now by either including a hidden toctree
or renaming *.rst files
|