From: henry atting <nospam@literaturlatenight.de>
To: help-gnu-emacs@gnu.org
Subject: Re: define multi-line comments
Date: Sun, 22 Jun 2008 17:43:14 +0200 [thread overview]
Message-ID: <87hcblwk4t.fsf@literaturlatenight.de> (raw)
In-Reply-To: mailman.13696.1214130202.18990.help-gnu-emacs@gnu.org
David Hansen wrote:
> On Sun, 22 Jun 2008 09:51:02 +0200 henry atting wrote:
> [...]
>>
>> Because its only purpose is to highlight direct speech (in my
>> text-mode) it actually works very well.
>
> Are you talking about setting `font-lock-multiline' to `t' and just
> using regexps that may spawn several lines? If it works for you just
> use it, it will save a lot of trouble. But be warned, it's not 100%
> accurate.
With `lazy-lock-mode' it works fine. I can use it all the more it has
not to be 100% reliable.
>> Mmh, with `font-lock-syntactic-keywords' I couldn't get very far. I
>> found this in the manual:
>
> If you describe your problems in a bit more detail someone might be able
> to help.
Much more out of curiosity (or to learn a little) I took the following
example from an old php mode library:
(defconst mytext-font-lock-syntactic-keywords
(list
'("\\(\%\\)"
(1 (11 . nil)))
'("%.*\\([\n]\\)"
(1 (12 . nil)))
))
I expected it to start a comment with `%' and end it on a new line
with `%' But it doesn't work this way.
So as a result of my poor understanding of elisp it may be complete
nonsense.
henry
prev parent reply other threads:[~2008-06-22 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 14:46 define multi-line comments henry atting
2008-06-20 16:01 ` David Hansen
[not found] ` <mailman.13617.1213978108.18990.help-gnu-emacs@gnu.org>
2008-06-21 8:32 ` henry atting
2008-06-21 9:11 ` David Hansen
[not found] ` <mailman.13659.1214040211.18990.help-gnu-emacs@gnu.org>
2008-06-22 7:51 ` henry atting
2008-06-22 10:15 ` David Hansen
[not found] ` <mailman.13696.1214130202.18990.help-gnu-emacs@gnu.org>
2008-06-22 15:43 ` henry atting [this message]
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=87hcblwk4t.fsf@literaturlatenight.de \
--to=nospam@literaturlatenight.de \
--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).