From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Juri Linkov <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: dired-view-command-alist
Date: Wed, 06 Oct 2004 10:31:35 +0900 [thread overview]
Message-ID: <buowty4eio8.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <16739.5360.519472.808537@zarniwoop.ms25.local> (Reinhard Kotucha's message of "Tue, 5 Oct 2004 23:41:04 +0200")
Reinhard Kotucha <reinhard.kotucha@web.de> writes:
> In my example the separate window displayed the three files within one
> line followed by two empty lines.
>
> Maybe the two empty lines are the reason it didn't attract your
> attention.
No, I don't think so -- though it may contribute. It's simply that a
marker in the prompt is _much_ more noticeable when your attention is
focused there.
This is a fairly important issue, BTW. It's not that hard to
inadvertantly use a command intending for it to be used on the current
file without realizing that you had some marks set, and the possibility
for damage is great.
-Miles
--
I'd rather be consing.
next prev parent reply other threads:[~2004-10-06 1:31 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 ` dired-view-command-alist David Kastrup
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 ` Miles Bader [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buowty4eio8.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=miles@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.