From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <f92capac@gmail.com>
Cc: 22694@debbugs.gnu.org
Subject: bug#22694: 25.0.91; dired-mark-files-containing-regexp read file disk
Date: Tue, 16 Feb 2016 18:05:39 +0200 [thread overview]
Message-ID: <83h9h8wsh8.fsf@gnu.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1602162134160.6276@calancha-ilc.kek.jp> (message from Tino Calancha on Tue, 16 Feb 2016 21:47:28 +0900 (JST))
> Date: Tue, 16 Feb 2016 21:47:28 +0900 (JST)
> From: Tino Calancha <f92capac@gmail.com>
>
> When a buffer visiting the file on disk exists, the matching is performed
> on this buffer: if the buffer is out of sync with the file, the
> result may be wrong.
>
> emacs -Q /tmp/foo --eval='(progn (with-current-buffer "foo" (insert "baz")) (save-buffer))'
> C-x d RET
> M-! printf baz >> bar; for f in foo bar; do printf qux >> $f ; done RET
> g
> % g \`bazqux$ RET
> ;; Just match bar. It may signal an error if trying to read a non regular file.
>
>
> *) Files satisfying predicate `file-regular-p'.
> *) A buffer visiting the file on disk need to be updated before matching the input regexp.
Isn't this by design? Dired doesn't by default re-sync with the disk;
if you don't like this, you can turn on auto-revert in the Dired
buffer.
next prev parent reply other threads:[~2016-02-16 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:47 bug#22694: 25.0.91; dired-mark-files-containing-regexp read file disk Tino Calancha
2016-02-16 16:05 ` Eli Zaretskii [this message]
2016-02-17 14:07 ` Tino Calancha
2016-02-24 9:31 ` Tino Calancha
2016-04-10 7:02 ` Tino Calancha
2016-04-20 14:55 ` Eli Zaretskii
2016-04-20 15:31 ` Tino Calancha
2016-04-20 15:48 ` Eli Zaretskii
2016-06-26 15:32 ` Tino Calancha
2016-07-09 11:07 ` Eli Zaretskii
2016-07-11 5:48 ` Tino Calancha
2016-07-11 5:49 ` bug#22694: (no subject) Tino Calancha
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=83h9h8wsh8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22694@debbugs.gnu.org \
--cc=f92capac@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 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.