From: Drew Adams <drew.adams@oracle.com>
To: 16114@debbugs.gnu.org
Subject: bug#16114: 24.3.50; wishlist (enhancement request): easier way for users to customize mode lines
Date: Wed, 11 Dec 2013 09:47:01 -0800 (PST) [thread overview]
Message-ID: <fb843f8b-1455-4a25-82a9-09f340b71004@default> (raw)
In-Reply-To: <0bfef262-9c3d-4538-a75f-eba7df4b29a5@default>
This bug was merged with bug #4833.
I disagree with the formulation of bug #4833, or at least its characterization as having to do with customization. Whether
or not the mode line is sufficiently ergonomic is different
question from whether it is easy enough for users to modify.
There is no need to make this into an all-inclusive
refashion-the-universe request.
Plus, the difficulty of customization is tacked onto the end of
bug #4833, seemingly as an afterthought ("What's more...").
The bulk of that bug report is about the makeup of the mode line
not being sufficiently ergonomic.
Leave it at that; split these two enhancement requests: one for
easier customizing, another for better ergonomics. If they both
get worked on (together or in either order) then any interplay
between them can be taken into account at that time.
Bug #16114 should be limited to trying to make it easier for
users to modify mode lines. Another enhancement request (e.g.
#4833) can address possible ergonomic improvements.
No specific ergonomic improvements were proposed in bug #4833
anyway (just complaints about length and relative positions,
AFAICT, which is OK), so that wish is fairly unspecified.
Glomming even more onto the same enhancement request is silly,
and it just makes it all the more likely that nothing will ever
be done to improve things (in regard to either customization or
ergonomics). Easier customization is already a big enough job.
prev parent reply other threads:[~2013-12-11 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:18 bug#16114: 24.3.50; wishlist (enhancement request): easier way for users to customize mode lines Drew Adams
2013-12-11 17:47 ` Drew Adams [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
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=fb843f8b-1455-4a25-82a9-09f340b71004@default \
--to=drew.adams@oracle.com \
--cc=16114@debbugs.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).