From: Thien-Thi Nguyen <ttn@glug.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: RMAIL, summary buffer need not be marked as modified
Date: 06 Mar 2003 11:48:41 -0500 [thread overview]
Message-ID: <jk7kbcl9ue.fsf@glug.org> (raw)
In-Reply-To: Alexander Pohoyda's message of "Wed, 12 Feb 2003 22:17:35 +0100 (CET)"
Alexander Pohoyda <alexander.pohoyda@gmx.net> writes:
Hi again,
I have to admit that the modified *RMAIL-summary* buffer irritates
me. This buffer is generated by emacs, so there is nothing user should
care about.
+ ;; There is no need for the summary buffer to be marked as modified.
+ (set-buffer-modified-p nil)
probably a better approach would be to use a mode-line format for RMAIL
summary mode that omits the superfluous information.
thi
prev parent reply other threads:[~2003-03-06 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 21:17 RMAIL, summary buffer need not be marked as modified Alexander Pohoyda
2003-03-06 16:48 ` Thien-Thi Nguyen [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jk7kbcl9ue.fsf@glug.org \
--to=ttn@glug.org \
--cc=bug-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).