From: David Kastrup <dak@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
Reinhard Kotucha <reinhard.kotucha@web.de>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: dired-view-command-alist
Date: Tue, 05 Oct 2004 10:05:48 +0200 [thread overview]
Message-ID: <x5brfhk2sj.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20041005074324.GA19800@fencepost> (Miles Bader's message of "Tue, 5 Oct 2004 03:43:24 -0400")
Miles Bader <miles@gnu.org> writes:
> On Tue, Oct 05, 2004 at 02:31:21AM +0200, Reinhard Kotucha wrote:
>> When more then one file is marked, it displays something like
>>
>> ! on * [3 files]: {3 guesses} [ghostview]
>>
>> in the minibuffer. The string "[3 files]" can be omitted because at
>> the same time the names of the marked files are displayed in a
>> separate window. Thus "! on *:" is sufficient.
>
> I disagree -- I find the "[3 files]" info useful. Despite the filenames
> being displayed in a separate, the presence of that string in the prompt is
> more noticeable (maybe that sounds surprising, but when I give a command that
> I know is going to prompt me, I tend to focus on the minibuffer, so a warning
> there is much more likely to wake me up than a new window).
>
> The presence of the actual number of files seems to have a similar effect:
> because it's not a fixed string, it's somehow more noticeable than for
> instance a simple "[multiple files]" would be.
>
> So I'd say keep the "[<N> files]" stuff in the prompt.
An a different tack, one of my proposals was to bind * to inserting a
text propertied string showing <marked files> or so. Perhaps it would
be more straightforward to just insert the file names themselves
(shell-quoted, of course).
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-10-05 8:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 2:00 dired-view-command-alist Reinhard Kotucha
2004-09-27 3:44 ` dired-view-command-alist Miles Bader
2004-09-27 14:54 ` dired-view-command-alist Richard Stallman
2004-10-02 20:33 ` dired-view-command-alist Juri Linkov
2004-10-04 15:17 ` dired-view-command-alist Richard Stallman
2004-10-05 0:31 ` dired-view-command-alist Reinhard Kotucha
2004-10-05 7:43 ` dired-view-command-alist Miles Bader
2004-10-05 8:05 ` David Kastrup [this message]
2004-10-05 8:42 ` dired-view-command-alist Miles Bader
2004-10-05 21:14 ` dired-view-command-alist Reinhard Kotucha
2004-10-06 17:10 ` dired-view-command-alist Richard Stallman
2004-10-05 13:38 ` dired-view-command-alist Robert J. Chassell
2004-10-05 21:41 ` dired-view-command-alist Reinhard Kotucha
2004-10-06 1:31 ` dired-view-command-alist Miles Bader
2004-10-06 5:29 ` dired-view-command-alist Richard Stallman
2004-10-06 19:17 ` dired-view-command-alist Reinhard Kotucha
2004-10-07 16:45 ` dired-view-command-alist Richard Stallman
2004-10-07 6:00 ` dired-view-command-alist Juri Linkov
2004-10-08 15:51 ` dired-view-command-alist Kai Grossjohann
2004-10-08 18:48 ` dired-view-command-alist Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 19:27 dired-view-command-alist Sam Steingold
2005-01-04 3:38 ` dired-view-command-alist Richard Stallman
2005-01-04 9:03 ` dired-view-command-alist Juri Linkov
2005-01-05 3:30 ` dired-view-command-alist Richard Stallman
2005-01-04 14:38 ` dired-view-command-alist Sam Steingold
2005-01-04 19:54 ` dired-view-command-alist 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=x5brfhk2sj.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=reinhard.kotucha@web.de \
--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).