GNU bug report logs -
#13156
dedicated face for parentheses in lisp modes
Previous Next
Reported by: Jonas Bernoulli <jonas <at> bernoul.li>
Date: Wed, 12 Dec 2012 12:21:02 UTC
Severity: wishlist
Tags: wontfix
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13156 in the body.
You can then email your comments to 13156 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Wed, 12 Dec 2012 12:21:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jonas Bernoulli <jonas <at> bernoul.li>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 12 Dec 2012 12:21:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello
Could you please add a `paren-face' that could be used in lisp modes
(and possibly others) to dim (or highlight) parentheses. I am currently
using the attached library to do this but think it would make sense if
this functionality was built-in.
Being very simple `parenface.el' just unconditionally adds an additional
keyword to `[lisp|scheme]-font-lock-keywords' when loaded.
I see two ways of implementing this as part of Emacs.
1. Add the keyword to `[lisp|scheme]-font-lock-keywords-2' directly and
let `paren-face' inherit from `default'. Users who actually want
parens to be dimmed or highlight can then customize the former.
2. Define a local minor mode that adds the additional keywords.
I would prefer (1) but maybe that is not an option because it might
negatively affects font-lock's performance.
If this has to be a mode then I am happy to write it. I haven't done
so yet because `parenface.el' works fine for me and because I would
actually prefer (1).
Thanks for considering,
Jonas
[parenface.el (application/emacs-lisp, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Tue, 18 Dec 2012 15:35:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 13156 <at> debbugs.gnu.org (full text, mbox):
> Could you please add a `paren-face' that could be used in lisp modes
> (and possibly others) to dim (or highlight) parentheses. I am currently
> using the attached library to do this but think it would make sense if
> this functionality was built-in.
I don't think it's sufficiently useful in general.
> Being very simple `parenface.el' just unconditionally adds an additional
> keyword to `[lisp|scheme]-font-lock-keywords' when loaded.
It could use font-lock-add-keywords.
BTW, if all parens are displayed the same, then you can also use the
buffer-display-table.
> If this has to be a mode then I am happy to write it. I haven't done
> so yet because `parenface.el' works fine for me and because I would
> actually prefer (1).
Having it as a separate mode would make more sense, yes.
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Wed, 19 Dec 2012 15:47:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 13156 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier writes:
>> Could you please add a `paren-face' that could be used in lisp modes
>> (and possibly others) to dim (or highlight) parentheses. I am currently
>> using the attached library to do this but think it would make sense if
>> this functionality was built-in.
>
> I don't think it's sufficiently useful in general.
What about all the Emacs users that are scared of lisp "because of all
the parens"? Dimming them might reduce the shock :-)
>> Being very simple `parenface.el' just unconditionally adds an additional
>> keyword to `[lisp|scheme]-font-lock-keywords' when loaded.
>
> It could use font-lock-add-keywords.
That's what I was going to do.
> BTW, if all parens are displayed the same, then you can also use the
> buffer-display-table.
Since you are suggesting this I assume that doesn't mess with
highlighting with highlighting matching parens. So I will try that too.
>> If this has to be a mode then I am happy to write it. I haven't done
>> so yet because `parenface.el' works fine for me and because I would
>> actually prefer (1).
>
> Having it as a separate mode would make more sense, yes.
If you don't change your mind about this not being sufficiently useful
to be built-in, then I will do write a mode; eventually.
Jonas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Wed, 19 Dec 2012 16:20:01 GMT)
Full text and
rfc822 format available.
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
just for completeness do I want to mention "RainbowDelimiters" here:
http://www.emacswiki.org/emacs/RainbowDelimiters
It is a generalization of what you want. It is also suitable of
reducing deterrence of Lisp, and it helps reading LISP code a lot,
without losing anything.
If anything like that should be built-in, then I would vote for that
package.
Regards,
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Wed, 19 Dec 2012 18:28:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 13156 <at> debbugs.gnu.org (full text, mbox):
> just for completeness do I want to mention "RainbowDelimiters" here:
I'd be happy to see this package in GNU ELPA. If someone could take
care of tracking down the copyright assignments...
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Fri, 21 Dec 2012 14:29:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 13156 <at> debbugs.gnu.org (full text, mbox):
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> > just for completeness do I want to mention "RainbowDelimiters" here:
>
> I'd be happy to see this package in GNU ELPA. If someone could take
> care of tracking down the copyright assignments...
Does he just have to sign the copyright papers (normal procedure), or is
something special needed for Elpa? If the first is true, I volunteer to
contact the author.
Regards,
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Sat, 22 Dec 2012 15:59:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 13156 <at> debbugs.gnu.org (full text, mbox):
> Does he just have to sign the copyright papers (normal procedure), or is
> something special needed for Elpa?
From a copyright point of view, we treat GNU ELPA as being part of
Emacs, so it's the exact same paperwork (where the project name is
"Emacs"). This is so that we can easily move code between Emacs and
GNU ELPA.
> If the first is true, I volunteer to contact the author.
Thank you,
Stefan
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Mon, 24 Dec 2012 13:45:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 13156 <at> debbugs.gnu.org (full text, mbox):
> > I volunteer to contact the author.
Done. I'll tell you when I got an answer.
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Fri, 18 Jan 2013 02:24:02 GMT)
Full text and
rfc822 format available.
Message #29 received at submit <at> debbugs.gnu.org (full text, mbox):
> > If the first is true, I volunteer to contact the author.
I wrote a message to the address given in the file header, but did not
receive any answer until now, sorry. No idea how to contact him
otherwise.
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Tue, 15 Oct 2013 18:30:03 GMT)
Full text and
rfc822 format available.
Message #32 received at 13156 <at> debbugs.gnu.org (full text, mbox):
Hello,
> > Does he just have to sign the copyright papers (normal procedure), or is
> > something special needed for Elpa?
>
> From a copyright point of view, we treat GNU ELPA as being part of
> Emacs, so it's the exact same paperwork (where the project name is
> "Emacs"). This is so that we can easily move code between Emacs and
> GNU ELPA.
>
> > If the first is true, I volunteer to contact the author.
Great news! I've now contact with the author, and he is willing to sign
the papers. We will tell you when it's done.
Regards,
Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#13156
; Package
emacs
.
(Wed, 27 Aug 2014 22:47:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 13156 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> Great news! I've now contact with the author, and he is willing to sign
> the papers. We will tell you when it's done.
I'm very sorry, but he told me now that he wont sign the papers.
Michael.
Added tag(s) wontfix.
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Mon, 12 Aug 2019 01:06:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Stefan Kangas <stefan <at> marxist.se>
:
You have taken responsibility.
(Mon, 12 Aug 2019 01:06:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jonas Bernoulli <jonas <at> bernoul.li>
:
bug acknowledged by developer.
(Mon, 12 Aug 2019 01:06:03 GMT)
Full text and
rfc822 format available.
Message #42 received at 13156-done <at> debbugs.gnu.org (full text, mbox):
tags 13156 + wontfix
thanks
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>> Could you please add a `paren-face' that could be used in lisp modes
>> (and possibly others) to dim (or highlight) parentheses. I am currently
>> using the attached library to do this but think it would make sense if
>> this functionality was built-in.
>
> I don't think it's sufficiently useful in general.
Since this was rejected in 2012, I'm closing it as wontfix.
If anyone disagrees with that, feel free to reopen.
Thanks,
Stefan Kangas
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 09 Sep 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 202 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.