| Age | Commit message (Collapse) | Author |
|---|
|
[dgit import orig notmuch_0.38.2.orig.tar.xz]
|
|
|
|
|
|
Currently the --to/--cc/--bcc options add "user@example.com, " to the
message headers, with the the unnecessary ", " separator after the
last address, regardless of how many addresses are being added.
This used to be fine, but with recent emacs mm, trying to send the
email with the trailing commas leads to prompt:
Email address looks invalid; send anyway? (y or n)
Fix this by only adding the commas between addresses, avoiding the
trailing commas.
|
|
|
|
qsort(3) does not promise stability, and recent versions of glibc have
been showing more unstable behaviour [2]. Michael Gruber observed [1] test
breakage due to changing output order for message properties.
We provide a sorting order of (key,value) pairs that _looks_ stable by
breaking ties based on value if keys are equal. Internally there may
be some instability in the case of duplicate (key,value) pairs, but it
should not be observable via the iterator API.
[1]: id:CAA19uiSHjVFmwH0pMC7WwDYCOSzu3yqNbuYhu3ZMeNNRh313eA@mail.gmail.com
[2]: id:87msv3i44u.fsf@oldenburg.str.redhat.com
|
|
notmuch 0.38.1 release
|
|
|
|
Just note the 3 bug fixes.
|
|
No changes from 0.38.1~rc1
|
|
notmuch 0.38.1~rc1 release
|
|
|
|
|
|
Fixes: commit 239fdbbbf0cbd6cd6ebafb87e88cdb3cded75364
|
|
Suppress compiler warning.
|
|
The previous version essentially repeated the source code, and
generated a compiler warning.
|
|
Suppress byte-compiler warnings about >80 character docstrings.
|
|
The complicated looking escapes are needed to avoid compile time
warnings. (info "(elisp) Text Quoting Style") for details.
|
|
notmuch release 0.38.1~pre0-1 for experimental (rc-buggy) [dgit]
[dgit distro=debian no-split --quilt=linear]
|
|
Bonus typo fix.
|
|
notmuch 0.38.1~pre0 release
|
|
According to emacs upstream [1], we can't expect overlay invisibility
and images to get along. This commit uses the previously stashed
undisplayer functions to actually remove the images from the buffer.
When the image is toggled, it is essentially redisplayed from scratch,
using the previously stashed redisplay data.
[1]: https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg00593.html
|
|
This data will eventually be used to redisplay hidden images. A
certain amount of refactoring is done here to avoid code
duplication.
|
|
This data will be used to redisplay an image that is hidden by
deleting it from the buffer. We cannot easily delay until the image
is hidden, as we won't have the original data at that point.
|
|
For some kinds of MIME parts (at least images), our trickery with
overlays will not work, so save the more drastic function created by
Gnus that actually deletes the part from the buffer. In an ideal world
we would return this function as (part of) a value, but here the call
stack is too complicated for anything that simple, so we stash it in
the part plist and rely on that being preserved (unlike the mm handle,
which is transient).
|
|
|
|
The function _notmuch_config_load_from_file is only called in two
places in open.cc. Update internal API to match the idiom in open.cc.
Adding a newline is needed for consistency with other status strings.
Based in part on a patch [1] from Eric Blake.
[1]: id:20230906153402.101471-1-eblake@redhat.com
|
|
This is a bit fragile w.r.t. glib changing their error message, but it
already helped me find one formatting bug, so for now I think it's
worth it, instead of just grepping for "UTF-8".
|
|
For now print a generic error message and exit with error on any
non-success code. Previously the code exited, but with exit code zero,
leading users / scripts to think the command had succeeded.
|
|
We should ideally print an informative error message, but at the very
least we should not exit with success.
|
|
|
|
Actual news items to be filled in after they are applied.
|
|
Start preparations for point release
|
|
Python likes to leave behind cache files; noticeable when doing an
in-tree build.
|
|
"ju" reported on IRC that browsing
https://nmbug.notmuchmail.org/nmweb/show/20160719094205.qmf5sjnja6crt5t3%40gotlib
crashed. The underlying issue is that python3 defaults to utf8
decoding files unless they are opened in binary mode. The file in
question (in the nmbug archive; it depends a bit on the routing the
message took) has
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
and some of it is not valid utf8.
|
|
|
|
|
|
|
|
This is created (at least) by the Debian build, but there seems no
harm in cleaning it for everyone.
|
|
Having autopkgtests changes Debian package migration (for better and
worse), so make a note when they were introduced to unstable.
|
|
This avoids spurious underline/italics when exporting to markdown.
|
|
|
|
These are generated indirectly by certain uses of python in the build.
|
|
The python setuputils clean relys on including _notmuch_config.py,
which is cleaned up. Rather than relying on careful ordering, just do
all the cleaning from the GNU Make based build system.
|
|
_notmuch_config.py is generated by configure, and cannot be cleaned up
by the current python build system, since it is imported as a module
by that same build system.
Use DISTCLEAN rather than CLEAN for consistency with other configure
related things.
|
|
|
|
|
|
|
|
|
|
|
