unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Arjan Bos <Arjan.Bos@icu.nl>
Subject: Re: syntax table entries for comments
Date: Thu, 11 Sep 2003 07:48:00 +0200	[thread overview]
Message-ID: <3F600C90.7020506@icu.nl> (raw)
In-Reply-To: <jwv8yowsn17.fsf@noir.iro.umontreal.ca>

Stefan Monnier wrote:

<snip>code snippet</snip>

>>Could you please enlighten me as to why your way is better? I'm no (e)lisp
>>expert, but I'm doing allright with a bit of voodoo programming[1].
> 
> 
> Advantages are:
> - shorter.
> - less memory used since the code that sets up the table can be discarded
>   after the table is setup, whereas in your case, the function
>   nrx-create-syntax-table needs to be kept around in case someone wants
>   to call it.
> - no temporary stage where nrx-mode-syntax-table holds a value that is
>   not a syntax-table (or that is a syntax-table but that is not yet
>   properly initialized): either it's there and initialized or it's not
>   there at all.

Sounds good to me, thanks!

> 
> 
<snip/>

>>
>>I tried the latter, but then strings within the `--' comment will undo the
>>comment highlighting.
> 
> 
> I suspect you used font-lock-keywords rather than
> font-lock-syntactic-keywords.
You're right, I'll look up the docs for that then.

> 
> 
>>So I'll try to voodoo hack src/syntax.c
> 
> 
> That would be wonderful.
> 
Don't get your hopes up to high yet. The amount of constants in syntax.c 
and my lack of c knowlegde will make this hard. (Were it COBOL though... 
:-). I do happen to have a fairly recent CVS snapshot though, so I'll 
try it.

Arjan

      reply	other threads:[~2003-09-11  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08  5:39 syntax table entries for comments Arjan Bos
2003-09-09 13:34 ` Stefan Monnier
2003-09-10 13:35   ` Arjan Bos
2003-09-10 15:04     ` Stefan Monnier
2003-09-11  5:48       ` Arjan Bos [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=3F600C90.7020506@icu.nl \
    --to=arjan.bos@icu.nl \
    /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).