unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
	Tomi Ollila <tomi.ollila@iki.fi>,
	Mark Walters <markwalters1009@gmail.com>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH v3] emacs:  postpone/resume support
Date: Thu, 07 Jul 2016 20:00:10 -0400	[thread overview]
Message-ID: <87shvlf185.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <87wpm3dgu6.fsf@zancas.localnet>

[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]

On Sun 2016-06-05 07:18:25 -0400, David Bremner wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> ... but I think I am not biased when I think that if ctrl-x ctrl-s
>> does something more magical than simple (save-buffer) in buffers that
>> looks like text editing buffer, that is going to be unexpected disturbing
>> functionality to someone (else like me)...
>
> This is a valid point. On the other hand the binding is copied from
> Gnus, which also includes at least _some_ magic
>
>       http://www.gnu.org/software/emacs/manual/html_node/gnus/Drafts.html

gnus isn't the only thing that does something more "magical" than saving
a raw buffer to a file.

try the following:

   echo test | gpg --output test.gpg --armor --default-recipient-self  --encrypt
   emacs test.gpg

emacs will prompt you to decrypt the file, then let you edit the
cleartext buffer.

a subsequent "C-x C-s" will re-save it encrypted.  (at least it does for
me!)

[ i note several weirdnesses here around the round-trip cleanliness and
  safety of this operation which aren't relevant to notmuch, but that's
  a different story, and i've reported them to emacs upstream ]

Of course, this functionality appears to also happen within
"save-buffer" itself -- so arguably it's not more "magical" than
save-buffer, since it *is* save-buffer.


Tomi, would you object if Mark's patches were somehow integrated into
save-buffer itself, instead of just re-mapping C-x C-s ?  (i don't know
elisp well enough to know how feasible that would be)

My bottom line:

Mark's series here works well for me, and represents the best draft
handling i've seen yet for notmuch-emacs.  It would be really good to
incorporate something approximating this functionality in the mainline.

        --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 948 bytes --]

  reply	other threads:[~2016-07-08 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 16:59 Emacs: postponing messages Brian Sniffen
2016-06-04  0:43 ` [PATCH v3] emacs: postpone/resume support Mark Walters
2016-06-05 10:43   ` Tomi Ollila
2016-06-05 11:18     ` David Bremner
2016-07-08  0:00       ` Daniel Kahn Gillmor [this message]
2016-07-08 11:08         ` Tomi Ollila
2016-08-30 18:24   ` Emacs: postponing messages David Bremner

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=87shvlf185.fsf@alice.fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=david@tethera.net \
    --cc=markwalters1009@gmail.com \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).