From: Peter.Weiss@class.de
Cc: Peter.Weiss@class.de, ding@gnus.org
Subject: Re: Draft buffer delete
Date: 26 Jan 2001 09:26:09 +0100 [thread overview]
Message-ID: <xpxy7l3ig1ni.fsf@Germany.Sun.com> (raw)
In-Reply-To: <m3g0i7wvs7.fsf@multivac.student.cwru.edu>
>>>>> On 25 Jan 2001 09:28:18 -0500, prj@po.cwru.edu (Paul Jarc) said:
Paul> Peter.Weiss@Class.de writes:
>> Finally I found message-sent-hook, which sounds very good, but setting
>>
>> (add-hook 'message-sent-hook '(lambda()
>> (kill-buffer (current-buffer))))
>>
>> needs still interaction since the buffer is marked as modified when the
>> hook runs.
Paul> You can use set-buffer-modified-p to mark it as unmodified before
Paul> killing it.
If I do this the draft files in the draft buffer won't be deleted.
Peter
--
Peter Weiss
CLASS Firmengruppe phone +49 (0)8151 / 991 - 0
Moosstrasse 7 fax +49 (0)8151 / 991 - 229
D-82319 Starnberg mobil 0172/ 83 79 125
http://www.class.de mailto:Peter.Weiss@Class.de
next prev parent reply other threads:[~2001-01-26 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 12:16 Peter.Weiss
2001-01-25 14:28 ` Paul Jarc
2001-01-26 8:26 ` Peter.Weiss [this message]
2001-02-07 13:37 ` Kai Großjohann
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=xpxy7l3ig1ni.fsf@Germany.Sun.com \
--to=peter.weiss@class.de \
--cc=ding@gnus.org \
/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).