unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <Roland.Winkler@physik.uni-erlangen.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, emacs-devel@gnu.org
Subject: Re: faces and face variables
Date: Sat, 13 Sep 2008 21:27:00 +0200	[thread overview]
Message-ID: <18636.5124.611868.27794@tfkp07.physik.uni-erlangen.de> (raw)
In-Reply-To: <jtzlmbhq92.fsf@fencepost.gnu.org>

On Sat Sep 13 2008 Glenn Morris wrote:
> http://lists.gnu.org/archive/html/emacs-devel/2008-02/msg01660.html
> 
>     Maybe we should work harder to document the fact that we do not
>     want such variables.
> 
> Echoing your suggestion.

That message continues:

  Where would such info have reached you better?

I looked up defface in the elisp manual in order to find a hint. But
there was none. So I suggest to mention there (or include a link
pointing elsewhere) that such variables are deprecated.

> > Font-lock also has such variables, and the code contains the comment
> > that these variables
> 
> Don't use font-lock as an example, it's a law unto itself for
> historical reasons.

As I said, the starting point for me was dired.el. Certainly, that
code has its own history. But the bottom line is that there is more
than one source for the "wrong inspiration" and it would be good if
at some prominent point it was stated clearly what today's
recommended strategy is (despite historical counter examples).

Are there, besides font-lock and dired, other fossils in GNU emacs
that still use such variables?

Roland




  reply	other threads:[~2008-09-13 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200809090636.m896acaT011007@sallyv1.ics.uci.edu>
     [not found] ` <18630.36126.116571.102340@tfkp07.physik.uni-erlangen.de>
     [not found]   ` <200809091834.m89IYJrt004178@sallyv1.ics.uci.edu>
     [not found]     ` <18630.52279.410707.428217@tfkp07.physik.uni-erlangen.de>
     [not found]       ` <200809100554.m8A5sbLU020022@sallyv1.ics.uci.edu>
     [not found]         ` <18634.41341.360898.898779@tfkp07.physik.uni-erlangen.de>
     [not found]           ` <200809121750.m8CHoXar025729@sallyv1.ics.uci.edu>
     [not found]             ` <18634.45534.791696.614584@tfkp07.physik.uni-erlangen.de>
     [not found]               ` <200809130953.m8D9rEZC011379@sallyv1.ics.uci.edu>
2008-09-13 16:03                 ` faces and face variables Roland Winkler
2008-09-13 18:09                   ` Glenn Morris
2008-09-13 19:27                     ` Roland Winkler [this message]
2008-09-13 22:43                       ` Drew Adams
2008-09-14 17:02                         ` Miles Bader
2008-09-14 19:04                           ` Drew Adams
     [not found] ` <18775.34703.848628.238267@tfkp04.physik.uni-erlangen.de>
2008-12-29  6:33   ` Proced's display/handling of process trees: request for feedback Roland Winkler

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=18636.5124.611868.27794@tfkp07.physik.uni-erlangen.de \
    --to=roland.winkler@physik.uni-erlangen.de \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).