From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, 33913@debbugs.gnu.org
Subject: bug#33913: 26.1; Optionally not font-lock newline char when `comment-end' = ""
Date: Sun, 30 Dec 2018 10:23:06 -0800 (PST) [thread overview]
Message-ID: <ec1b1a78-d35e-4628-8358-af54b391e6eb@default> (raw)
In-Reply-To: <5C29048F.8050108@gmx.at>
> > Please consider letting users easily (e.g. user option) not highlight a
> > newline character when it ends a comment, such as in Lisp.
> >
> > The effect should be to highlight only the chars of the line, starting
> > with `comment-start', up to but not including the newline char.
>
> For my private solution to this problem look at the attached file.
Maybe you could fix that up to become a
general replacement, to fix this bug (only)?
But I do think a user option might be good,
or even a non-option variable.
> > (I never would have noticed how annoying the default behavior is if
> > I hadn't tried putting a background color on comments, as the OP
> > did. I don't even think it should be the default behavior to
> > highlight the newline char.)
>
> Fully agreed.
I doubt that such an incompatible change (to
the default) would be accepted immediately.
But a fix for the bug might be.
next prev parent reply other threads:[~2018-12-30 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 22:39 bug#33913: 26.1; Optionally not font-lock newline char when `comment-end' = "" Drew Adams
[not found] ` <mailman.6534.1546123809.1284.bug-gnu-emacs@gnu.org>
2018-12-30 11:51 ` Alan Mackenzie
[not found] ` <mailman.6551.1546170751.1284.bug-gnu-emacs@gnu.org>
2018-12-30 12:33 ` Alan Mackenzie
2018-12-30 17:21 ` Drew Adams
2018-12-30 17:46 ` martin rudalics
2018-12-30 18:23 ` Drew Adams [this message]
2018-12-30 19:00 ` martin rudalics
2019-10-30 19:20 ` Lars Ingebrigtsen
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=ec1b1a78-d35e-4628-8358-af54b391e6eb@default \
--to=drew.adams@oracle.com \
--cc=33913@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).