From: Lennart Borgman <lennart.borgman@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: C Mode: acceleration in brace deserts.
Date: Fri, 4 Dec 2009 13:03:28 +0100 [thread overview]
Message-ID: <e01d8a50912040403i2c6d264y4c0b9a5cd2c1cac6@mail.gmail.com> (raw)
In-Reply-To: <20091204115605.GB1456@muc.de>
On Fri, Dec 4, 2009 at 12:56 PM, Alan Mackenzie <acm@muc.de> wrote:
> On Fri, Dec 04, 2009 at 12:03:27PM +0100, Lennart Borgman wrote:
>> On Fri, Dec 4, 2009 at 11:34 AM, Lennart Borgman
>
>> Just a question I forgot: Why are you not using syntax-ppss here
>> [keeping track of comments/strings in c-parse-state's supporting
>> functions]? Are you not looking for the same thing (ie inside comment
>> or string).
>
> I think at the time I did it, it was just less work to write it from
> scratch. syntax-ppss isn't a well encapsulated system, and it almost
> requires its users to read its source code to see exactly what it does.
> Also, c-parse-state (in effect) changes the syntax table in use by
> setting category properties. At the time, I was considering actually
> changing the syntax table (for reasons I'm not entirely clear about any
> more). Does syntax-ppss exist in XEmacs, and if so, since when? Some of
> syntax-ppss's supporting infrastructure only came into existence after
> syntax-ppss itself.
>
>> If you did it that way then it would already be supported by MuMaMo.
>
> Ah. That sounds like a good reason to change my new code to use
> syntax-ppss. :-( But not before the first pretest release next week.
Thanks. ;-)
Would it be enough to change c-state-literal-at? Perhaps you could
send me a new version of that so I could test it in that case. I could
just defadvice c-state-literal-at.
next prev parent reply other threads:[~2009-12-04 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 16:21 C Mode: acceleration in brace deserts Alan Mackenzie
2009-12-03 16:26 ` Lennart Borgman
2009-12-03 16:59 ` Alan Mackenzie
2009-12-03 17:22 ` Lennart Borgman
2009-12-03 19:39 ` Alan Mackenzie
2009-12-03 19:57 ` Lennart Borgman
2009-12-04 10:34 ` Lennart Borgman
2009-12-04 11:03 ` Lennart Borgman
2009-12-04 11:56 ` Alan Mackenzie
2009-12-04 12:03 ` Lennart Borgman [this message]
2009-12-04 12:18 ` Lennart Borgman
2009-12-04 13:54 ` Alan Mackenzie
2009-12-04 19:03 ` Lennart Borgman
2009-12-05 2:11 ` Lennart Borgman
2009-12-05 4:49 ` Stefan Monnier
2009-12-04 5:31 ` Richard Stallman
2009-12-04 11:37 ` Alan Mackenzie
2009-12-05 6:50 ` Richard Stallman
2009-12-03 17:09 ` Stefan Monnier
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=e01d8a50912040403i2c6d264y4c0b9a5cd2c1cac6@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=acm@muc.de \
--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).