all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: 2235@emacsbugs.donarmstrong.com
Subject: bug#2235: 22.2.1 emacs -Q should not turn on font-lock
Date: Sun, 8 Feb 2009 14:44:28 +0100	[thread overview]
Message-ID: <e01d8a50902080544h6b84e209w9a1eeebe0fe6357@mail.gmail.com> (raw)
In-Reply-To: <87bptdxddg.fsf@jondo.cante.net>

On Sun, Feb 8, 2009 at 2:32 PM, Jari Aalto <jari.aalto@cante.net> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> On Sun, Feb 8, 2009 at 11:53 AM, Jari Aalto <jari.aalto@cante.net> wrote:
>>
>>>  emacs -Q  README
>>>
>>> On a white terminal[1], the results are unreadable. Please deactivate
>>> font-lock when --no-site-file (as in -Q) option is specified.
>>
>> Seems to me like it is better to fix the colors used.
>
> That's good, but is only secondary problem.
>
> Please refrain from turning on additional features when "bare bones"
> (-Q) program behavior is asked.

Font lock mode is on by default since Emacs 22.

If you want "bare bones" you can perhaps use fundamental-mode in Emacs.






  reply	other threads:[~2009-02-08 13:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvy6wgy90s.fsf-monnier+emacsbugreports@gnu.org>
2009-02-08 10:53 ` bug#2235: 22.2.1 emacs -Q should not turn on font-lock Jari Aalto
2009-02-08 11:15   ` Lennart Borgman
2009-02-08 13:32     ` Jari Aalto
2009-02-08 13:44       ` Lennart Borgman [this message]
2009-02-08 13:51         ` Jari Aalto
2009-02-08 16:16           ` Kevin Rodgers
2009-02-08 20:30   ` bug#2235: marked as done (22.2.1 emacs -Q should not turn on font-lock) Emacs bug Tracking System
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

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e01d8a50902080544h6b84e209w9a1eeebe0fe6357@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=2235@emacsbugs.donarmstrong.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.