unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Li Zhai <mrzhaili@gmail.com>
Cc: 6362@debbugs.gnu.org
Subject: bug#6362: Emacs command `dired-isearch-filenames-regexp' cause CPU usage 100%
Date: Mon, 07 Jun 2010 21:05:09 +0300	[thread overview]
Message-ID: <87k4qb82s3.fsf@mail.jurta.org> (raw)
In-Reply-To: <AANLkTiliQ-m3AWvLpEZoGvtKG6BTVSKnf3tPAXVTx9ng@mail.gmail.com> (Li Zhai's message of "Sun, 6 Jun 2010 20:30:42 +0800")

> Yes, I expect that query-replace will rename file names start with
> `f'. As the search process just matched the file names, it is a simple
> thought that `^' means the beginning of the file name.
>
> If we could add some special syntax properties to the white-space
> before the file name, it is possible to match the file names start
> with `f'. For instance, type :
>
> dired-isearch-filenames-regexp RET \sxf  RET
>
> At here, the `x' means the special syntax class.

`\sx' matches a character, but it would be better to match the empty string
like `^' does.

One variant is to narrow the dired buffer so the beginning of a line
will be the beginning of a file name.  Unfortunately, it's impossible
to narrow to columns, only to lines.

Another variant is to add a new predicate function in regex.c
that will specify where ^ should match, so dired will set it
to a function that returns non-nil at the beginning of a file name.

-- 
Juri Linkov
http://www.jurta.org/emacs/





  reply	other threads:[~2010-06-07 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06  3:36 bug#6362: Emacs command `dired-isearch-filenames-regexp' cause CPU usage 100% Li Zhai
2010-06-06  9:54 ` Juri Linkov
2010-06-06 12:30   ` Li Zhai
2010-06-07 18:05     ` Juri Linkov [this message]
2010-06-07 18:09   ` Juri Linkov
2011-09-09 15:49     ` 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

  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=87k4qb82s3.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=6362@debbugs.gnu.org \
    --cc=mrzhaili@gmail.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 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).