Xiyue Deng writes:
>>
>> There is also message-server-alist, which does not need a header.
>
> Thanks for the tip! I think that should work, though I'd like a more
> notmuch-ish solution if possible. And in fact I had some success on
> advising `notmuch-mua-mail' and reacting on 'From from `oth
* David Bremner:
> The post-insert-hook is only called by notmuch-insert. [...]
Thanks, David. Why I did not suspect this, I have no idea. In my setup,
I don't require notmuch-insert, so the same is true for the hook.
-Ralph
___
notmuch mailing list --
Oops, looks like I somehow hijacked a thread instead of creating a new
one. Sorry, my bad. I guess switching one's MUA is not easily done
without small hiccups along the way.
-Ralph
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send
the best place to set this in
>> notmuch when sending/replying. AIUI notmuch does not really have the
>> concept of mail account, so this may require some manual handling. I
>> tried to `re-search-forward' in notmuch-message-mode-hook for the `From:
>
>
> You could tr
does not really have the
> concept of mail account, so this may require some manual handling. I
> tried to `re-search-forward' in notmuch-message-mode-hook for the `From:
You could try out message-templ (elpa-message-templ in Debian). I'm
using that to set the X-Message-SMTP-Method h
David Bremner writes:
> David Bremner writes:
>
>> +EXPECTED=$NOTMUCH_SRCDIR/test/git-remote.expected-output
>> +MAKE_EXPORT_PY=$NOTMUCH_SRCDIR/test/make-export.py
>
> I see I lost the script make-export.py going from v1 to v2. I will
> re-roll the series to i
David Bremner writes:
> +EXPECTED=$NOTMUCH_SRCDIR/test/git-remote.expected-output
> +MAKE_EXPORT_PY=$NOTMUCH_SRCDIR/test/make-export.py
I see I lost the script make-export.py going from v1 to v2. I will
re-roll the series to include it, but I want try a refactor that puts
the URL parsin
* inwit:
> please do share any thoughts in the ml or in the irc channel, and do
> send patches over if you feel like!
I already tried subscribing to the aerc mailing list, but whoever
configured the ML service for sourcehut forgot to create the necessary
DNS records for IPv6. :-( Antispam measure
Frederick Eaton writes:
> it is rather common to receive multiple distinct messages with the
> same ID, for example when someone replies to a mailing list post and
> Cc's me, and I would want these to be separately viewable (they are
> linked together ith an "=" in the Mutt thread view) for secur
On 29/09/2024, 06:37, Ralph Seichter wrote:
> That's one hell of a recommendation, inwit. Thank you! I think that aerc
> may be just what I was looking for.
Happy to help! :) The notmuch backend in aerc still has some rough
edges, and the community is nice and helpful, so please do share any
tho
* inwit:
> I use aerc as my main email driver: it works fine with notmuch, it's
> quite configurable and you can easily use $EDITOR to write your emails
Blimey! I only wanted to give "aerc" a brief glance to begin with, and
now two hours have flown by. Aerc is looking mighty fine already,
running
On 2024-09-28 20:49, Nicolas Graves wrote:
>> I cannot reproduce this in my local environment. Could it be
>> something in your pre-new/post-new hooks?
>
> Oh thanks, it seems indeed that it might come from there. I will post an
> update if that was indeed the issue.
>
> Thanks again.
Indeed it
David Bremner writes:
> Brennan Vincent writes:
>
>> This command inserts the current buffer as a draft. It optionally
>> begins editing the draft.
>
> [nice commit message snipped]
>
> Here again, if possible we would like a test. For emacs tests it is a
> bit more laborious, but there are seve
On 2024-09-28 18:14, Pengji Zhang wrote:
> Hi!
>
> Nicolas Graves writes:
>
>> Hi!
>>
>> Thanks for notmuch.
>>
>> I have a device which for some reason have a space in its name.
>> It's the default installation, I surely don't remember setting
>> such a name myself.
>>
>> This creates so
If I may chime in, I use evil inside emacs to alleviate some of the
finger-memory burdens you mention (and because modal editing is THE way, of
course). But, more importantly, I use aerc as my main email driver: it works
fine with notmuch, it's quite configurable and you can easily use $EDITOR t
* Emmanuel Beffara:
> Notmuch certainly does not require you to use Emacs [...]
Sorry, my wording was certainly not ideal. I am aware that Emacs is not
a requirement for Notmuch. I am also using the Notmuch binary in various
custom scripts.
Emacs has been part of my mail workflow because I found
Hello,
De Ralph Seichter le 28/09/2024 à 15:00:
> Is anybody here using Notmuch in combination with an up-to-date version
> of Neovim? I have experimented with notmuch-vim [1], but without success.
> Given that the latest changes to this plugin were made three years ago
> and that the plugin targe
Hi!
Nicolas Graves writes:
Hi!
Thanks for notmuch.
I have a device which for some reason have a space in its name.
It's the default installation, I surely don't remember setting
such a name myself.
This creates some issues with notmuch, which seems to inject
this variable without quoti
Thank you all for your helpful replies. It seems pretty clear that the recommended Notmuch usage
for someone who wants to incorporate a script that classifies a batch of messages, is either to
write the whole script to use Notmuch from the beginning, and to have the messages specified as a
list
"Brennan Vincent" writes:
>> Since notmuch is already a talloc context, you should address the need
>> for a new context somewhere (either a comment or the commit message).
> I don't remember why I did this. I've never used talloc before and
> probably just got confused. I'll switch to using notm
Start of forwarded message
From: "Brennan Vincent"
To: David Bremner
Subject: Re: [PATCH v2] Add --emit-message-id flag to notmuch-insert.
Date: Thu, 26 Sep 2024 16:04:43 -0400
David Bremner writes:
> Brennan Vincent writes:
>
>
Brennan Vincent writes:
> This command inserts the current buffer as a draft. It optionally
> begins editing the draft.
[nice commit message snipped]
Here again, if possible we would like a test. For emacs tests it is a
bit more laborious, but there are several options outlined in
test/
> wil
Brennan Vincent writes:
First, thanks for sending a contribution to notmuch.
Usually we insist on a bit more verbose (see
https://notmuchmail.org/contributing/#index5h2 for details).
Here it's probably enough to mention the overall goal of the patch
series, that this feature will be used to add
Panayotis Manganaris writes:
> I find this way to be more flexible than the current provisions for "named
> queries" in the notmuch config/database:
>
> query:
>
> The 'query:' prefix allows queries to refer to previously saved queries
> added with ‘notmuch-config(1)’.
>
> Though, I'm not
Am Sa., 21. Sept. 2024 um 18:24 Uhr schrieb Panayotis Manganaris
:
...
> notmuch search --output=messages 'tag:new' > /tmp/msgs
> notmuch search --output=files 'tag:new' |\
> bogofilter -o0.7,0.7 -bt |\
> paste - /tmp/msgs |\
> awk '$1 ~ /S/ { print "-new +spam", "-", $3 }' |\
> not
ch faster than repeatedly invoking "notmuch tag"
Of course, this performance difference is probably not noticeable in a well
curated inbox.
Also, the awk-print-tag-batch pattern is re-usable if you'd like to auto-tag
messages in other ways e.g.
- tag "vip" threads from known
* 2024-09-21 12:24:14-0400, Panayotis Manganaris wrote:
> Like you, I have notmuch configured to assign newly fetched mail with
> tag "new"
>
> notmuch search --output=messages 'tag:new' > /tmp/msgs
> notmuch search --output=files 'tag:new' |\
> bogofilter -o0.7,0.7 -bt |\
> paste - /tmp/m
Frederick Eaton writes:
>
> Suppose the filter script reads a message from a particular file and decides
> that it is
> spam. How does the filter tell Notmuch that the message corresponding to that
> file is spam?
> You seem to be saying below that the filter script should extract the
> Messag
Hi Frederick,
* Frederick Eaton [2024-09-20; 20:23 -07]:
> On Sat, Sep 21, 2024 at 08:25:10AM +0800, Pengji Zhang wrote:
>>Frederick Eaton writes:
>>>I am trying to figure out how to adapt a script I wrote for
>>>filtering messages, to apply notmuch tags to each message. A
>>>difficulty is that t
Am Sa., 21. Sept. 2024 um 05:23 Uhr schrieb Frederick Eaton :
>
> Thank you for your response, Pengji.
>
> On Sat, Sep 21, 2024 at 08:25:10AM +0800, Pengji Zhang wrote:
> >Hi Frederick,
> >
> >Frederick Eaton writes:
> >
> >>I am trying to figure out how to adapt a script I wrote for
> >>filtering
f the manual pages, particularly
illustrating the case where the programmer wants to re-tag a
message that is provided as a file or on stdin.
[...]
I see now that this text is only suggesting that Notmuch
supports searches for directory names, but on first read it
wasn't really clear to me
to the user that there is no index of path names would help clarify what can be
done with the software. Also, a short example of using Notmuch in a filter
script would be useful in one of the manual pages, particularly illustrating
the case where the programmer wants to re-tag a message
Hi Frederick,
Frederick Eaton writes:
I am trying to figure out how to adapt a script I wrote for
filtering messages, to apply notmuch tags to each message. A
difficulty is that the messages are already in the Notmuch
database, because another tool has delivered them to a maildir
and run "n
Hi David, Mohsin,
* David Bremner [2024-09-02; 22:12 -03]:
> Mohsin Kaleem writes:
>> David Bremner writes:
> You can search any header if you index it first. See notmuch-config(1)
> for how to configure extra headers. Received seems like the most likely
> to have what you want. I'm curious how
Mohsin Kaleem writes:
> David Bremner writes:
>
>> Our strategy for indexing html hasn't changed much since the
>> beginning. We just remove all tags using a simple state
>> machine. Unfortunately the term you want to search for is an attribute
>> of an href tag. Offhand I can't think of a simpl
David Bremner writes:
> 3) The original script took a path to mail_root, but this doesn't
> really cover the possible split configurations; in particular it
> doesn't handle my (XDG) layout. The current code just looks for the
> "default" notmuch setup, and ignores the URL. I am open to ideas fo
Am Fr., 23. Aug. 2024 um 17:46 Uhr schrieb Martin Jambor :
>
> Hi,
>
> On Thu, Aug 22 2024, Michael J Gruber wrote:
> > Am Do., 22. Aug. 2024 um 14:37 Uhr schrieb Martin Jambor :
> >>
> >> Hi,
> >>
> >> I have noticed that notmuch-git was not being copied to an appropriate
> >> destination during m
First of all, apologies for being late to the discussion, and for having
missed its initial part.
I have been tinkering with email address completion in message mode for
a while, and would like to add a few comments with the hope of providing
slightly bigger picture, and with the hope that it may
Hi,
On Thu, Aug 22 2024, Michael J Gruber wrote:
> Am Do., 22. Aug. 2024 um 14:37 Uhr schrieb Martin Jambor :
>>
>> Hi,
>>
>> I have noticed that notmuch-git was not being copied to an appropriate
>> destination during make install. This patch adds that.
>>
>> ---
>> Makefile.local | 1 +
>> 1 f
Michael J Gruber writes:
> notmuch-git(1) mentions nmbug, so we'd want to install that as well, don't we?
>
FWIW, we do in Debian. But I am probably biased as one of the main users
of nmbug and the Debian package maintainer.
d
___
notmuch mailing lis
Am Do., 22. Aug. 2024 um 14:37 Uhr schrieb Martin Jambor :
>
> Hi,
>
> I have noticed that notmuch-git was not being copied to an appropriate
> destination during make install. This patch adds that.
>
> ---
> Makefile.local | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Makefile.local b
Antoine Beaupré writes:
>
> I'm fine with that too, what's the next step? A patch that actually
> replaces the notmuch-address.el stuff with tarsis's? A reply to tarsius'
> original patch? :)
>
> I can try either, but don't have the latter in my archives, i think.
My plan is as follows.
1) rel
Pengji Zhang writes:
> This is a follow-up to [1: 8d06dfce]. Per Info node '(elisp)Autoload',
> autoload cookies should start with ';;;###'.
>
> 1: 2024-04-04 8d06dfce175593aebae9a759c9167df4988a3444
>emacs: Autoload notmuch-user-agent related functions
applied to master, thanks
On 2024-08-13 10:05:40, David Bremner wrote:
> Antoine Beaupré writes:
>
>>
>> So I'm not sure what to do with this. This certainly seems really
>> precious stuff! Could we add this to notmuch-emacs, perhaps gated on the
>> Emacs version?
>>
>> Running Emacs 29.4 from Debian bookworm-backports her
Antoine Beaupré writes:
>
> So I'm not sure what to do with this. This certainly seems really
> precious stuff! Could we add this to notmuch-emacs, perhaps gated on the
> Emacs version?
>
> Running Emacs 29.4 from Debian bookworm-backports here, in case that
> matters.
>
I'm more interested in c
Pengji Zhang writes:
>
> I wonder if we could generate and install a 'notmuch-autoloads.el'
> file as well during installation, like mu4e[1]. So we only need to
> load that file at Emacs startup, which should be much cheaper.
Currently notmuch-autoloads.el is generated by package.el
during ins
e that, as it's been broken for months and nobody noticed until
> > recently.
I noticed, switched to https and went ahead.
> > Anyway, it's on my list of things to fix, but it's not really a
> > priority. I'd welcome _good_ reasons why people cannot switch
On 2024-08-11 10:36:07, Liam Hupfer wrote:
> Antoine Beaupré writes:
>
>> I should have posted a followup to this patch already, and must say it’s
>> really not ready at all.
>>
>> I have found myself in the situation where my address completion is now
>> completely broken. I don’t even *know* how
t;
> Anyway, it's on my list of things to fix, but it's not really a
> priority. I'd welcome _good_ reasons why people cannot switch to to
> https, that might cause me to re-prioritize
I recall the git:// worked to pull 2024-06-15 14:54 -0300 Marc Fargas ...
Since then thi
Bumping this patch ([[RFC PATCH] CLI/reply: Remove Received by domain
>From detection]). See the rationale there.
Does anyone depend on notmuch-reply’s fallback to Received by parsing?
Adding Carl Worth, who applied the initial implementation by Dirk
Hohndel (who doesn’t seem to be around) in
Antoine Beaupré writes:
> I should have posted a followup to this patch already, and must say it’s
> really not ready at all.
>
> I have found myself in the situation where my address completion is now
> completely broken. I don’t even *know* how to restore the previous
> behavior.
>
> So clearly
Antoine Beaupré writes:
>
> I should have posted a followup to this patch already, and must say it's
> really not ready at all.
>
> I have found myself in the situation where my address completion is now
> completely broken. I don't even *know* how to restore the previous
> behavior.
>
> So clear
On 2024-08-06 07:30:30, David Bremner wrote:
> Antoine Beaupré writes:
>
>>
>> Now, it seems to me a simple fix is to implement a proper
>> capf (`completion-at-point-function') for notmuch. And that, in turn,
>> is actually pretty simple compared to the code hidden underneath
>> `notmuch-address-
David Bremner writes:
> David Bremner writes:
>
>>
>> This reproduces the problem for me. Indeed it looks a bit like a similar
>> "cursor jumping" problem I have seen (and someone else has reported on
>> IRC). I will see if I can figure anything more out now that I have a
>> reproducer.
>
> I th
David Bremner writes:
> If you can make a reproducer that does not rely on your private notmuch
> config (query:list), I might be able to turn that into a test.
The reproducer does not rely on anything private. Simply evaluate the
expression, say using C-x C-e. You should see it evaluate to th
Tomi Ollila writes:
>
> -- and is the behavior different in some other modes (I (mostly) just use
> notmuch-search and notmuch-show modes so cannot recall how other views
> look like...
>
Yes, the issue is exactly making the behaviour consistent between
modes. It's not just ^M but also tabs tha
David Bremner writes:
> This limitation seems somewhat hard to fix, but at least try to warn
> users when combining crypto operations with mbox output format.
>
> Because the default is --decrypt=auto, the warning is omitted if
> --decrypt=auto is specified. While this is not great, it seems more
Antoine Beaupré writes:
>
> Now, it seems to me a simple fix is to implement a proper
> capf (`completion-at-point-function') for notmuch. And that, in turn,
> is actually pretty simple compared to the code hidden underneath
> `notmuch-address-expand-name', which not only finds completion
> candi
Rudolf Adamkovič writes:
> From c0cb08a843b5c904642da639f94c4a5e43d1ef14 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?=
> Date: Wed, 13 Dec 2023 22:39:02 +0100
> Subject: [PATCH] emacs: Fix saved-search buffer titles
>
> REPRODUCTION STEPS:
>
> (let ((notmuch-saved-search
David Bremner writes:
> Thanks to changing the column widths to accomodate longer function
> names, the diff is rather large, but the content is two new rows for
> 'u' and 'U'
applied to master.
___
notmuch mailing list -- notmuch@notmuchmail.org
To un
Nicholas D Steeves writes:
> James McCoy (1):
> Convert notmuch-vim to Vim addon policy 2.0
>
> Nicholas D Steeves (3):
> Add changelog entry for James McCoy's work
> Allow neomutt to fulfill the "mutt" requirement of notmuch-mutt, and
> Add Astroid as an alternative Recommends; this one
Thorben Günther writes:
> I noticed this when investigating an aerc bug report [1].
>
> When the notmuch config contains a different location for
> database.mail_root (e.g. ~/.mail/user) and database.path (unset,
> should default to ~/.local/share/notmuch/default), the filepath returned
> by "not
Nicholas D Steeves writes:
>
> I have an old clone from https://git.notmuchmail.org/git/notmuch; and I
> track two branches: debian/unstable and release. I made sure both were
> up to date. The presence of debian/unstable usually indicates DEP14
> layout, and I noticed all the other debian/code
David Bremner writes:
> Hi Nicholas;
>
> Thanks for the patches.
You're welcome.
> Unfortunately they are against 5 year old version of notmuch and don't
> apply.
Oh no.
> On debian you can try
>
> $ debcheckout notmuch
>
> For debian only stuff, patches against the release branch (default) a
Nicholas D Steeves writes:
> that may be less intimidating for new users.
> ---
> debian/changelog | 7 +++
> debian/control | 2 +-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/debian/changelog b/debian/changelog
> index 72a52546..442e22ed 100644
> --- a/debian/chang
Sandra Snan writes:
> David Bremner writes:
>> 1) can you make a test (probably something in T465 can serve as
>> a model
>
> What does T465 refer to?
test/T465-emacs-unthreaded.sh
>
> But if the treshhold is too big it won't prevent any crashes,
> overloads, or uncomfortably unergonomic thr
David Bremner writes:
1) can you make a test (probably something in T465 can serve as
a model
What does T465 refer to?
2) Should this be bound by default, or is the function in the
next patch always the one users will want?
The latter since it prevents crashes. I've been dogfooding this
s
Lars Kotthoff writes:
> Thanks David, I've attached the modified patch that I think addresses
> all your comments -- I'm still not 100% sure about the whitespace
> though.
tweaked version applied to master.
___
notmuch mailing list -- notmuch@notmuchma
Thanks David, I've attached the modified patch that I think addresses all your
comments -- I'm still not 100% sure about the whitespace though.
Thanks,
Lars
On Thu, 25 Jul 2024 17:33:48 +0900, David Bremner wrote:
> Lars Kotthoff writes:
>
> > Sorry, I dropped the ball on this -- here's the
Sandra Snan writes:
>
> It shells out to notmuch count to see if the thread is big or small.
> "Big" is hardcoded to ten messages or lower, if we want to introduce a
> variable for that instead, that might be great.
Yes, I think a defcustom is called for.
>
> It's a deliberate choice to count al
Sandra Snan writes:
> + (interactive "P")
> + (let ((thread-id (notmuch-search-find-thread-id)))
> +(if thread-id
> + (notmuch-unthreaded (if entire thread-id
> + (concat notmuch-search-query-string " and "
> thread-id)))
> + (message "No such thread with
Tony Zorman writes:
> Hi,
>
> this adds a new custom variable, `notmuch-mua-subject-regexp`, and an
> associated function, `notmuch-mua-subject-check`, to warn the user when
> the subject contains potentially troublesome things (e.g., nothing at
> all). The idea is the same as `notmuch-mua-attach
Kevin Boulain writes:
> Follow-up of 6273966d, now that sfsexp 1.4.1 doesn't rely on globals
> anymore by default (https://github.com/mjsottile/sfsexp/issues/21).
>
> This simply defers the initial query generation to use the thread-safe
> helper (xapian_query_match_all) instead of Xapian::Query:
David Bremner writes:
> According to the now deleted commentary, the hack of using run-at-time
> was needed for Emacs 24. It seems to be no longer needed for Emacs
> 28.2, and removing it makes further changes to the code simpler.
applied to master
___
David Bremner writes:
> Sometimes merging is not what we want with tags; in particular it
> tends to keep tags in the local repo that have been removed elsewhere.
> This commit provides a new reset command; the reset itself is trivial,
> but the work is to provide a safety check that uses the exi
Lars Kotthoff writes:
> Sorry, I dropped the ball on this -- here's the patch again with space/tab
> inconsistencies fixed. I wasn't entirely sure about this as it's inconsistent
> in the existing source, so I tried to make it as consistent as possible.
> Cover included again below.
>
Hi Lars
te this.
>
Maybe something like the re-edit draft as new interface (e), although
allowing arbitrary edits is a bit of a footgun, so we'd probably want to
make people confirm "are you sure, this could destroy your message" or
similar. I'm too far behind to do this myself,
David Bremner wrote:
> you can use "c F" to copy the file name of the current message into the
> the kill ring, then just yank wherever useful (e.g. to visit the file in
> emacs).
>
> After editing you will need to reindex that file. One way would be
> to use "c i" to copy the message id into the
Morten Kjeldgaard writes:
>
> It's tedious to use the notmuch CLI client to search for the mail and
> then copy/paste the filename, and edit it to correct the date. It would
> be so much easier if it were possible to edit the raw file directly in
> Emacs. I can use 'V' to view the raw file, and t
Aidan Jones writes:
>>
>> This is the only line that caught my eye.
>>
>> Can you try
>>
>> $ notmuch config set maildir.synchronize_flags true
>
> That did it. Thanks for the help!
Glad to hear it. We should try to provide a more informative error
message here.
d
__
Sent with Proton Mail secure email.
On Thursday, June 27th, 2024 at 10:39 AM, David Bremner
wrote:
> Aidan Jones arjones...@protonmail.ch writes:
>
>
>
> > maildir.synchronize_flags=sync
>
>
> This is the only line that caught my eye.
>
> Can you try
>
> $ notmuch config set maildi
Aidan Jones writes:
> maildir.synchronize_flags=sync
This is the only line that caught my eye.
Can you try
$ notmuch config set maildir.synchronize_flags true
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmu
Sent with Proton Mail secure email.
On Wednesday, June 26th, 2024 at 3:44 PM, David Bremner
wrote:
> Aidan Jones arjones...@protonmail.ch writes:
>
> > I am new to notmuch, so I apologize if this is just an operator
> > error. I have a local maildir created using offlineimap. I have ran
>
Aidan Jones writes:
> I am new to notmuch, so I apologize if this is just an operator
> error. I have a local maildir created using offlineimap. I have ran
> notmuch setup and configured notmuch to use the maildir as its
> archive. However, running notmuch new returns 'notmuch new: Illegal
> argu
Hi Tomi,
>> Lovely! This is exactly what I am looking for. But, in addition, we also
>> need another desktop file that uses emacsclient instead of emacs. It
>> would be great if notmuch provided that.
>
> That is kinda provided, if u get the ./emacs/notmuch-emacs-mua.desktop
> file and did
>
> @
On Tue, Jun 18 2024, Arun Isaac wrote:
> Hi David,
>
>> There is emacs/notmuch-mua-mail.desktop in the source. This seems to do
>> what you ask for?
>
> Lovely! This is exactly what I am looking for. But, in addition, we also
> need another desktop file that uses emacsclient instead of emacs. It
>
David Bremner writes:
>
> This reproduces the problem for me. Indeed it looks a bit like a similar
> "cursor jumping" problem I have seen (and someone else has reported on
> IRC). I will see if I can figure anything more out now that I have a
> reproducer.
I think the following is a (simpler) re
michaeljgruber+grubix+...@gmail.com writes:
> From: Michael J Gruber
>
> 37c022ae ("Use `without-restriction` in
> `with-temporary-notmuch-message-buffer`", 2024-03-14)
> introduced `delete-line` in a test, but this is Emacs 29 and above only.
> Replace it with its (almost) definition.
both v2
Am Di., 18. Juni 2024 um 07:58 Uhr schrieb Marc Fargas
:
>
> Hi,
>
> El lun. 17 de jun. 2024, David escribió:
> >
> >> From: Michael J Gruber
> >>
> >> 37c022ae ("Use `without-restriction` in
> >> `with-temporary-notmuch-message-buffer`", 2024-03-14)
> >> introduced `delete-line` in a test, but t
Hi,
El lun. 17 de jun. 2024, David escribió:
>
>> From: Michael J Gruber
>>
>> 37c022ae ("Use `without-restriction` in
>> `with-temporary-notmuch-message-buffer`", 2024-03-14)
>> introduced `delete-line` in a test, but this is Emacs 29 and above only.
>> Replace it with its (almost) definition.
Hi David,
> There is emacs/notmuch-mua-mail.desktop in the source. This seems to do
> what you ask for?
Lovely! This is exactly what I am looking for. But, in addition, we also
need another desktop file that uses emacsclient instead of emacs. It
would be great if notmuch provided that.
Thanks,
michaeljgruber+grubix+...@gmail.com writes:
> From: Michael J Gruber
>
> 37c022ae ("Use `without-restriction` in
> `with-temporary-notmuch-message-buffer`", 2024-03-14)
> introduced `delete-line` in a test, but this is Emacs 29 and above only.
> Replace it with its (almost) definition.
The chan
Marc Fargas writes:
> Hi,
>
> El lun. 17 de jun. 2024, Marc escribió:
>>
>> El lun. 17 de jun. 2024, Michael escribió:
(...)
>>>
>>> Does this depend on emacs version by any chance, i.e. is
>>> `without-restriction` defined on all emacsen? In Fedora's copr
>>> infrastructure, all builds succ
Hi,
El lun. 17 de jun. 2024, Marc escribió:
>
> El lun. 17 de jun. 2024, Michael escribió:
>>> (...)
>>
>> Does this depend on emacs version by any chance, i.e. is
>> `without-restriction` defined on all emacsen? In Fedora's copr
>> infrastructure, all builds succeed but some tests fail with
>> `S
Hi,
El lun. 17 de jun. 2024, Michael escribió:
>> (...)
>
> Does this depend on emacs version by any chance, i.e. is
> `without-restriction` defined on all emacsen? In Fedora's copr
> infrastructure, all builds succeed but some tests fail with
> `Symbol'€™s function definition is void: without-res
David Bremner writes:
> Marc Fargas writes:
>
>> Hi,
>>
>> El lun. 17 de jun. 2024, Michael escribió:
(...)
>>>
>>> Does this depend on emacs version by any chance, i.e. is
>>> `without-restriction` defined on all emacsen? In Fedora's copr
>>> infrastructure, all builds succeed but some tes
Marc Fargas writes:
> Hi,
>
> El lun. 17 de jun. 2024, Michael escribió:
>>> (...)
>>
>> Does this depend on emacs version by any chance, i.e. is
>> `without-restriction` defined on all emacsen? In Fedora's copr
>> infrastructure, all builds succeed but some tests fail with
>> `Symbol'€™s functio
Am Sa., 15. Juni 2024 um 19:57 Uhr schrieb David Bremner :
>
> Marc Fargas writes:
>
> > Hi again,
> >
> > El dom. 24 de mar. 2024, Marc escribió:
> >> El mié. 13 de mar. 2024, Carl escribió:
> >>> (...)
> >>> Could you put your fix together in the form of a git-appliable patch?
> >>> Such as by a
Marc Fargas writes:
> Hi again,
>
> El dom. 24 de mar. 2024, Marc escribió:
>> El mié. 13 de mar. 2024, Carl escribió:
>>> (...)
>>> Could you put your fix together in the form of a git-appliable patch?
>>> Such as by applying it to the notmuch source, running `git commit` and
>>> then `git forma
David Bremner writes:
> In [1], Jakub Wilk observes that the current behaviour is confusing
> since it looks like there are two mailboxes in From, while in fact
> there is only one. It seems to me that notmuch should at least quote
> the display-name part of a mailbox if it has "funny" character
1 - 100 of 18666 matches
Mail list logo
