From: Eli Zaretskii <eliz@gnu.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: dimech@gmx.com, 58282@debbugs.gnu.org
Subject: bug#58282: Distinguishing glasses-mode display
Date: Tue, 04 Oct 2022 21:16:44 +0300 [thread overview]
Message-ID: <834jwjv4hf.fsf@gnu.org> (raw)
In-Reply-To: <99xitOu83kpIWgFvyzyVed04AAl2JEN4tMQvxP2zDw0PmAxIk0oZQ2Z-cbBhRv_SW4hFMI0PfbcXtlHTphED2jHSuTW9Phx1MQw6ki7YXdk=@proton.me> (message from uzibalqa on Tue, 04 Oct 2022 18:09:53 +0000)
> Date: Tue, 04 Oct 2022 18:09:53 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: dimech@gmx.com, 58282@debbugs.gnu.org
>
> > You cannot simply assign the value to this variable. Look at its
> > defcustom form to understand what is missing.
> >
> > And anyway, what does this have to do with the bug report? You are
> > asking basic Emacs Lisp questions.
>
> Because I can use utf, I can easily distinguish between code and glasses display.
> This feature solves my problem.
So do use it. It is possible and supported, just not by a simple
setq.
Here's the defcustom of that option from glasses.el:
(defcustom glasses-separator "_"
"String to be displayed as a visual separator in identifiers.
It is used both for adding missing separators and for replacing separators
defined by `glasses-original-separator'. If you don't want to add missing
separators, set `glasses-separator' to an empty string. If you don't want to
replace existent separators, set `glasses-original-separator' to an empty
string."
:type 'string
:set 'glasses-custom-set
:initialize 'custom-initialize-default)
What does the :set attribute tell you?
next prev parent reply other threads:[~2022-10-04 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 3:36 bug#58282: Distinguishing glasses-mode display uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 7:18 ` 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 [this message]
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=834jwjv4hf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58282@debbugs.gnu.org \
--cc=dimech@gmx.com \
--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.