unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jari Aalto <jari.aalto@cante.net>, 2235@emacsbugs.donarmstrong.com
Cc: cyd@stupidchicken.com
Subject: bug#2235: 22.2.1 emacs -Q should not turn on font-lock
Date: Sun, 08 Feb 2009 21:32:54 +0200	[thread overview]
Message-ID: <uskmosp09.fsf@gnu.org> (raw)
In-Reply-To: <87fxiox29w.fsf@jondo.cante.net>

> From: Jari Aalto <jari.aalto@cante.net>
> Date: Sun, 08 Feb 2009 19:32:43 +0200
> Cc: 2235@emacsbugs.donarmstrong.com
> 
> Chong Yidong <cyd@stupidchicken.com> writes:
> 
> >> Please refrain from turning on additional features when "bare bones"
> >> (-Q) program behavior is asked.
> >
> > No, thanks.  The -Q option is largely intended for debugging

Indeed.  This is Emacs, not XEmacs: -Q does not mean "bare bones", it
means "without loading any customization files".

> If the -Q option cannot be changed, please provide separate option which
> turns off colors, something like:
> 
>   --no-colors

This is already available, it's called "--color=never".  Although I
don't understand why you think it will load faster than the default
version.  Care to explain? or is this again based on your experience
with XEmacs?

> 1)  Some programs that parse EDITOR, can't handle embedded quotes and
>     embedded spaces  correctly.

Which ones?

> 3)  The short, self documenting option "--no-colors" and some suitable
>     short option is easier to write.

It's only self-documenting if one reads documentation.  But if one
does read documentation, then one would have known about a no less
self-documenting option "--color".






  reply	other threads:[~2009-02-08 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 15:40 bug#2235: 22.2.1 emacs -Q should not turn on font-lock Chong Yidong
2009-02-08 17:32 ` Jari Aalto
2009-02-08 19:32   ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-08 10:53 Jari Aalto
2009-02-08 11:15 ` Lennart Borgman
2009-02-08 13:32   ` Jari Aalto
2009-02-08 13:44     ` Lennart Borgman
2009-02-08 13:51       ` Jari Aalto
2009-02-08 16:16         ` Kevin Rodgers

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=uskmosp09.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=2235@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=jari.aalto@cante.net \
    /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).