From: Marcin Borkowski <mbork@mbork.pl>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Colour Capital Letters
Date: Wed, 25 Oct 2023 20:30:09 +0200 [thread overview]
Message-ID: <875y2uimha.fsf@mbork.pl> (raw)
In-Reply-To: <hN1C-w62RuGVXOsjxzYHdSRRHrBROTUEqafKaw0Bjiiq5QmxWAbYPB1Suv4iJqBqy1oXitOvw_FV-U6DVJPJEbRAf08rNoRt-Nx_-oJhBNI=@protonmail.com>
On 2023-10-18, at 21:40, Heime <heimeborgia@protonmail.com> wrote:
> Sent with Proton Mail secure email.
>
> ------- Original Message -------
> On Thursday, October 19th, 2023 at 6:58 AM, Marcin Borkowski <mbork@mbork.pl> wrote:
>
>
>> On 2023-10-02, at 03:58, Heime heimeborgia@protonmail.com wrote:
>>
>> > I want to make a stand alone function that uses a different colour for capital letters
>> > in CamelCase names. Possibly taking code from glasses.el.
>> >
>> > (defun color-camelcase-capital-letters ()
>> > "Color capital letters in CamelCase variables."
>> > (interactive)
>> > (highlight-regexp "\\(?:^\\|\\b\\)[[:upper:]][[:lower:]]*" 'hi-yellow))
>>
>>
>> Just saw this while looking through my email backlog. This is a great
>> idea, but I think it can be made even better. How about using two
>> colors so that subsequent /words/ in CamelCase identifiers are colored
>> differently? I suspect this could be great for readibility!
>>
>> > What can I do ?
>>
>>
>> Do you have any working code? I might be tempted to try to write
>> something like this...
>
> Do not have a working one yet. I wanted to start with something quite
> simple first. But I was planning to get subsequent words colored differently.
>
> The purpose was about readability, particularly for Latex where one cannot use
> underscore '_'.
I looked at glasses.el, and it *already has* that feature! Set
`glasses-separator' to an empty string and `glasses-face' to e.g. 'bold
(the symbol - name of te face). Note: use customize-option.
If you really want to highlight every other subword, not just the
initial letters, check out this proof-of-concept implementation:
https://gitlab.com/-/snippets/3614958 . I plan to blog about it on Nov
11.
Hth,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-10-25 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 1:58 Colour Capital Letters Heime
2023-10-02 10:28 ` Philip Kaludercic
2023-10-18 18:58 ` Marcin Borkowski
2023-10-18 19:40 ` Heime
2023-10-25 18:30 ` Marcin Borkowski [this message]
2023-11-14 19:59 ` Marcin Borkowski
2024-03-31 1:21 ` Heime
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=875y2uimha.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=heimeborgia@protonmail.com \
--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).