This commit replaces the call to `read-directory-name' by a call to
`read-file-name' when asking the user about the target location for
saving an attachment. This new dialog is better suited because:
1/ the user is currently saving a file, not a directory: he might want
to complete over existing files (e.g., to replace an existing file
with a new one just received).
2/ the current dialog was asking for a directory but then, if the user
enters a directory, mu4e proposes him to "override" the directory
with a file. This is not going to work obviously. In the new dialog,
it is also possible to enter a directory name instead of a file name.
In this case, a new file is created under the chosen directory name.
`lispdir` is no longer hardcoded in the Makefile.
Users can set the desired `lispdir` at configure time, with `./configure
--with-lispdir='...'`; or at install time with `make lispdir='...' install`.
The default install path is the folder `mu4e/` inside whatever AM_PATH_LISP
finds, which is probably what the original default intended.
This change fixes#320.
* mu4e/mu4e-view.el (mu4e-view-go-to-url): Add the ability to visit
multiple URLs by specifying a numeric range.
* mu4e/mu4e.texi (The message view: Keybindings): Document ability to
visit multiple URLs.
`mu4e-view-go-to-url' now behaves like `mu4e-view-save-attachment'. You
can specify multiple URLs to visit at once by prefixing the visit
command by <C-u>; so C-u g asks you for a range of URLs to visit (for
example, 1 3-6 8). The range "‘a’" is a shortcut for all URLs.
Apply patch is useful when you might want to change the patch. However
for reviews you may well just want stuff applied directly to the
commit history.
add-to-list does pre-pend an element to a list by default, but only if
it isn't in there already. This change ensures the path we have just
added is always the first in the list. This makes sense when applying
a series of patches by hand.
