unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Alexander Pohoyda <alexander.pohoyda@gmx.net>, emacs-devel@gnu.org
Subject: Re: (font-lock-mode 1) does not always force font-lock
Date: 26 Oct 2003 14:07:31 -0500	[thread overview]
Message-ID: <jwvd6cjom42.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <m3ismcx7j2.fsf@hniksic.iskon.hr>

>> ;; Don't turn on Font Lock mode if we don't have a display (we're running a
>> ;; batch job) or if the buffer is invisible (the name starts with a space).
>> (when (or noninteractive (eq (aref (buffer-name) 0) ?\ ))
>> (setq font-lock-mode nil))

> I propose removing the buffer-name check, at least when the argument
> to font-lock-mode is positive.

I always thought that the whole thing should be removed (i.e. including the
noninteractive check: after all, you might want to use it in batch with
ps-print or htmlize), but I never cared enough to try and convince the
rest of the developers.
So for what it's worth, I completely agree,


        Stefan

  reply	other threads:[~2003-10-26 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3smlkygno.fsf@hniksic.iskon.hr>
2003-10-23 18:38 ` (font-lock-mode 1) does not always force font-lock Richard Stallman
2003-10-23 22:30   ` Hrvoje Niksic
2003-10-24  5:22     ` Alexander Pohoyda
2003-10-24  9:49       ` Hrvoje Niksic
2003-10-24 19:12         ` Alexander Pohoyda
2003-10-24 20:15           ` Hrvoje Niksic
2003-10-25  7:35             ` Alexander Pohoyda
2003-10-25  9:52               ` Hrvoje Niksic
2003-10-26 11:32                 ` Alexander Pohoyda
2003-10-26 16:56                   ` Hrvoje Niksic
2003-10-26 19:07                     ` Stefan Monnier [this message]
2003-10-27 23:44                       ` Richard Stallman
2003-10-28 22:09                         ` Alexander Pohoyda
2003-11-18 21:13                         ` Alexander Pohoyda

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=jwvd6cjom42.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    --cc=alexander.pohoyda@gmx.net \
    --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).