unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Words with spaces highlighted in elisp-mode comments
Date: Mon, 17 Jul 2023 12:56:20 +0000	[thread overview]
Message-ID: <y5UzFuKt2f8t9qUGHxTWvrRu2VC15KVz9kTComD6FfZG4KyQ53EI48hX29IPUscMfC0tbOrZnu7n-8khwgUvksv4sMhoGue1ByWeXTVVa3M=@proton.me> (raw)
In-Reply-To: <87edl7h2t6.fsf@dataswamp.org>


------- Original Message -------
On Monday, July 17th, 2023 at 11:08 AM, Emanuel Berg <incal@dataswamp.org> wrote:


> uzibalqa wrote:
> 
> > Currently in elisp-mode
> 
> 
> It is `emacs-lisp-mode', but I agree there should be an
> "elisp-mode" alias. Here:
> 
> (defalias 'elisp-mode #'emacs-lisp-mode)
> 
> https://dataswamp.org/~incal/emacs-init/ide/elisp.el
> 
> > 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.

Consider a line showing usage of a function with a description 
beneath it.  Highlighting the usage code part would help readability. 




  reply	other threads:[~2023-07-17 12:56 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 [this message]
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
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='y5UzFuKt2f8t9qUGHxTWvrRu2VC15KVz9kTComD6FfZG4KyQ53EI48hX29IPUscMfC0tbOrZnu7n-8khwgUvksv4sMhoGue1ByWeXTVVa3M=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.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).