From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Red Gnus 0.74: Undo menu in *Group* buffer
Date: 17 Dec 1996 11:00:21 +0100 [thread overview]
Message-ID: <rjybexxzgq.fsf@babbage.dina.kvl.dk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 16 Dec 1996 21:46:18 +0100
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Because it's something that can (theoretically) be switched on in all
> buffers.
Why would you want to switch it off? Is it something that the user is
likely to switch on and off through a session? I.e. if it takes
resources, wouldn't a `gnus-use-undo' meta variable be more
appropriate.
> That would be possible, but it would be nicer not to "hard-code" this.
> What's the magic incantation to insert a menu bar entry into some
> menu? I seem to be having some problems groking the menu code...
It is `define-key-after' in Emacs and `add-menu-button' in XEmacs.
next prev parent reply other threads:[~1996-12-17 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-10 9:21 Per Abrahamsen
1996-12-11 0:27 ` Lars Magne Ingebrigtsen
1996-12-11 8:25 ` Per Abrahamsen
1996-12-16 20:46 ` Lars Magne Ingebrigtsen
1996-12-17 10:00 ` Per Abrahamsen [this message]
1996-12-17 19:06 ` Lars Magne Ingebrigtsen
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=rjybexxzgq.fsf@babbage.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).