From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: customize-rouge output with emacs -q --no-site-file
Date: Sun, 6 Feb 2005 13:54:10 -0600 (CST) [thread overview]
Message-ID: <200502061954.j16JsAB15305@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1Cxlk9-0000JN-AI@fencepost.gnu.org> (message from Richard Stallman on Sun, 06 Feb 2005 07:42:25 -0500)
Richard Stallman wrote:
Perhaps we could set it up so that the "standard values" of these
variables are expressions that compute the proper default based on the
circumstances. Would these variables work right then?
Actually user-mail-address _only_ becomes a rogue variable if you
apply the patch I sent for experimentation (but did not propose to
install in CVS), because it sets the standard value for this
particular option too early. If you do not apply that patch you get:
this option is unchanged from its standard setting.
for user-mail-address, but of course, plenty of _other_ options then
become rogue.
What it shows is that the patch I sent is too simplistic. (Something
I was actually afraid of.)
Sincerely,
Luc.
next prev parent reply other threads:[~2005-02-06 19:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 16:03 customize-rouge output with emacs -q --no-site-file Lennart Borgman
2005-02-04 19:14 ` Lennart Borgman
2005-02-04 21:57 ` Lennart Borgman
2005-02-04 22:17 ` Lennart Borgman
2005-02-04 23:48 ` Luc Teirlinck
2005-02-05 0:47 ` Luc Teirlinck
2005-02-05 17:39 ` Richard Stallman
2005-02-05 0:03 ` Luc Teirlinck
2005-02-05 0:06 ` Luc Teirlinck
2005-02-05 17:39 ` Richard Stallman
2005-02-05 1:56 ` Luc Teirlinck
2005-02-05 3:51 ` Luc Teirlinck
2005-02-05 9:08 ` Lennart Borgman
2005-02-05 14:51 ` Luc Teirlinck
2005-02-06 12:42 ` Richard Stallman
2005-02-06 19:54 ` Luc Teirlinck [this message]
2005-02-05 19:06 ` Luc Teirlinck
2005-02-05 19:52 ` Lennart Borgman
2005-02-05 21:16 ` Luc Teirlinck
2005-02-07 20:51 ` Richard Stallman
2005-02-07 21:27 ` Lennart Borgman
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=200502061954.j16JsAB15305@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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).