From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Customizing the mode line
Date: Sat, 31 Oct 2009 11:00:14 +0100 [thread overview]
Message-ID: <f7ccd24b0910310300w46aba896ve2901b5ecfb6f5ee@mail.gmail.com> (raw)
In-Reply-To: <83bpjodk5g.fsf@gnu.org>
The discussion is centered in making room in the modeline, and that is good.
But I'm also interested in ways to make mode-line customization (from
elisp, not M-x customize) easier. Currently I have things like this in
my .emacs:
(setcar (cdddr (cadadr (cadadr mode-line-client))) (propertize " "
'face 'variable-pitch))
(setf (cadr (assq :propertize mode-line-modes))
'(overwrite-mode
;; etc))
and it ain't pretty (and it is quite fragile, of course).
Perhaps a way to access its content similar to menus could be made to
work; currently, some things are in variables, some are not, and there
are cases where you want to add some tiny thing (like spacing around a
value), and in order to keep the text properties (tooltips, etc)
you've got to copy a bunch of stuff.
Juanma
next prev parent reply other threads:[~2009-10-31 10:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 11:18 Customizing the mode line Eli Zaretskii
2009-10-30 11:28 ` Juanma Barranquero
2009-10-30 13:38 ` Stefan Monnier
2009-10-30 15:15 ` Eli Zaretskii
2009-10-30 16:54 ` Drew Adams
2009-10-30 17:18 ` Eli Zaretskii
2009-10-30 19:12 ` Stefan Monnier
2009-10-30 20:39 ` Eli Zaretskii
2009-10-31 5:16 ` Miles Bader
2009-10-31 8:47 ` Eli Zaretskii
2009-10-31 10:00 ` Juanma Barranquero [this message]
2009-10-31 16:03 ` Drew Adams
2009-10-31 16:29 ` Eli Zaretskii
2009-10-31 17:03 ` Drew Adams
2009-10-31 6:09 ` Manoj Srivastava
2009-10-31 10:31 ` Štěpán Němec
2009-10-31 20:38 ` Scrollbar thumbs (was: Customizing the mode line) Stefan Monnier
2009-11-01 3:11 ` Scrollbar thumbs Miles Bader
2009-11-02 6:55 ` Stefan Monnier
2009-11-02 7:41 ` Jason Rumney
2009-11-02 14:10 ` Stefan Monnier
2009-11-04 16:36 ` Customizing the mode line Evil Boris
2009-10-30 15:01 ` joakim
2009-10-30 15:25 ` Eli Zaretskii
2009-10-30 21:55 ` Stephen Berman
2009-10-30 17:45 ` Chong Yidong
2009-10-30 20:41 ` Eli Zaretskii
2009-10-30 20:56 ` Lennart Borgman
2009-10-31 0:13 ` Stefan Monnier
2009-10-31 5:17 ` Justin Bogner
2009-10-31 5:19 ` Miles Bader
2009-10-31 11:07 ` Richard Stallman
2009-10-31 11:19 ` Juanma Barranquero
2009-11-01 9:28 ` Richard Stallman
2009-11-01 15:21 ` Juanma Barranquero
2009-10-31 11:27 ` Eli Zaretskii
2009-10-31 14:09 ` Robert J. Chassell
2009-10-31 14:30 ` Eli Zaretskii
2009-10-31 22:13 ` Robert J. Chassell
2009-10-31 22:40 ` Robert J. Chassell
2009-11-01 3:49 ` Eli Zaretskii
2009-10-31 18:55 ` Juanma Barranquero
2009-10-31 17:46 ` M Jared Finder
2009-10-31 18:30 ` Eli Zaretskii
2009-10-31 19:02 ` Juanma Barranquero
2009-10-31 14:33 ` Chong Yidong
2009-10-31 15:45 ` Eli Zaretskii
2009-10-31 18:07 ` Chong Yidong
2009-10-31 18:21 ` Eli Zaretskii
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=f7ccd24b0910310300w46aba896ve2901b5ecfb6f5ee@mail.gmail.com \
--to=lekktu@gmail.com \
--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).