| Age | Commit message (Collapse) | Author |
|---|
|
Although not documented, Mutt would previously intepret a
$header_cache value ending in '/' as a directory even if it didn't
exist. The new DT_PATH normalization prevents this possibility, so a
directory will need to be created in advance.
I'm not fond of "fixing" regressions with documentation, but I believe
this is a small issue, easily worked around for first-time use, and
the benefits of the normalization are worth this small change.
|
|
Thanks for the fix from Mario Blättermann and the manpages-l10n
project.
|
|
The section number should not be part of the BR text.
Thanks to @hmartink and the manpage-l10n project for the bug report!
|
|
|
|
This will allow translators to add additional reply prefixes common to
their locale.
Add more documentation to the option, to explain the parts of the
regular expression. Give an example of adding more prefixes.
Note that the result of this is stored in the header cache. Probably
people rarely were affected by this before, but with the new
localization, people may experiment and need to be aware to turn the
header cache off while testing.
|
|
Since the values are shown as if double-quoted, backslash also needs
to be properly escaped.
|
|
Mention $forward_attribution_intro, $forward_attribution_trailer, and
$forward_format.
|
|
It turns out Cyrus SASL's license may not be compatible with GPL
programs, see Debian Bug 999672.
So, add support for the GNU SASL library, using configure option
--with-gsasl.
I haven't touched the Cyrus SASL code in Mutt all that much in the
past, but I've done my best to keep the gsasl code clean and simple.
There are likely mistakes to be fixed and additions to be made,
though.
I queried the gsasl mailing list about the need for a socket
wrapper (as is done for the cyrus code), and it seems this should no
longer be needed. As long as GSASL_QOP is left at the
default (qop-auth), the client should ask for authentication, and not
negotiate integrity or confidentiality. (Thanks to Phil Pennock and
Simon Josefsson for their reponses - although the blame is fully
on *me* if this turns out to be incorrect). Therefore there is no
CONNECTION wrapping in this implementation.
Add multiline response support for SMTP authentication (which is
probably not actually needed). Also add arbitrary line length for the
SASL server responses (the RFCs note that for SASL, the protocol line
lengths don't apply).
|
|
Step three only selects from enriched, plain, and then html; not _any_
text type.
Step four considers any text type as one that Mutt can handle
internally.
|
|
The IMAP protocol only supports unread and total counts, but the
manual had no mention of this.
|
|
The manual mistakenly said to use <select-entry>, which is not (and
never has been) supported by the code. Change it to <tag-entry>, and
note that <Space> is bound to <tag-entry> in the alias menu.
|
|
Move the "extra" keybindings added manually inside km_init() into the
keybinding tables instead.
This allows the documentation in the manual to be generated correctly.
It also corrects a small problem with duplicate OPS in the struct
binding_t table. The exec completion and unbound list in the help
menu iterated the active binding_t table and assumed each OP appears
only once. When '\n' and '\r' were both added to the binding_t table,
this broke the assumption and caused those to misbehave.
|
|
This patch is based on the patch from Mike Frysinger, archived from
the old trac system at:
https://gitlab.com/muttmua/trac-tickets/-/blob/master/attachments/3494/mutt-enter-return-hg-6658.patch
This version creates a new key symbol, <KeypadEnter> for the KEY_ENTER
value returned by getch(). According to Vincent Lefèvre's research,
that corresponds to the "key pad" Enter key. If KEY_ENTER is not
defined, it binds the symbol to "\n". It does this after the
KeyNames[] definitions of <Enter> and <Return> so they remain the
default shown by <what-key>.
Since Mutt already accepts KEY_ENTER at the y/n prompt, add it for all
the built-in operations too.
Bindings with "\r" and "\n" in the binding_t structures don't need
"<enter>" and "<return>" to be re-specified in km_init(), so remove
those. Instead add the "<KeypadEnter>" bindings there.
Remove unnecessary Alias menu bindings for OP_GENERIC_SELECT_ENTRY in
km_init().
As a note: I don't believe non-extended key symbol bindings need to be
bound inside km_init(). I'm not clear why this was done, or what
purpose it serves. I'll do a bit more research, but if I can't
uncover any issues, will move them inside the binding_t structures in
another commit.
|
|
Add to the sentence mentioning '-y'.
|
|
Currently, every variable is shown in the table of contents of the
reference manual. Variable list is over 400 items long. This makes the
ToC difficult to work with.
Removing is done by adding an overwriting template for the parent of
variables section (that is sect1 tag with id="variables"). In the
DocBook source matching template calls another template named subtoc
with two parameters: context (self element) and nodes (child
sections). Normally a list of descendant nodes is passed here, but we
don't want that and instead call subtoc with no parameters.
This approach results in semantically correct code being generated in
all modes.
Note, that the ID (variables) will have to be kept in sync with XML
generating code, but that is already hardcoded elsewhere.
|
|
|
|
|
|
Use the map tables to print out a correct default value for sort
types.
Remove the unneeded SORT_ALPHA type, for $sort_browser documentation,
since we can do the lookup now.
|
|
They aren't available in batch mode. This was mentioned in the "batch
compose flow" section, but should be mentioned a bit more prominently
in the manual.
|
|
|
|
Thanks to Gregory Anders for the ticket and suggested patch, which
this commit is based upon.
|
|
Mutt runs the file through mutt_prepare_template() in both cases,
which will decrypt, remove signatures, strip multipart/alternatives.
The documentation wasn't clear about this, and it might be
misunderstood that -H is a "pass through" option.
|
|
|
|
This mirrors the <view-pager> in the attachment menu (and just added
to the compose menu), but adds it to the compose menu for alternative
generation.
|
|
This will remove the useless link and field numbers from output in the
manual.txt.
|
|
Closes #334.
If all the html to txt programs we use (lynx, elinks, w3m) are missing
from the system, the shell redirection willl create an empty file.
Change the install step to use -s "FILE exists and has a size greater
than zero".
Thanks to Mitchell Blank Jr for the ticket and suggested fix.
|
|
Emphasize that it's not always set, for example in command-line mode,
or when evaluating the muttrc at startup.
|
|
The CurrentFolder can actually be used to resolve an fcc-hook at fcc
time. We would want to use the folder they started composing in, to
be consistent with expectations.
|
|
Previously, gettext's po/Makefile.in.in was modified to separately
scan and merge a generated file: keymap_alldefs.h. Gettext doesn't
recommend nor provide support for scanning generated files.
However, there is no reason we have to scan the generated file.
Instead move the N_() markers and L10N comments into the OPS files.
Then simply add the OPS files to po/POTFILES.in.
Add a '--language=C' option to xgettext to avoid a warning about the
OPS files not have any known language suffix.
Modify gen_defs and doc/gen-map-doc to deal with the new format of the
OPS files.
|
|
The CurrentFolder can actually be used to resolve an fcc-hook at fcc
time. We would want to use the folder they started composing in, to
be consistent with expectations.
|
|
Previously, Mutt would find the first match and use that.
However, the example shown in the manual:
hdr_order From Date: From: To: Cc: Subject:
gives the expectation that an mbox From_ line would print first, then
the Date:, and then the From: header.
Change the matcher to scan all HeaderOrderList entries and use the
longest match.
Update the documentation to make it clear From_ lines are printed out
with other "real" headers, and can be manipulated via ignore and
hdr_order commands.
|
|
Fix logic error in mutt_buffy_check().
Add -nonotify flag to the configuration command list in the manual
too.
Add line wraps to the muttrc.man mailboxes options, to make the
synopsis more readable within 80 columns.
|
|
-nonotify allows to disable notifications for mailboxes.
-notify can be used to re-enable notifications for a previously disabled
mailbox.
A typical use case are mailboxes for mailing lists. The User may want to
get notified about new mail in their work mailbox, but not get disrupted
by new mail received from the mailing list.
This patch allows individual configuration for all mailboxes.
|
|
|
|
I'll run the update tool on source files in master a bit later.
|
|
|
|
mutt uses either the Muttrc owned by the sysadmin, or its own Muttrc.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
|
|
|
|
This is based on <skip-quoted>, and is bound to 'H' by default.
I've added an error message in case there is no text past the headers,
just to cover the logical case. I don't think Mutt allows that to
happen for text passed to the pager, but just in case.
|
|
List-Post parsing is inline in the List-Post header handler. This moves
it to some separate functions so that we can use it for other purposes.
|
|
|
|
This uses a copiousoutput mailcap entry, or falls back to raw text.
The existing functions do not provide a way to use copiousoutput
mailcap entries exclusively. The default <view-attach> will use one
for internally supported types if auto_view is configured, but there
is no way to do so for other mime types (such as application/pdf).
|
|
start_debug() takes a boolean indicating whether to rotate debug
files.
The -d option allows a negative number. If negative, debug files
are not rotated. The debug level is the absolute value.
This is useful for continuously watching (e.g. tail -f) the
.muttdebug0 file.
|
|
|
|
|
|
|
|
It's a FAQ, so I think is worth emphasizing in the "getting started"
section.
|
|
|
|
"mail", incorrect function name
|
|
|
