From: "A. Soare" <alinsoar@voila.fr>
To: emacs-devel@gnu.org
Cc: rms@gnu.org
Subject: Re: New paren matching feature request
Date: Thu, 29 Jan 2009 17:04:10 +0100 (CET) [thread overview]
Message-ID: <31628377.61031233245050005.JavaMail.www@wwinf4614> (raw)
>
> Message: 9
> Date: Thu, 29 Jan 2009 09:31:44 -0500
> From: Richard M Stallman <rms@gnu.org>
> Subject: New paren matching feature request
> To: emacs-devel@gnu.org
> Message-ID: <E1LSXvk-0001Ei-ED@fencepost.gnu.org>
> Content-Type: text/plain; charset=ISO-8859-15
>
> Date: Wed, 28 Jan 2009 06:53:31 +0100 (CET)
> Subject: Re: Happy Chinese New Year!
> From: hf@hongfeng.ch
> To: rms@gnu.org
>
> what I meant is to use different colors for nested parentheses of
> Lisp code, indicating the hierarchy or the layers, e.g. the outermost
> parentheses displayed in red, while the innermost one is violet.
> We can try the solar spectrum for them.
>
>
If you remember, a few months ago I have written an automaton that in one for-loop over a sexp; it returned a list of the correct indentation for that sexp. It also can return a list of the positions and the deep-level of every sexp. More that that, I have said then that it is identically to the automaton from `parse-partial-sexp`. I have told then that my code can be used to colorize all the paranthesis into a different color depending of the level.
I do not understand why nobody considered my code. Otherwise I could have re-writen it in C and included in parse-partial-sexp, and this one could have returned information about indentation too.
____________________________________________________
Écoutez en un clic votre musique préférée et découvrez de nouveaux titres en affinité avec vos goûts sur http://musiline.voila.fr
next reply other threads:[~2009-01-29 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 16:04 A. Soare [this message]
2009-01-30 7:25 ` New paren matching feature request Richard M Stallman
2009-01-31 1:39 ` Stefan Monnier
2009-02-01 6:31 ` Richard M Stallman
2009-02-01 21:38 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-02-02 17:40 A. Soare
2009-02-02 0:19 A. Soare
2009-02-01 23:56 A. Soare
2009-02-01 21:12 A. Soare
2009-02-01 23:42 ` Thien-Thi Nguyen
2009-02-01 11:37 A. Soare
2009-02-01 2:30 A. Soare
2009-02-01 18:44 ` Thien-Thi Nguyen
2009-01-31 2:16 A. Soare
2009-02-01 1:09 ` Thien-Thi Nguyen
2009-01-31 1:48 A. Soare
2009-01-31 21:33 ` Stefan Monnier
2009-02-01 6:31 ` Richard M Stallman
2009-01-29 14:31 Richard M Stallman
2009-01-29 21:50 ` Thorsten Bonow
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=31628377.61031233245050005.JavaMail.www@wwinf4614 \
--to=alinsoar@voila.fr \
--cc=emacs-devel@gnu.org \
--cc=rms@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).