New action mu4e-action-retag-message that reads tag changes from the user and
modifies the corresponding header (X-Keywords, X-Label, etc) on the message.
Now, mark commands with region on headers view,
target of the first email is reflected in the rest of email.
```
Date From Subject
--------------------------------------------
2012-12-05 Github ...
2012-12-05 Yahoo! ...
2012-12-05 Work ...
refiling to
Date From Subject
--------------------------------------------
r -> /github 2012-12-05 Github ...
r -> /github 2012-12-05 Yahoo! ...
r -> /github 2012-12-05 Work ...
```
In this patch, change target in region email.
```
Date From Subject
--------------------------------------------
r -> /github 2012-12-05 Github ...
r -> /yahoo 2012-12-05 Yahoo! ...
r -> /work 2012-12-05 Work ...
```
Autoload functions `mu4e' and `mu4e~compose-mail' and the definition of
the mail-user-agent `mu4e-user-agent'. The last to are required so
that `compose-mail' can be used without explicitly loading mu4e.
Also require `mu4e' in mu4e-compose.el (after providing mu4e-compose
to avoid a circular dependencies). This is required because the
autoload definitions only cause mu4e-compose but not mu4e to be loaded
when using `compose-mail', but if mu4e isn't loaded various handlers
are not loaded (and possibly there are other problems if mu4e is not
fully loaded).
Without this `mail-user-agent' cannot be set to `mu4e-user-agent'
through customize, as the custom type expects a function. Not sure
whether this function is actually ever used; if it is then returning
the symbol is probably the correct thing to do, as other such
functions suggest.
This allows `find-function' to find the definition. While the
definition doesn't contain much useful information jumping there
instead of the beginning of the file is still better because the macro
used to define them is defined right above.
Also remove the comments about wanting to define the commands in a
loop. One shouldn't do that; it would again make it impossible to
find the definition.
Use face `bold' for the sorted column but leave the face unspecified
for other columns. This is how tabulated-list does it to; it only
uses fixed-pitch for whitespace between columns.
The problem with using fixed-pitch is that uses "Monospace" which
might be a different monospace font than what is used for `default'.
These fonts might have a different width causing columns in the header
and the buffer not to be aligned.
Inheriting `fixed-pitch' from `default' instead of specifying the font
does not work as that causes the `fixed-pitch'ed parts of the
header-line not to be raised like the rest anymore. One (that is
every user) could also manually copy the font family from `default'.
Simply not specifying the font fixes all that.
The first sentence should summarize the variable's or function's
purpose and it should fit on the first line. Change existing
doc-string by:
* Move first sentence onto first line even if that makes it _a bit_
long.
* Move additional notes out of first sentence and add them later,
possibly as complete sentences.
* If I am uncertain whether doing the above would alter the meaning,
_don't_ do it.
* If fitting the initial sentence on the first line would require a
complete rewrite of the doc-string _don't_ do so unless it is very
easy to do.
* Remove indentation from second and later lines if it is there to
align them with the first in the source code, instead of in
`describe-*' output.
* Make "pullet point" lists a bit more consistent.
Obviously this does not fix all problems but it's a start.
This should make it more intuitive to see that actions are performed
on the region as well as the current line (which usually is not part
of the region).
djcb
Sebastian Fischmeister
Abdó Roig-Maranges
Wataru MIYAGUNI
David Pflug
Jonas Bernoulli