From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: menubar Commands Hide Signature vs. mode-line
Date: Sat, 29 Dec 2001 22:42:09 +0100 [thread overview]
Message-ID: <vafr8pd1z66.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3wuz6pacb.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 29 Dec 2001 11:52:20 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> At present, they are generated by the `gnus-article-wash-status'
> function, which just returns a string. The mode line is updated by
> `gnus-set-mode-line'. I'm guessing that there'll have to be voodoo in
> that function to add these mousey thingies? Or what?
I don't know, but I think it is enough to just return a propertized
string (with the `help-echo' text property?).
Ah. Cf the following node in the lispref for Emacs 21:
/----[ Properties in the Mode Line ]
|
| Properties in the Mode Line
| ---------------------------
|
| Starting in Emacs 21, certain text properties are meaningful in the
| mode line. The `face' property affects the appearance of text; the
| `help-echo' property associate help strings with the text, and
| `local-map' can make the text mouse-sensitive.
|
| There are three ways to specify text properties for text in the mode
| line:
|
| 1. Put a string with the `local-map' property directly into the
| mode-line data structure.
|
| 2. Put a `local-map' property on a mode-line %-construct such as
| `%12b'; then the expansion of the %-construct will have that same
| text property.
|
| 3. Use a list containing `:eval FORM' in the mode-line data
| structure, and make FORM evaluate to a string that has a
| `local-map' property.
|
| You use the `local-map' property to specify a keymap. Like any
| keymap, it can bind character keys and function keys; but that has no
| effect, since it is impossible to move point into the mode line. This
| keymap can only take real effect for mouse clicks.
|
\----
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
next prev parent reply other threads:[~2001-12-29 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 15:26 Pavel Janík
2001-12-29 0:36 ` Lars Magne Ingebrigtsen
2001-12-29 10:45 ` Kai Großjohann
2001-12-29 10:52 ` Lars Magne Ingebrigtsen
2001-12-29 21:42 ` Kai Großjohann [this message]
2001-12-29 22:09 ` Lars Magne Ingebrigtsen
2002-01-02 14:22 ` Per Abrahamsen
2001-12-29 22:10 ` Pavel Janík
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=vafr8pd1z66.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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.
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 NNTP newsgroup(s).