<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs/notmuch-draft.el, branch 0.31</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.31</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.31'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-08-22T12:11:06Z</updated>
<entry>
<title>emacs: Use pop-to-buffer-same-window rather than switch-to-buffer</title>
<updated>2020-08-22T12:11:06Z</updated>
<author>
<name>Sean Whitton</name>
<email>spwhitton@spwhitton.name</email>
</author>
<published>2020-08-11T16:59:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=88ae4f02511c4dd61ea90b28794f469819d543be'/>
<id>urn:sha1:88ae4f02511c4dd61ea90b28794f469819d543be</id>
<content type='text'>
This means that notmuch commands obey display-buffer-alist so the user
can customize how buffers show up.

It also permits the use of C-x 4 4, C-x 5 5 and C-x t t, available in
Emacs 28.  For example, one can use C-x 4 4 M-x notmuch-jump-search RET
to open a saved search in another window rather than the current window.
Or in notmuch-search mode, C-x 5 5 RET to view the message at point in
a new frame.

notmuch-tree has custom buffer display logic, so bind
display-buffer-overriding-action to make pop-to-buffer-same-window
behave exactly as switch-to-buffer while that function is running.
</content>
</entry>
<entry>
<title>emacs: Use 'and' instead of 'when' when the return value matters</title>
<updated>2020-08-09T23:51:16Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dfb1b8eb89e814f4bf6f6e62b700c72aa1b4659a'/>
<id>urn:sha1:dfb1b8eb89e814f4bf6f6e62b700c72aa1b4659a</id>
<content type='text'>
Also do so for some 'if' forms that lack an ELSE part.
Even go as far as using 'and' and 'not' instead of 'unless'.
</content>
</entry>
<entry>
<title>emacs: Fix indentation</title>
<updated>2020-08-09T23:48:09Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=caaa10876046096320f4e69053542eabe17e7e55'/>
<id>urn:sha1:caaa10876046096320f4e69053542eabe17e7e55</id>
<content type='text'>
</content>
</entry>
<entry>
<title>emacs: Shorten long lines</title>
<updated>2020-08-09T22:48:36Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a4617f29ce81e7ae3e0cb747fdb9070f88407a28'/>
<id>urn:sha1:a4617f29ce81e7ae3e0cb747fdb9070f88407a28</id>
<content type='text'>
</content>
</entry>
<entry>
<title>emacs docstrings: consistent indentation, newlines, periods</title>
<updated>2020-06-06T10:55:58Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2020-05-24T19:17:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ed40579ad3882e6f9bbe9b1ba5e707ab289ca203'/>
<id>urn:sha1:ed40579ad3882e6f9bbe9b1ba5e707ab289ca203</id>
<content type='text'>
Fixed emacs docstrings to be consistent. No functional change.

- removed some (accidental) indentation
- removed some trailing newlines
- added trailing periods where missing (some exclusions)
</content>
</entry>
<entry>
<title>emacs: Use `cl-lib' instead of deprecated `cl'</title>
<updated>2020-04-27T10:36:10Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-04-25T20:18:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=11ac932a4503872c19987b843d58513c4b9ef76f'/>
<id>urn:sha1:11ac932a4503872c19987b843d58513c4b9ef76f</id>
<content type='text'>
Starting with Emacs 27 the old `cl' implementation is finally
considered obsolete.  Previously its use was strongly discouraged
at run-time but one was still allowed to use it at compile-time.

For the most part the transition is very simple and boils down to
adding the "cl-" prefix to some symbols.  A few replacements do not
follow that simple pattern; e.g. `first' is replaced with `car',
even though the alias `cl-first' exists, because the latter is not
idiomatic emacs-lisp.

In a few cases we start using `pcase-let' or `pcase-lambda' instead
of renaming e.g. `first' to `car'.  That way we can remind the reader
of the meaning of the various parts of the data that is being
deconstructed.

An obsolete `lexical-let' and a `lexical-let*' are replaced with their
regular variants `let' and `let*' even though we do not at the same
time enable `lexical-binding' for that file.  That is the right thing
to do because it does not actually make a difference in those cases
whether lexical bindings are used or not, and because this should be
enabled in a separate commit.

We need to explicitly depend on the `cl-lib' package because Emacs
24.1 and 24.2 lack that library.  When using these releases we end
up using the backport from GNU Elpa.

We need to explicitly require the `pcase' library because
`pcase-dolist' was not autoloaded until Emacs 25.1.
</content>
</entry>
<entry>
<title>emacs: make editing a message as new include FCC</title>
<updated>2019-03-31T16:20:32Z</updated>
<author>
<name>Léo Gaspard</name>
<email>leo@gaspard.io</email>
</author>
<published>2018-10-22T14:44:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8e584392dce53d322b9403306991944c5578b1f0'/>
<id>urn:sha1:8e584392dce53d322b9403306991944c5578b1f0</id>
<content type='text'>
This changes the meaning of `e` for non-drafts to make it behave
similarly to new messages, which here means add the `FCC` header.
</content>
</entry>
<entry>
<title>emacs: resume messages</title>
<updated>2016-11-13T17:15:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-13T14:08:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2dd96d6bd642c3b32ce1997528f69665019b7497'/>
<id>urn:sha1:2dd96d6bd642c3b32ce1997528f69665019b7497</id>
<content type='text'>
Provide functionality to resume editing a message previously saved with
notmuch-draft-save, including decoding the X-Notmuch-Emacs-Secure
header.

Resume gets the raw file from notmuch and using the emacs function
mime-to-mml reconstructs the message (including attachments).

'e' is bound to resume a draft from show or tree mode.
</content>
</entry>
<entry>
<title>emacs: check drafts for encryption tags before saving</title>
<updated>2016-11-13T17:15:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-13T14:08:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=90248f862b1860cc80c8afd06636311372e95fe4'/>
<id>urn:sha1:90248f862b1860cc80c8afd06636311372e95fe4</id>
<content type='text'>
In general the user may not want to save plaintext copies of messages
that they are sending encrypted, so give them a chance to abort.
</content>
</entry>
<entry>
<title>emacs: postpone a message</title>
<updated>2016-11-13T16:55:24Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-11-13T14:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d820b97477f5705640aa8dcf9dcf311e37508def'/>
<id>urn:sha1:d820b97477f5705640aa8dcf9dcf311e37508def</id>
<content type='text'>
This provides initial support for postponing in the emacs frontend;
resuming will follow in a later commit. On saving/postponing it uses
notmuch insert to put the message in the notmuch database

Current bindings are C-x C-s to save a draft, C-c C-p to postpone a
draft (save and exit compose buffer).

Previous drafts get tagged deleted on subsequent saves, or on the
message being sent.

Each draft gets its own message-id, and we use the namespace
draft-.... for draft message ids (so, at least for most people, drafts
are easily distinguisable).
</content>
</entry>
</feed>
