From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 2031@emacsbugs.donarmstrong.com, ding@gnus.org,
storm@cua.dk (Kim F. Storm)
Subject: Re: bug#2031: 23.0.60; Edit menu missing in Gnus buffers.
Date: Sun, 25 Jan 2009 11:01:40 +0100 [thread overview]
Message-ID: <87d4eb7lh7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87ocxww993.fsf@cyd.mit.edu> (Chong Yidong's message of "Sat, 24 Jan 2009 18:54:16 -0500")
On Sun, Jan 25 2009, Chong Yidong wrote:
> "Kim F. Storm" <storm@cua.dk> wrote:
>
>> This is an old bug - but still not fixed in Emacs 23.
>>
>> For some reason, M-x gnus consistently removes the Edit menu
>> in all buffers related to gnus.
There are so many top-level menus that they might not even fit on a
typical 80 column frame depending on the fonts.
>> It might be ok in the group overview, and possibly in the article
>> overview, but in the article buffers, I think it must be shown.
The only commands from Edit that might be useful are:
- Copy
- Select All
- Goto / *
Others?
Maybe it would be better to remove the Tools menu instead?
> Punting to ding---any objection to removing the calls to
> gnus-turn-off-edit-menu in at least the article buffers?
We have this since 1997 and I don't recall many complaints. So at
least we would make it customizable (similar to
message-tool-bar-zap-list).
(defcustom gnus-menu-bar-zap-list
'((t tools) ;; turn of tools many in all special Gnus buffers
(category edit)
(article nil) ;; keep edit in Article buffer
(group edit)
(server edit)
(browse edit)
(summary edit))
[...]
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2009-01-25 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090124203612.935EB9E022@smtp.fullrate.dk>
2009-01-24 23:54 ` Chong Yidong
2009-01-25 10:01 ` Reiner Steib [this message]
2009-01-25 13:17 ` Kim F. Storm
2009-01-25 19:14 ` Reiner Steib
2010-10-18 21:35 ` 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=87d4eb7lh7.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=2031@emacsbugs.donarmstrong.com \
--cc=Reiner.Steib@gmx.de \
--cc=cyd@stupidchicken.com \
--cc=ding@gnus.org \
--cc=storm@cua.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).