alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e: rework uri-handling in view, add mu4e-view-save-url

Browse Source 
Rework the handling of URIs in the view a bit; add a functionto save
URLs to the kill ring. Also add mu4e-view-for-each-uri to iterate over
them.
This commit is contained in:
djcb
2015-03-21 15:22:12 +02:00
parent 6680b364a8
commit 7de65b91bc
2 changed files with 50 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
mu4e/mu4e.texi
View File

@ -1157,6 +1157,9 @@ actions
g go to (visit) numbered URL (using `browse-url')
(or: <mouse-1> or M-RET with point on url)
C-u g visits multiple URLs
k save the numbered URL in the kill-ring.
C-u g saves multiple URLs
e extract (save) attachment (asks for number)
(or: <mouse-2> or S-RET with point on attachment)
C-u e extracts multiple attachments
@ -2529,13 +2532,17 @@ action}
@noindent
You can also write your own functions without using the above. If you
want to do so, key useful functions are @code{mu4e-message-at-point}
(see below), @code{mu4e-headers-for-each} (to iterate over all headers,
see its docstring) and @code{mu4e-view-for-each-part} (to iterate over
all parts/attachments, see its docstring). Another useful function is
(see below), @code{mu4e-headers-for-each} (to iterate over all
headers, see its docstring) and @code{mu4e-view-for-each-part} (to
iterate over all parts/attachments, see its docstring). There is also
@code{mu4e-view-for-each-uri} to iterate of all the URIs in the
current message.
Another useful function is
@code{mu4e-headers-find-if} which searches for a message matching a
certain pattern; again, see its docstring.
@node Available functions
@node Avaifmlable functions
@section Available functions
The whole of @t{mu4e} consists of hundreds of elisp functions. However, the