unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: Global Font Lock by default
Date: Wed, 02 Nov 2005 05:27:35 -0500	[thread overview]
Message-ID: <E1EXFqB-0001F8-A2@fencepost.gnu.org> (raw)
In-Reply-To: <m3pspku1ky.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    Maybe we should have a --no-font-lock -nfl options....

I don't see a need for them.  There is no reason to make
a command line option for every Emacs option.
Command line options are mainly useful for things
that you might want to do differently from one Emacs invocation
to another.  I don't think that font lock is in that class.

Besides, people will think that -nfl means it follows
US-style football rules.

  parent reply	other threads:[~2005-11-02 10:27 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 20:34 Global Font Lock by default Richard M. Stallman
2005-10-29 21:51 ` Kim F. Storm
2005-10-29 23:44   ` David Kastrup
2007-02-27 19:59     ` Stuart D. Herring
2005-10-30 14:52   ` Richard M. Stallman
2005-10-31 16:48     ` Dan Nicolaescu
2005-10-31 17:31       ` Romain Francoise
2005-10-31 17:47         ` Dan Nicolaescu
2005-10-31 18:35           ` Romain Francoise
2005-10-31 20:48             ` Dan Nicolaescu
2005-10-31 21:11               ` Romain Francoise
2005-10-31 21:24                 ` Dan Nicolaescu
2005-10-31 21:50                   ` Romain Francoise
2005-10-31 22:07                     ` Dan Nicolaescu
2005-10-31 22:21                       ` Stefan Monnier
2005-10-31 22:41                         ` Dan Nicolaescu
2005-10-31 22:52                           ` Stefan Monnier
2005-10-31 23:20                             ` Miles Bader
2005-11-01 15:05                         ` Dan Nicolaescu
2005-11-01 11:56                       ` Romain Francoise
2005-11-01 21:52                       ` Richard M. Stallman
2005-11-02 22:51                         ` Dan Nicolaescu
2005-11-01  4:53                 ` Eli Zaretskii
2005-11-01  6:25                   ` Dan Nicolaescu
2005-11-01  6:35                   ` Dan Nicolaescu
2005-11-01 19:50                     ` Eli Zaretskii
2005-11-01 20:43                       ` Dan Nicolaescu
2005-11-02  4:23                         ` Eli Zaretskii
2005-11-02  5:46                           ` Dan Nicolaescu
2005-11-02 18:55                             ` Eli Zaretskii
2005-11-02 20:00                               ` Dan Nicolaescu
2005-11-03  4:39                                 ` Eli Zaretskii
2005-11-03  5:53                                   ` Dan Nicolaescu
2005-11-04 11:01                                     ` Eli Zaretskii
2005-11-04 14:20                                       ` Eli Zaretskii
2005-11-06 19:47                       ` Dan Nicolaescu
2005-11-01  7:29       ` Dan Nicolaescu
2005-11-01 10:03         ` Kim F. Storm
2005-11-01 12:04           ` Kim F. Storm
2005-11-01 12:56             ` Chong Yidong
2005-11-01 13:36               ` Kim F. Storm
2005-11-01 15:10                 ` Dan Nicolaescu
2005-11-01 17:19                   ` Luc Teirlinck
2005-11-01 17:23                   ` Luc Teirlinck
2005-11-01 17:28                   ` Luc Teirlinck
2005-11-01 19:57                   ` Eli Zaretskii
2005-11-01 19:54           ` Eli Zaretskii
2005-11-01 20:03             ` Kim F. Storm
2005-11-02  1:33               ` Luc Teirlinck
2005-11-02 10:27           ` Richard M. Stallman [this message]
2005-11-02 12:08             ` David Kastrup
2005-11-02 14:10               ` Luc Teirlinck
2005-11-03 13:50               ` Richard M. Stallman
2005-11-03 14:57                 ` Stefan Monnier
2005-11-03 16:24                   ` David Kastrup
2005-11-04  2:03                 ` 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=E1EXFqB-0001F8-A2@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=dann@ics.uci.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).