In the keybinding defintions for mu4e-view-mode-map, the variable
mu4e-view-use-gnus was used quoted in an if condition, which means that the
condition always evaluated to true. Therefore, M-q would always be bound to
article-fill-long lines and never to mu4e-view-fill-long-lines.
Using mu4e-index-updated-hook in mu4e~start with a lambda is just like
adding the call to mu4e-info-handler so do it explicitely which is
much cleaner.
* mu4e/mu4e-utils.el (mu4e-info-handler): Always refresh main buffer.
(mu4e~start): Remove insertion of mu4e-index-updated-hook.
* mu4e/mu4e-headers.el (mu4e~headers-quit-buffer): Refresh main buffer
when done.
* mu4e/mu4e-main.el (mu4e-main-mode-map): Don't bind "g" to mu4e, "g"
should be bound to revert-buffer (special-mode).
(mu4e-main-mode): No need to specify map.
(mu4e~main-view-real-1): New.
(mu4e~main-redraw-buffer): New.
(mu4e~main-view-real): Use them.
(mu4e~main-view): Take one more arg REFRESH.
(mu4e~main-toggle-mail-sending-mode): revert-buffer when done.
Use "_" as the title of that section so that it is less distracting
when sections are collapsed to get an overview of the library.
Using a separate section is useful because it reduces the risk of
accidentally into the middle of a library.
Placing two semicolons on an otherwise empty line helps to logically
"connect" the surrounding "paragraphs", which in (only) some cases
makes sense.
Previously the three paragraphs of the permission statement were not
connected to each other like this, which is perfectly fine. However
the preceding "This file is not part of GNU Emacs." line was connected
to the first paragraph, which does not make sense considering that the
latter is not connected two the second paragraph, which it relates to
more.
Once those two semicolons are gone, it also makes sense to remove
those from the second line.
Texinfo is of the opinion that every hyperlink has to be prefixed
by either "see" or "in". If neither of these words appears there,
then it inserts "see" and it cannot be told not to do that.
This turns a correct sentence like:
> Mu4e lets you define custom actions for messages in the <Headers view>.
into:
> Mu4e lets you define custom actions for messages in the see <Headers view>.
The best compromise is
> Mu4e lets you define custom actions for messages in <Headers view>.
which isn't correct but at least less messed up.
Alternatively one could rephrase every sentence that contains a link
to circumvent Texinfo's speech impairment. Or one could replace each
link with a footnote and place the actual link in the footnote.
There already is a ".editorconfig" file for cross-editor
configuration, but most Emacs users don't use that, so this also has
to be configured the traditional Emacs way. (Also I have some doubts
that cross-editor configuration is relevant for Emacs Lisp files.)
Dirk-Jan C. Binnema
Hans-Peter Deifel
Thierry Volpiatto
Christophe Troestler
Jonas Bernoulli