Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: storm@cua.dk (Kim F. Storm)
Cc: 2031@emacsbugs.donarmstrong.com,
	Chong Yidong <cyd@stupidchicken.com>,
	ding@gnus.org
Subject: Re: bug#2031: 23.0.60; Edit menu missing in Gnus buffers.
Date: Sun, 25 Jan 2009 20:14:37 +0100	[thread overview]
Message-ID: <87iqo35hb6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87mydfplsg.fsf@kfs-lx.rd.rdm> (Kim F. Storm's message of "Sun, 25 Jan 2009 14:17:35 +0100")

On Sun, Jan 25 2009, Kim F. Storm wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> There are so many top-level menus that they might not even fit on a
>> typical 80 column frame depending on the fonts.
>
> The real problem is too many Gnus menus then :-)

I'm not sure which ones are less useful than "Edit" or "Tools".  I
don't really like a redesign of menus so shortly before the start of
Emacs 23 pretest.

> But there is plenty of room in the Article menu.

When point is on a MIME part, you get:

File Options Buffers Tools Treatments Article Post Command MIME Part Help

>> Maybe it would be better to remove the Tools menu instead?
>
> I don't think that is acceptable - E.g. apply patch on the tools menu.

Hm.

> Maybe we could get rid of the Options menu (in general) by moving it to
> the bottom of the Edit menu where many other applications have their
> "Customize..."  or "Options..." entry.

I don't think this would be useful for Emacs in general.

>> So at least we would make it customizable (similar to
>> message-tool-bar-zap-list).
>
> Fine with me.

I'll be busy during the next week so I probably won't have time to
implement it.  Any volunteer?

> BTW, why is this reply sent to Chong and not Reiner.
> The headers in Reinar's response said:
>
>>Mail-Followup-To: Chong Yidong <cyd@stupidchicken.com>, 2031@emacsbugs.donarmstrong.com, ding@gnus.org, storm@cua.dk (Kim F. Storm)
>>Reply-To: Reiner Steib <Reiner.Steib@gmx.de>
>
> Does the Mail-Followup-To header take precedense over the Reply-To
> header ... 

I'd guess so.  The Reply-To just says "Use ...@imap.cc instead of
...@gmx.de for replies".

[ BTW, the mail that pass the bugtracker have a different Reply-To:

  To: Chong Yidong <cyd@stupidchicken.com>
  Cc: 2031@emacsbugs.donarmstrong.com, ding@gnus.org,
  	"Kim F. Storm" <storm@cua.dk>
  Reply-To: Reiner Steib <Reiner.Steib@gmx.de>, 2031@emacsbugs.donarmstrong.com
  Mail-Followup-To: Chong Yidong <cyd@stupidchicken.com>,
  	2031@emacsbugs.donarmstrong.com, ding@gnus.org,
  	storm@cua.dk (Kim F. Storm) 
]

> shouldn't Gnus use both when using wide reply (I added Reinar
> manually on this mail)?

No, I added this Mail-Followup-To since I don't need a copy because I
read the list (but I don't care much if I get one - it is split to my
news-cc group).

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2009-01-25 19:14 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
2009-01-25 13:17     ` Kim F. Storm
2009-01-25 19:14       ` Reiner Steib [this message]
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=87iqo35hb6.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).