Richard Russon [Thu, 3 May 2018 12:46:51 +0000 (13:46 +0100)]
merge: upstream fixes
* Add more explanation of known vs subscribed lists to manual.
* Add ~M pattern to match mime Content-Types.
* Update pattern documentation.
* Update copyright notices.
Kevin McCarthy [Sat, 28 Apr 2018 20:21:42 +0000 (13:21 -0700)]
Update pattern documentation.
Note that ~b, ~B, ~h, ~M, and ~X read the message in, and that this
can be much slower.
Change =b, =B, =h table rows to document just the IMAP behavior. The
"=" simple string behavior is already covered below, and makes it less
obvious whether "***)" should be added to those entries in the table.
Break up the simple string and imap server-side matching explanation
into two paragraphs.
Add ~M to the list of patterns you can't use message scoring with.
Add equivalent, if briefer, explanations to the muttrc.man page.
Kevin McCarthy [Mon, 30 Apr 2018 23:17:52 +0000 (16:17 -0700)]
Add more explanation of known vs subscribed lists to manual.
Mention in both the "Mailing Lists" and "Handling Mailing Lists"
sections the difference between known and subscribed mailing lists.
Note that the Mail-Followup-To header is generated if any of the
recipients are known mailing lists. If any of those are subscribed
mailing lists, the sender's address will not be in the header. If all
of them are known (but not subscribed), the sender's address will be
added to the header.
Richard Russon [Wed, 2 May 2018 18:05:12 +0000 (19:05 +0100)]
merge: Add support for multipart/multilingual emails
* Initial support for multipart/alternative
* support for multipart/alternative and multipart/mixed
* inline parts of a multipart/alternative email
* Clear the filename of an inline part
* clean up redraw
* Implement RFC8255 - multilingual email parts
* Enable editing of multipart/multilingual mails
* remove content-language checking when composing
* add doc for multipart/{alternative,multilingual}
message.c: retry message parse if first attempt is zero-length
On IMAP failure the message body can sometimes be truncated, which
leaves an empty message in the cache that must be manually deleted
to be properly re-fetched.
If the cached message body is zero-length, retry the message parse
once to be sure that the message body actually *is* empty.
Kevin McCarthy [Thu, 19 Apr 2018 20:51:07 +0000 (13:51 -0700)]
Add $browser_abbreviate_mailboxes.
This allows '=' and '~' mailboxes shortcuts to be turned off in the
browser mailbox list.
The default $sort_browser value of "alpha" uses strcoll(3), which
ignores some punctuation. When using multiple accounts with
dynamically changing values of $folder, this can lead to an
unintuitive sorting order. (See issue #22 for an example.)
This problem came about because of commit 8328ce68, which enabled
mutt_pretty_mailbox() calls for IMAP and POP mailboxes too. The
commit had a valid point about consistency and too-wide mailbox
listings, so I don't really want to revert it.
This option provides an alternative to completely enable/disable the
shortcuts for those who run into an issue.
Austin Ray [Wed, 25 Apr 2018 10:34:04 +0000 (06:34 -0400)]
Respect environment VISUAL and EDITOR variables
* Respect environment VISUAL and EDITOR variables
Commit 0ef255e repositioned where Neomutt set its standard defaults in
init.c to after the logic for loading the VISUAL and EDITOR variables.
As a result, Neomutt overrides the values it retrieved from the
environment with the ones from the configuration file. This matches the
desired precedence of config->environment->code.
However, if `editor` is not set in the configuration file then Neomutt
does not retrieve EDITOR and VISUAL again. This results in Neomutt
falling back to the editor specified in the code. Thus the precedence is
config->code.
This commit returns the standard default set loop to its initial
location allowing for the environment variables to be usable.
Floyd Anderson [Sun, 8 Apr 2018 22:03:27 +0000 (00:03 +0200)]
doc/manual.xml.head: Remove logical NOT operator
This optional pattern operator prefix:
• should be known as negation operator, so no reason to mention it
• where important, hopefully all commands describe it, like folder-hook
• is not used on all configuration commands which support patterns and
even it has been, that would like express a positive number 42 as +42
• is curiously used for regex, which has the caret ‘^’ for negation
• may mistaken as $spoolfile mailbox shortcut
• is not special; otherwise ‘^’ prefix to match all email addresses in
a list ^) and maybe others must also mentioned in command definitions
projects / neomutt / log