From: Bozhidar Batsov <bozhidar.batsov@gmail.com>
To: Matthias Meulien <orontee@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Mode line strings for sub- and super- minor modes are counterintuitive
Date: Fri, 15 Aug 2014 08:45:36 +0300 [thread overview]
Message-ID: <etPan.53ed9e80.7c83e458.d691@bozhidar-mini.local> (raw)
In-Reply-To: <87d2c23jqz.fsf_-_@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
I totally agree - such lighters are quite confusing. I think the practice of using punctuation characters only for minor-mode lighters should be discouraged.
—
Cheers,
Bozhidar
On August 14, 2014 at 23:21:51, Matthias Meulien (orontee@gmail.com) wrote:
When subword (resp. superword) minor mode is enabled, a comma
(resp. a superscript two) is displayed in the mode line. I found
those two characters difficult to see and meaning less.
I understand that there's not much space in the mode line but
other minor modes are much verbose (eg. MML, Abbrev, Fill, Narrow,
Outl, etc). Why subword and superword modes have this special
treatment?
I suggest to use Subw and Supw for the user to have a chance to
link the mode line string to the full minor mode.
–
Matthias
[-- Attachment #2: Type: text/html, Size: 1575 bytes --]
prev parent reply other threads:[~2014-08-15 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 0:25 [PATCH] Custom option to turn Flyspell mode on in prog modes Matthias Meulien
2013-12-09 13:28 ` Rüdiger Sonderfeld
2013-12-11 23:17 ` Matthias Meulien
2014-01-07 19:23 ` Glenn Morris
2014-01-07 19:30 ` Glenn Morris
2014-08-08 13:59 ` Rüdiger Sonderfeld
2014-08-08 23:45 ` Juri Linkov
2014-08-14 12:46 ` Sebastien Vauban
2013-12-11 23:17 ` bug#16394: " Matthias Meulien
2014-08-08 14:10 ` Rüdiger Sonderfeld
2014-08-14 20:21 ` Mode line strings for sub- and super- minor modes are counterintuitive Matthias Meulien
2014-08-15 5:45 ` Bozhidar Batsov [this message]
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=etPan.53ed9e80.7c83e458.d691@bozhidar-mini.local \
--to=bozhidar.batsov@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=orontee@gmail.com \
/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.