all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dkcombs@panix.com (David Combs)
Subject: Re: Regexp for marking source code
Date: Wed, 6 Sep 2006 04:06:28 +0000 (UTC)	[thread overview]
Message-ID: <edlhg4$lgp$1@reader2.panix.com> (raw)
In-Reply-To: 44d8c969$1@news.greennet.net

In article <44d8c969$1@news.greennet.net>,
Ken Goldman  <kgold@watson.ibm.com> wrote:
>The dired Q command seems quite useful, but
>regexp syntax is obscure enough that I can't quite
>get what I want.
>


What *is* this dired "Q" command?

I got into a dired-buf, did C-h k, and typed in Q,
and got this:



q runs the command quit-window
   which is an interactive compiled Lisp function in `window'.
It is bound to q.
(quit-window &optional KILL WINDOW)

Quit the current buffer.  Bury it, and maybe delete the selected frame.
(The frame is deleted if it is contains a dedicated window for the buffer.)
With a prefix argument, kill the buffer instead.

Noninteractively, if KILL is non-nil, then kill the current buffer,
otherwise bury it.

If WINDOW is non-nil, it specifies a window; we delete that window,
and the buffer that is killed or buried is the one in that window.




What am I doing wrong?


Thanks,

David

  parent reply	other threads:[~2006-09-06  4:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 17:28 Regexp for marking source code Ken Goldman
2006-08-07 17:34 ` David Kastrup
2006-08-07 20:59   ` Org mode modifies files Sébastien Vauban
2006-08-10  5:33     ` claudine
2006-08-13 12:34       ` Sébastien Vauban
2006-08-08 21:12   ` Regexp for marking source code Dieter Wilhelm
     [not found]   ` <mailman.5022.1155124251.9609.help-gnu-emacs@gnu.org>
2006-08-09 12:08     ` David Kastrup
2006-08-14 21:13       ` Dieter Wilhelm
2006-08-15 20:58         ` David Kastrup
2006-09-06  4:06 ` David Combs [this message]
2006-09-06 17:51   ` Eli Zaretskii
2006-09-06 18:10     ` Arnaldo Mandel
2006-09-06 18:28       ` Eli Zaretskii

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='edlhg4$lgp$1@reader2.panix.com' \
    --to=dkcombs@panix.com \
    /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.