From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Documentation of write-contents-functions
Date: Wed, 23 Jun 2004 09:13:00 -0500 (CDT) [thread overview]
Message-ID: <200406231413.i5NED0P22207@raven.dms.auburn.edu> (raw)
In-Reply-To: <40D94A02.3090809@math.ku.dk> (message from Lars Hansen on Wed, 23 Jun 2004 11:14:42 +0200)
Lars Hansen wrote:
To me the description in files.texi of write-contents-functions does not
make much sense.
I suggest the chances attached.
Do you agree?
These changes are OK with me.
Sincerely,
Luc.
prev parent reply other threads:[~2004-06-23 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 9:14 Documentation of write-contents-functions Lars Hansen
2004-06-23 14:13 ` Luc Teirlinck [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=200406231413.i5NED0P22207@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@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).