unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Marc Fargas <telenieko@telenieko.com>, notmuch@notmuchmail.org
Subject: Re: notmuch.el, needs without-restriction to properly save draft
Date: Wed, 13 Mar 2024 16:00:25 -0700	[thread overview]
Message-ID: <87frwtg2k6.fsf@wondoo.home.cworth.org> (raw)
In-Reply-To: <87wmq6rt2f.fsf@marcfargas.com>

On Wed, Mar 13 2024, Marc Fargas wrote:
> Hi there,

Hi, Marc!

> I'm not sure if this is the appropiate mailing list for bugs regarding
> notmuch.el (Notmuch in Emacs). Also, I'm not subscribed so please keep
> me in CC!

Yes, this is a fine place to report things

> I recently noticed that when saving drafts in notmuch I would loose all
> the headers that are not normally visible on the compose
> buffer. References, In-Reply-To and the likes.

Thanks for the bug report, as well as the fix you provided. I haven't
run it, but it looks totally reasonable.

> Note that when resuming the draft later on all headers will be visible,
> still working out how to restore the narrow restriction there.

That seems worth chasing down, but shouldn't prevent the acceptance of
your fix here which seems like only progress in the right direction.

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 format-patch HEAD~` or similar.

Thanks again,

-Carl

  reply	other threads:[~2024-03-13 23:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 16:32 notmuch.el, needs without-restriction to properly save draft Marc Fargas
2024-03-13 23:00 ` Carl Worth [this message]
2024-03-14 15:03   ` [PATCH] Use `without-restriction` in `with-temporary-notmuch-message-buffer` Marc Fargas
2024-03-15  8:33     ` Marc Fargas
2024-03-15  9:59       ` David Bremner
2024-03-24 17:04   ` notmuch.el, needs without-restriction to properly save draft Marc Fargas
2024-03-24 17:54     ` Marc Fargas
2024-04-04 11:13       ` Marc Fargas
2024-06-15 17:57       ` David Bremner
2024-06-17  9:27         ` Michael J Gruber
2024-06-17  9:53           ` Marc Fargas
2024-06-17 10:27             ` David Bremner
2024-06-17 10:29               ` David Bremner
2024-06-17 11:37             ` Marc Fargas
2024-06-17 14:04               ` [PATCH] Replace `without-restriction` with `save-restriction` michaeljgruber+grubix+git
2024-06-17 19:28                 ` [PATCH v2 1/2] " michaeljgruber+grubix+git
2024-06-17 19:28                 ` [PATCH v2 2/2] Replace `delete-line` with its definition michaeljgruber+grubix+git
2024-06-17 22:49                   ` David Bremner
2024-06-18  5:58                     ` Marc Fargas
2024-06-18 14:33                       ` Michael J Gruber
2024-06-19 10:48                   ` David Bremner
2024-06-17 14:28               ` notmuch.el, needs without-restriction to properly save draft David Bremner
2024-03-24 17:08   ` Marc Fargas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frwtg2k6.fsf@wondoo.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=notmuch@notmuchmail.org \
    --cc=telenieko@telenieko.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).