unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Further problem with recent changes to custom-magic-alist.
Date: Thu, 24 Feb 2005 17:28:25 -0600 (CST)	[thread overview]
Message-ID: <200502242328.j1ONSPa18239@raven.dms.auburn.edu> (raw)
In-Reply-To: <200502242315.j1ONFkp18229@raven.dms.auburn.edu> (message from Luc Teirlinck on Thu, 24 Feb 2005 17:15:46 -0600 (CST))

>From my previous reply:

   If deemed _really_ necessary, there would be place for things like:

   SAVED, but not set.  Code written into `custom-file'.

   Or, less accurately, if custom-file is set:

   SAVED, but not set.  Code written in your init file.

That could be somewhat confusing again.  Better:

SAVED, but not set.  Custom wrote code into `custom-file'.

or:

SAVED, but not set.  Custom wrote code in your init file.

But I really find both redundant, given the proposed text on top of
the buffer.  So I prefer:

SAVED, but not set.

which is the present version of my patch.

Sincerely,

Luc.

  reply	other threads:[~2005-02-24 23:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15  0:55 Further problem with recent changes to custom-magic-alist Luc Teirlinck
2005-02-22  8:42 ` Richard Stallman
2005-02-22 15:41   ` Luc Teirlinck
2005-02-22 23:10     ` Robert J. Chassell
2005-02-23  0:50       ` Luc Teirlinck
2005-02-23  1:26         ` Luc Teirlinck
2005-02-23 23:01         ` Robert J. Chassell
2005-02-23 20:37     ` Richard Stallman
2005-02-23 22:09       ` Lennart Borgman
2005-02-24 23:15         ` Luc Teirlinck
2005-02-24 23:28           ` Luc Teirlinck [this message]
2005-02-27  0:33           ` Richard Stallman
2005-02-27  2:23             ` Luc Teirlinck
2005-02-27 20:41               ` Richard Stallman
2005-02-27 21:47                 ` Luc Teirlinck
2005-02-24  3:51       ` Luc Teirlinck

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=200502242328.j1ONSPa18239@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=rms@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).