From: Hrvoje Niksic <hniksic@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: (font-lock-mode 1) does not always force font-lock
Date: Sat, 25 Oct 2003 11:52:19 +0200 [thread overview]
Message-ID: <m3oew5d4q4.fsf@hniksic.iskon.hr> (raw)
In-Reply-To: <87y8v9epmv.fsf@oak.pohoyda.family> (Alexander Pohoyda's message of "25 Oct 2003 09:35:20 +0200")
Alexander Pohoyda <alexander.pohoyda@gmx.net> writes:
> Hrvoje Niksic <hniksic@xemacs.org> writes:
>
>> > Yes, both cases work. If I comment out (font-lock-mode 1), things
>> > still work.
>>
>> Please repeat the tests with `emacs -q' then.
>
> OK. There is no difference whether the buffer is named "*foo*" or just
> "foo". Both cases work.
I'm afraid you tested the wrong thing. You need to try "*foo*" and
" *foo*", i.e. with and without the leading space in the buffer name.
Whether the buffer name contains asterisks or not is, as you
discovered, irrelevant.
> If I comment out (font-lock-mode 1), both cases does not work: a
> string is not fontified.
There is no use in testing that. The code is not expected to fontify
anything when you remove `(font-lock-mode 1)'.
If you're not sure what to test, you should contact me privately with
your findings, to prevent needless traffic on the development list.
next prev parent reply other threads:[~2003-10-25 9:52 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 [this message]
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=m3oew5d4q4.fsf@hniksic.iskon.hr \
--to=hniksic@xemacs.org \
--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).