all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: `Q' in Dired - be able to skip the rest of one file and move on to the next
Date: Thu, 03 Jan 2008 04:50:32 -0500	[thread overview]
Message-ID: <E1JAMie-00008V-8O@fencepost.gnu.org> (raw)
In-Reply-To: <DHEEKFAFJEFOJHLCFPFDKEFCCDAA.drew.adams@oracle.com>

    AFAICT, you must always visit each occurrence in one file before moving on
    to the next file. (Or else you can of course quit altogether, unmark the
    file you're through with, and then hit `Q' again.)

I agree it would be good to have a way to skip to the start of the next file.
A natural interface for this would be to unmark each file just before starting
to search that file.  Then, quitting the command and resuming it will skip
that file.

  reply	other threads:[~2008-01-03  9:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02  7:34 `Q' in Dired - be able to skip the rest of one file and move on to the next Drew Adams
2008-01-03  9:50 ` Richard Stallman [this message]
2008-01-03 10:11   ` Andreas Schwab
2008-01-03 10:27     ` Miles Bader
2008-01-03 16:17       ` Drew Adams
2008-01-03 15:56   ` Luc Teirlinck
2008-01-03 16:18     ` `Q' in Dired - be able to skip the rest of one file and move onto " Drew Adams
2008-01-03 21:32       ` Juri Linkov
2008-01-04  2:11         ` Bastien
2008-07-15  0:27           ` Juri Linkov
2008-07-15  7:38             ` Lennart Borgman (gmail)
2008-07-20  0:33               ` Juri Linkov
2008-01-05  5:54       ` Richard Stallman
2008-01-08  0:21         ` Juri Linkov
2008-01-08  0:33           ` Drew Adams
2008-01-08 19:08             ` Richard Stallman
2008-01-09  0:48             ` Juri Linkov
2008-01-09  1:47               ` Drew Adams
2008-01-08  2:12           ` Luc Teirlinck
2008-01-09  0:54             ` Juri Linkov

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=E1JAMie-00008V-8O@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@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.