From: "T.V Raman" <raman@google.com>
To: contovob@tcd.ie
Cc: eliz@gnu.org, raman@google.com, emacs-devel@gnu.org
Subject: Re: Feature Request: Ability to Tweak "/l" in mode-name
Date: Wed, 8 Feb 2023 07:17:33 -0800 [thread overview]
Message-ID: <25571.48397.821189.277557@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <87a61o8hmb.fsf@tcd.ie>
Your solution works for me, though at some nit-level, Emacs
hard-wiring the "/l" and "/d" is likely going to make it harder to
internationalize -- but that is the least of my or emacs' problems:-)
Basil L. Contovounesios writes:
> Eli Zaretskii [2023-02-08 14:04 +0200] wrote:
>
> >> From: "T.V Raman" <raman@google.com>
> >> Date: Tue, 7 Feb 2023 19:57:21 -0800
> >>
> >> At present the "/l" vs "/d" for lexical vs dynamic scoping is
> >> hard-wired in the definition of emacs-lisp-mode; Could we make this
> >> configurable?
> >
> > Do we offer customization of the mode lighter in any other modes?
>
> Some modes expose the mode lighter as a user option,
> e.g. flymake-mode-line-lighter. I suspect fewer do so in emacs.git than
> in the wider ecosystem.
>
> > You can always customize any part of the mode line directly, by
> > changing mode-line-format or its portions, so I'm unsure why we would
> > need yet another knob, and in this specific case in particular.
>
> FWIW I use delight from GNU ELPA for this purpose, e.g.:
>
> (delight
> '((emacs-lisp-mode "(ε)" :major)
> (lisp-interaction-mode "(ι)" :major)))
>
> --
> Basil
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2023-02-08 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 3:57 Feature Request: Ability to Tweak "/l" in mode-name T.V Raman
2023-02-08 12:04 ` Eli Zaretskii
2023-02-08 12:30 ` Basil L. Contovounesios
2023-02-08 15:17 ` T.V Raman [this message]
2023-02-08 15:22 ` T.V Raman
2023-02-09 11:17 ` Basil L. Contovounesios
2023-02-09 15:22 ` T.V Raman
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=25571.48397.821189.277557@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).