all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Words with spaces highlighted in elisp-mode comments
Date: Sat, 22 Jul 2023 08:00:30 +0200	[thread overview]
Message-ID: <87tttwfptt.fsf@dataswamp.org> (raw)
In-Reply-To: 8ADlKavHDtxrJCESAqF033FMxAQWk1LFM6_dZHM59eCWdqWQBo_xoke12JrquaHDv90D9rAbLj-KQGJUEMiHaVUqv2ko6VDxPoj6UWV_5tE=@proton.me

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.

> We can keep highlighting with a back-quote for things that
> can be evaluated (e.g. `something')

Agreed, that is the exception that proves the rule. I could
also think of hyperlinking them to the help, as has been
suggested not that long ago. In ERC it is already like that
BTW, and here is some more work on that:

  https://dataswamp.org/~incal/emacs-init/erc/erc-man.el

  https://dataswamp.org/~incal/emacs-init/erc/erc-show-modes.el

But putting point at the beginning of `something' and doing
`C-h f' isn't that much of a deal, which is the reason I think
no one has cared about it enough to do it.

But I like all integration things, big and small, so why not.
Here it should be noted that they already get
`font-lock-constant-face', if it sounds here like nothing at
all happens to the poor things.

> and use single-quote for more general case that allows
> spaces (e.g. 'this and that').

But what do that express? What's the intended usage? Can you
provide a piece of Elisp, where you use that proposed syntax
for us to see?

> We should not use multiple comment characters (e.g. ;;;
> Something) because those are for outlines - something of
> a completely different orthogonal purpose.

As long as it has a purpose, it can be font locked in
a distinguished way. If it should, in this case, is another
thing, but it could, and it wouldn't be wrong to do. But if it
should, I don't know, especially since comments in a uniform
color simply looks  much better.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2023-07-22  6:00 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tttwfptt.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.