From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Words with spaces highlighted in elisp-mode comments
Date: Sat, 22 Jul 2023 15:49:46 +0200 [thread overview]
Message-ID: <trinity-a8e860a1-ac24-476c-aca2-98c7f762b5a0-1690033785989@3c-app-mailcom-bs03> (raw)
In-Reply-To: <83pm4k887q.fsf@gnu.org>
> Sent: Sunday, July 23, 2023 at 12:02 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Words with spaces highlighted in elisp-mode comments
>
> > From: Emanuel Berg <incal@dataswamp.org>
> > Date: Sat, 22 Jul 2023 08:00:30 +0200
> >
> > uzibalqa wrote:
> >
> > >> But comments are already font locked into
> > >> `font-lock-comment-face' (there is also a`
> > >> font-lock-comment-delimiter-face', IMO it is overkill to
> > >> have that in another color than `font-lock-comment-face').
> > >
> > > I do not see the usefulness of coloring the comment
> > > delimiter separately (because that affects all comments in
> > > the same way, no distinguishing feature whatsoever ).
> >
> > Indeed, I think all comments should be of the same color,
> > including the delimiters.
>
> Font-lock is not just about colors, so this feature is still useful.
What feature is useful ? Highlighting comment-delimiter with a different colour ?
I agree with Emanuel, Why would one use another color than `font-lock-comment-face'
for `comment-delimiter' ?
next prev parent reply other threads:[~2023-07-22 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 22:49 Words with spaces highlighted in elisp-mode comments uzibalqa
2023-07-16 23:08 ` Emanuel Berg
2023-07-17 12:56 ` uzibalqa
2023-07-17 15:13 ` [External] : " Drew Adams
2023-07-19 1:02 ` Emanuel Berg
2023-07-20 11:47 ` uzibalqa
2023-07-22 6:00 ` Emanuel Berg
2023-07-22 12:02 ` Eli Zaretskii
2023-07-22 13:49 ` Christopher Dimech [this message]
2023-07-22 14:16 ` Eli Zaretskii
2023-07-22 14:22 ` Heime
2023-07-22 14:33 ` Eli Zaretskii
2023-07-24 12:18 ` Emanuel Berg
2023-07-22 13:21 ` uzibalqa
2023-07-24 12:13 ` Emanuel Berg
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=trinity-a8e860a1-ac24-476c-aca2-98c7f762b5a0-1690033785989@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).