From: David Kastrup <dak@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Tumme menu in Dired, what to do about it?
Date: Thu, 25 May 2006 14:06:36 +0200 [thread overview]
Message-ID: <85fyiyz4tv.fsf@lola.goethe.zz> (raw)
In-Reply-To: <7dbe73ed0605250457j7c9dbbf6ubec96c45cb1daa0f@mail.gmail.com> (Mathias Dahl's message of "Thu, 25 May 2006 13:57:52 +0200")
"Mathias Dahl" <mathias.dahl@gmail.com> writes:
> Richard replied:
>
>> There is no room for an additional menu bar menu in Dired mode
>> on a text terminal. The menu bar is nearly full already.
>
>> Putting it in as a submenu of some existing Dired menu would be ok.
>> Perhaps "Immediate".
>
> So I created the sub menu there.
>
>> Shouldn't this item be under "Regexp"?
>> ...
>> And this one (and others) under "Operate"?
>
> Probably, in one sense. But do we really want to mess with these
> "standard" or "old" Dired menus? If there were a "Dired tools" menu,
> tumme would fit well as a sub menu under that one.
In my opinion, stuff should be there where the user would expect it
according to its functionality, not according to package boundaries.
>> Assuming tumme-tag-remove deletes tags, tumme-tag-delete sounds better.
>
> I trust your judgement on this one (my English skills are not good
> enough).
I am opposed. "tumme-tag-delete" sounds like it would delete tagged
files, not like it would remove tags from files. "delete" sounds more
appropriate with more physical entities than just tags. You can,
after "deleting" a tag, put it right on afterwards again.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-05-25 12:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 0:42 Tumme menu in Dired, what to do about it? Mathias Dahl
2006-02-13 17:59 ` Juri Linkov
2006-02-13 20:24 ` Mathias Dahl
2006-02-14 0:40 ` Richard M. Stallman
2006-02-13 20:04 ` Richard M. Stallman
2006-02-13 20:25 ` Mathias Dahl
2006-05-24 18:54 ` Mathias Dahl
2006-05-24 21:45 ` Nick Roberts
2006-05-24 22:07 ` Mathias Dahl
2006-05-25 0:52 ` Drew Adams
2006-05-25 11:40 ` Mathias Dahl
2006-05-25 3:51 ` Richard Stallman
2006-05-25 8:06 ` Nick Roberts
2006-05-25 8:11 ` Nick Roberts
2006-05-25 11:57 ` Mathias Dahl
2006-05-25 12:06 ` David Kastrup [this message]
2006-05-25 13:20 ` Nick Roberts
2006-05-25 13:23 ` David Kastrup
2006-05-25 13:51 ` Nick Roberts
2006-05-25 13:58 ` Mathias Dahl
2006-05-25 13:59 ` David Kastrup
2006-05-26 2:21 ` Richard Stallman
2006-05-26 10:33 ` Mathias Dahl
2006-05-27 3:36 ` Richard Stallman
2006-05-26 22:24 ` Mathias Dahl
2006-05-26 22:35 ` Mathias Dahl
2006-05-25 13:13 ` Nick Roberts
2006-05-26 2:22 ` Richard Stallman
2006-05-26 10:40 ` Mathias Dahl
2006-05-27 3:36 ` Richard Stallman
2006-05-25 11:32 ` Mathias Dahl
2006-05-26 2:21 ` Richard Stallman
2006-05-26 23:29 ` Mathias Dahl
2006-05-27 23:32 ` Richard Stallman
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=85fyiyz4tv.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=rms@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).