From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: New .texi file
Date: Tue, 15 Jun 2004 14:13:34 -0400 [thread overview]
Message-ID: <E1BaIRC-0000fm-Uz@fencepost.gnu.org> (raw)
In-Reply-To: <200406140306.i5E36KQ29367@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 13 Jun 2004 22:06:20 -0500 (CDT))
The 14-character limit is not important in Emacs any more.
prev parent reply other threads:[~2004-06-15 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 1:18 New .texi file Luc Teirlinck
2004-06-13 11:47 ` Kai Grossjohann
2004-06-13 16:28 ` Juri Linkov
2004-06-16 2:56 ` Luc Teirlinck
2004-06-13 22:21 ` Kim F. Storm
2004-06-14 3:06 ` Luc Teirlinck
2004-06-14 7:39 ` Kim F. Storm
2004-06-14 19:44 ` Luc Teirlinck
2004-06-14 19:52 ` Eli Zaretskii
2004-06-15 18:13 ` Richard Stallman [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=E1BaIRC-0000fm-Uz@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).