From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64597@debbugs.gnu.org
Subject: bug#64597: mode-line tool inaccessible when window width is small
Date: Sat, 15 Jul 2023 14:10:38 +0000 [thread overview]
Message-ID: <dbubAt_LEvhsHhJZBgwDk_H-cZzVn_N6uswauEWxEc39eNiisjnlh24u4sWkYqvPcUdLKnAmcvdUYxW8YJjWGDRmkiR9nhJDI0MhN8cO8qM=@proton.me> (raw)
In-Reply-To: <83zg3xbalj.fsf@gnu.org>
------- Original Message -------
On Sunday, July 16th, 2023 at 12:52 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 15 Jul 2023 11:41:59 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: Eli Zaretskii eliz@gnu.org, 64597@debbugs.gnu.org
> >
> > Could there be a way to move the lighters around ?
>
>
> There already is: you can change mode-line-format to show the minor
> modes at the beginning of the mode line.
I do not think one has control on the order of the minor modes because
they are run-time dependent. Perhaps the list of lighters could be used
to allow user to change the order. Although I used mode-line-format
playing with it is not a speedy task.
next prev parent reply other threads:[~2023-07-15 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 15:15 bug#64597: mode-line tool inaccessible when window width is small uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 15:56 ` Eli Zaretskii
2023-07-14 21:25 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 6:00 ` Eli Zaretskii
2023-07-15 11:23 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 11:37 ` Eli Zaretskii
2023-07-15 11:41 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 12:52 ` Eli Zaretskii
2023-07-15 14:10 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-15 14:44 ` Eli Zaretskii
2023-07-15 14:48 ` 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
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='dbubAt_LEvhsHhJZBgwDk_H-cZzVn_N6uswauEWxEc39eNiisjnlh24u4sWkYqvPcUdLKnAmcvdUYxW8YJjWGDRmkiR9nhJDI0MhN8cO8qM=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=64597@debbugs.gnu.org \
--cc=eliz@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 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).