<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs/notmuch.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:23:26Z</updated>
<entry>
<title>Emacs: Fix notmuch-message-summary-face definition</title>
<updated>2020-08-22T12:23:26Z</updated>
<author>
<name>Teemu Likonen</name>
<email>tlikonen@iki.fi</email>
</author>
<published>2020-08-16T17:13:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3512e2bc83b226a6fddff2940f3929b16ffea67c'/>
<id>urn:sha1:3512e2bc83b226a6fddff2940f3929b16ffea67c</id>
<content type='text'>
Emacs face definition forms are either

    ((DISPLAY . PLIST)
     (DISPLAY . PLIST))

or

    ((DISPLAY PLIST)   ;For backward compatibility.
     (DISPLAY PLIST))

Commit a2388bc56e55da5d5695816818274f8a84b0ed92 (2020-08-08) follows
neither of the correct formats. It defines:

    `((((class color) (background light))
       ,@(and (&gt;= emacs-major-version 27) '(:extend t))
       (:background "#f0f0f0"))
      (((class color) (background dark))
       ,@(and (&gt;= emacs-major-version 27) '(:extend t))
       (:background "#303030")))

which produces:

    ((DISPLAY
      :extend t (:background "#f0f0f0"))
     (DISPLAY
      :extend t (:background "#303030")))

And that is wrong format.

This change fixes the face definition form to produce:

    ((DISPLAY
      :extend t :background "#f0f0f0")
     (DISPLAY
      :extend t :background "#303030"))

which follows the (DISPLAY . PLIST) format (see above).
</content>
</entry>
<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/tree: introduce notmuch-tree-parent-buffer variable</title>
<updated>2020-08-16T13:42:02Z</updated>
<author>
<name>William Casarin</name>
<email>jb55@jb55.com</email>
</author>
<published>2020-08-11T17:36:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=189175ecd6fde78ded219a4bc6dd7b649564c30f'/>
<id>urn:sha1:189175ecd6fde78ded219a4bc6dd7b649564c30f</id>
<content type='text'>
This variable will be used in a similar fashion to
notmuch-show-parent-buffer. It will be used to navigate between
threads from the parent search buffer.

Signed-off-by: William Casarin &lt;jb55@jb55.com&gt;
</content>
</entry>
<entry>
<title>emacs: Increase consistency of library headers</title>
<updated>2020-08-10T00:14:36Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=df3fab18fe70ea750f6f06da30291c67de7e74f2'/>
<id>urn:sha1:df3fab18fe70ea750f6f06da30291c67de7e74f2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>emacs: Improve doc-strings</title>
<updated>2020-08-10T00:14:36Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e63f37a4a90c5d2a399a99a0566b6e1dfea263aa'/>
<id>urn:sha1:e63f37a4a90c5d2a399a99a0566b6e1dfea263aa</id>
<content type='text'>
- The first sentence should fit on the first line in full.  This is
  even the case when that causes the line to get a bit long.  If it
  gets very long, then it should be made shorter.

- Even even the second sentence would fit on the first line, if it
  just provides some details, then it shouldn't be done.

- Symbols are quoted like `so'.

- There is no clear rule on how to (not) quote non-atomic
  s-expressions, but quoting like '(this) is definitely weird.

- It is a good idea to remember that \" becomes " and to take
  that in mind when adjusting the automatic filling by hand.

- Use the imperative form.

- Arguments are written in all uppercase.
</content>
</entry>
<entry>
<title>emacs: Extend face to window edge again</title>
<updated>2020-08-09T23:53:46Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a2388bc56e55da5d5695816818274f8a84b0ed92'/>
<id>urn:sha1:a2388bc56e55da5d5695816818274f8a84b0ed92</id>
<content type='text'>
Since Emacs 27 each face has to be explicitly configured to "extend
to the edge of the window".  Without doing that the face used for
the newline character only has an effect that spans "one character"
(i.e. it looks like there is a single trailing space character).

We don't want that so extend the face in Emacs 27, so that it looks
the same as it did in older Emacs releases.  We have to do this
conditionally, otherwise older Emacsen would choke on it.
</content>
</entry>
<entry>
<title>emacs: Use 'when' instead of 'if' when there is no ELSE part</title>
<updated>2020-08-09T23:52:34Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e1a700067a22214f54064c281219fbbbef87de06'/>
<id>urn:sha1:e1a700067a22214f54064c281219fbbbef87de06</id>
<content type='text'>
</content>
</entry>
<entry>
<title>emacs: Use 'unless' instead of 'when' and 'not'</title>
<updated>2020-08-09T23:51:26Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=09f6533c3781b61ea634790d4bad38aadf89115c'/>
<id>urn:sha1:09f6533c3781b61ea634790d4bad38aadf89115c</id>
<content type='text'>
Also use 'unless' in a few cases where previously 'if' was used with
'not' but without an ELSE part.
</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: Only set one variable per setq form</title>
<updated>2020-08-09T23:50:50Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=18d289c86309ae796e6f027c289b17ccdd38f220'/>
<id>urn:sha1:18d289c86309ae796e6f027c289b17ccdd38f220</id>
<content type='text'>
It's a bit weird to avoid having to write the "(setq ... )" more than
once, just because we can.  In a language that uses '=' for the same
purpose we also happily use that once per assignment.

While there are no benefit to using just one 'setq' there are some
drawbacks.  It is not always clear on first what is a key and what a
value and as a result it is easy to make a mistake.  Also it becomes
harder to comment out just one assignment.
</content>
</entry>
</feed>
