| 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.
|
|
|
|
| |
fixes #1411
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
pep8!
Better variable names, new feature into docs.
Make sphinx documentation.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
This requires regenerating the accounts_table docs, as they've changed
for python 3.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
maildir knows R and P flags which denote messages that have been replied
to resp. passed on (fowarded, bounced). They correspond to IMAP flags
\Replied and $Forwarded which are used by many clients and by
synchronisation software. E.g., mbsync syncs \Replied to R, a patch for
P is pending.
Implement replied_tags and passed_tags for alot which work similar to
sent_tags: sent_tags tags the sent message; replied_tags (resp.
passed_tags) tags the message being replied to (resp. being fowarded).
Basically, setting the replied_tags config to `replied` and replying to
a message has the same effect as doing `tag replied; reply`, but the
latter would tag even sending the reply is aborted or fails. The
implementation in this patch makes sure that the tagging is done only if
and when the reply resp. forward has been sent successfully.
|
| |
| |
| |
| |
| | |
draft_tags works the same way as sent_tags, so provide the same defaults
and doc.
|
| |
| |
| |
| |
| |
| | |
force_list() converts single items to lists already. Thus, remove a
superfluous list() that could be mistaken for converting a single string
into a list of chars.
|
|/ |
|
|
|
|
|
| |
- 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`
|
|
|
|
|
| |
this simply renames some (sub)section titles in the configuration
docs.
|
|\
| |
| | |
thread mode message indentation
|
| | |
|
|/
|
|
|
| |
which will be interpreted just like 'search.exclude_tags' in the notmuch
config.
|
| |
|
|
|
|
|
| |
This class will encapsulate the logic of comparing email addresses and
the rules of handling when capitalization is allowed and when it's not.
|
|
|
|
|
|
| |
This fixes the example "goodbye"-hook in order to make it work again
with v0.6 and newer branches: the initializes SettingsManager
object is now accessible as 'alot.settings.const.settings'.
|
| |
|
|
|
|
| |
Mark all values for [account]encrypt_by_default as deprecated
|
|
|
|
|
| |
... which displays a prefix of the msg contents.
This feature was missing in the docs.
|
|
|
|
| |
Since the original patch that added the support didn't.
|
|
|
|
|
|
| |
Fixes #707 and #332.
Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>
|
|
|
|
| |
Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>
|
|\
| |
| | |
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
|
| |
| |
| |
| |
| | |
This is done to give more emphasis to the fact that there might be header
lines at the top of the string.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
The old regex that was suggested to capture addresses for completion from the
command `notmuch address` was bogus. The json output format is much more
predictable.
Reported in #990.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|