unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: (font-lock-mode 1) does not always force font-lock
Date: 24 Oct 2003 07:22:09 +0200	[thread overview]
Message-ID: <87vfqffbwe.fsf@oak.pohoyda.family> (raw)
In-Reply-To: <m31xt3io3q.fsf@hniksic.iskon.hr>

Hrvoje Niksic <hniksic@xemacs.org> writes:

> > what code tests this?
> 
> I don't have the sources handy.  It seems that the code recognizes
> the buffer as temporary by checking for names that begins with
> space.  For instance, this works (returns t):
> 
> (let ((newbuf (generate-new-buffer "*foo*")))
>   (with-current-buffer newbuf
>     (c-mode)
>     (font-lock-mode 1)
>     (prog1 font-lock-mode
>       (kill-buffer (current-buffer)))))
> 
> Change "*foo*" to " *foo*", and it no longer works, i.e. it returns
> nil.

I have just tested it on recent Emacs and this code always works
(returns t). 


-- 
Alexander Pohoyda <alexander.pohoyda@gmx.net>
PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72  15 54 5F 62 20 23 C6 44

  reply	other threads:[~2003-10-24  5:22 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 [this message]
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
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=87vfqffbwe.fsf@oak.pohoyda.family \
    --to=alexander.pohoyda@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).