From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Words with spaces highlighted in elisp-mode comments
Date: Wed, 19 Jul 2023 03:02:58 +0200 [thread overview]
Message-ID: <87wmywg1bx.fsf@dataswamp.org> (raw)
In-Reply-To: y5UzFuKt2f8t9qUGHxTWvrRu2VC15KVz9kTComD6FfZG4KyQ53EI48hX29IPUscMfC0tbOrZnu7n-8khwgUvksv4sMhoGue1ByWeXTVVa3M=@proton.me
uzibalqa wrote:
>>> comments, words within single quotes get highlighted.
>>> It would be beneficial if arbitrary text is also
>>> highlighted within single quotes (e.g. text with spaces).
>>
>> I don't understand what 'ooh' and 'ooh aah' means in Elisp,
>> do you?
>>
>> But it is clear the oohs and the aahs are treated
>> differently by Emacs as 'ooh' gets the
>> `font-lock-constant-face' and with the whitespace, as you
>> say, it doesn't.
>>
>> You can evaluate 'ooh' (into ooh) but not use it in code,
>> 'ooh aah' cannot be evaluated.
>
> Highlighting some text in comments would be beneficial.
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 don't see why 'ooh' within a comment should be colorized any
other way than the comment, since that syntax don't denote
anything in Elisp. If you intend to use it as labels, and to
put them aside as a special color, I'd say there are better
ways to do that, namely stack semi-colons in different numbers
denoting different things, so that, for example
;; this is a general comment <-- one face
(setq one 1) ; don't do that <-- comment that refers to one line
;;; this is a LABEL, as seen in Lisp packages <-- one face for that
(code (code ...)
(code (code ...)
This would also be safe to implement because if someone didn't
like it, it could be default be set so that all those Lisp
levels of comments initially were set to the same color.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-07-19 1:02 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 [this message]
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
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=87wmywg1bx.fsf@dataswamp.org \
--to=incal@dataswamp.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).