From: Tassilo Horn <tassilo@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Font-Locking for Allout Mode
Date: Fri, 09 Mar 2007 00:18:42 +0100 [thread overview]
Message-ID: <87k5xrl3xp.fsf@baldur.tsdh.de> (raw)
In-Reply-To: mailman.687.1173393945.7795.help-gnu-emacs@gnu.org
Stephen Berman <Stephen.Berman@gmx.net> writes:
Hi Stephen,
> I meant you should add the file local variable `mode: allout' to a
> file you are visiting in the major mode Text Mode. However, if the
> file you are visiting in Text Mode is ~/.emacs, presumably your allout
> headings beginning with `;;;_' and if so, they won't match
> allout-regexp for Text Mode, so won't get fontified.
Indeed, I forgot about the different regexps. :)
> Try saving the following as `allout-test.txt'; I would be surprised,
> and mystified, if you still don't see the fontification.
>
> * test
> .. test
> test
> . , test
> test
> . . test
> . , test
> . . test
> test
> . , test
> . . test
> . , test
>
> * file local variables list
> Local variables:
> allout-layout: (+ :)
> mode: allout
> End:
Wow, it works! And really, the "mode: allout" is required. But it still
doesn't work with emacs lisp files regardless of the presence of the
"mode: allout"...
> In my allout.el (2.2.1) the docstring of allout-init ends:
>
> "To prime your Emacs session for full auto-outline operation, include
> the following two lines in your Emacs init file:
>
> (require 'allout)
> (allout-init t)"
>
> Since you have it in yours, I'm at a loss to explain the different
> behaviors you and I are observing.
Does fontification work for you in elisp files?
Bye,
Tassilo
--
People say that if you play Microsoft CD's backwards, you
hear satanic things, but that's nothing, because if you
play them forwards, they install Windows.
next prev parent reply other threads:[~2007-03-08 23:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 20:07 Font-Locking for Allout Mode Tassilo Horn
2007-03-08 13:23 ` Stephen Berman
[not found] ` <mailman.654.1173360249.7795.help-gnu-emacs@gnu.org>
2007-03-08 14:03 ` Tassilo Horn
2007-03-08 16:06 ` Stephen Berman
[not found] ` <mailman.663.1173370034.7795.help-gnu-emacs@gnu.org>
2007-03-08 16:42 ` Tassilo Horn
2007-03-08 22:38 ` Peter Dyballa
2007-03-08 22:45 ` Stephen Berman
[not found] ` <mailman.686.1173393546.7795.help-gnu-emacs@gnu.org>
2007-03-08 22:49 ` Tassilo Horn
[not found] ` <mailman.687.1173393945.7795.help-gnu-emacs@gnu.org>
2007-03-08 23:18 ` Tassilo Horn [this message]
2007-03-09 11:28 ` Stephen Berman
[not found] ` <mailman.704.1173439750.7795.help-gnu-emacs@gnu.org>
2007-03-09 14:27 ` Tassilo Horn
2007-03-09 16:50 ` Stephen Berman
2007-03-11 15:07 ` Stephen Berman
2007-03-09 20:36 ` Stefan Monnier
2007-03-09 21:44 ` Tassilo Horn
2007-03-09 23:34 ` Stephen Berman
2007-03-09 23:47 ` Stephen Berman
2007-03-11 15:07 ` Stephen Berman
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=87k5xrl3xp.fsf@baldur.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=help-gnu-emacs@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.
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).