From: dhall@illusion.apk.net (d. hall)
Subject: Yanking the original article buffer
Date: 06 Mar 1996 19:36:09 -0500 [thread overview]
Message-ID: <x6zq9tpwna.fsf@illusion.apk.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Per mentioned an invisible buffer which contains the original article.
Could Sept. Gnus. I'm assuming SC doesn't know about this buffer and yanks
the modified buffer. Could/should Emacs overload this function with it's
own version? Or else should Emacs switch to the original article buffer
before it decides to reply/followup?
d.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMT4vTIX26urqpgG1AQFMDgP/WcPEyCk/4mQFT0CV3og0wFJeVwiBVhHX
KqDcxqwIJuUZommA2+h5AyGo9CNRGCNAE2kOvuAuQvXaIXvUW1qGmeHajz2gkt72
HeRpRaV3ASdj0WjfKqnGAzcNBQcUvIQRn/yZSH1xLI4Cbw6NIbjyun5KXTFuWHKy
RHCHbzDArl8=
=vEYI
-----END PGP SIGNATURE-----
--
``it's a death row pardon... two minutes, too late''
~ alanis morissette, ironic
next reply other threads:[~1996-03-07 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-07 0:36 d. hall [this message]
1996-03-07 1:11 ` Per Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x6zq9tpwna.fsf@illusion.apk.net \
--to=dhall@illusion.apk.net \
/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.
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 NNTP newsgroup(s).