From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 58282@debbugs.gnu.org
Subject: bug#58282: Distinguishing glasses-mode display
Date: Tue, 04 Oct 2022 03:36:34 +0000 [thread overview]
Message-ID: <Zt1nnb-hoOWlA8Bwi7YQ4Pgitoj0k7YmjE6sfj2yAQnKTx8lFn9okOfLdoMD6IvExikPVBhRI6PW_lidshprOy1NUY0aYpgdUoYxtCOCZZM=@proton.me> (raw)
I am using "glasses-mode", but It is difficult to distinguish which words get changed. For instance, if one has a mixture of CamelCase, Under_scores one would not know which is modified and which is original. Particularly problematic when one is modifying the code.
Could "glasses-mode" be made in such way as to indicate that "glasses-mode" changed its display, by default.
next reply other threads:[~2022-10-04 3:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 3:36 uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-04 7:18 ` bug#58282: Distinguishing glasses-mode display Eli Zaretskii
2022-10-04 11:01 ` Lars Ingebrigtsen
2022-10-04 11:47 ` Christopher Dimech
2022-10-04 12:27 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 12:43 ` Eli Zaretskii
2022-10-04 14:46 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 14:52 ` Christopher Dimech
2022-10-04 15:53 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 16:28 ` Eli Zaretskii
2022-10-04 16:26 ` Eli Zaretskii
2022-10-04 17:28 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 18:02 ` Eli Zaretskii
2022-10-04 18:09 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 18:16 ` Eli Zaretskii
2022-10-06 0:56 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-06 6:35 ` Eli Zaretskii
2022-10-06 11:53 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='Zt1nnb-hoOWlA8Bwi7YQ4Pgitoj0k7YmjE6sfj2yAQnKTx8lFn9okOfLdoMD6IvExikPVBhRI6PW_lidshprOy1NUY0aYpgdUoYxtCOCZZM=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=58282@debbugs.gnu.org \
--cc=uzibalqa@proton.me \
/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.