all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Chris Moore" <christopher.ian.moore@gmail.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: tags-search doesn't check files are up-to-date
Date: Fri, 01 Feb 2008 18:46:38 -0500	[thread overview]
Message-ID: <87fxwcutnl.fsf@stupidchicken.com> (raw)
In-Reply-To: <a9691ee20802011035t1e691d67mf59e91efaf38e76f@mail.gmail.com> (Chris Moore's message of "Fri\, 1 Feb 2008 19\:35\:21 +0100")

"Chris Moore" <christopher.ian.moore@gmail.com> writes:

> I was just trying to find something in an old IRC logfile.  I went to
> the directory holding the files with dired, marked the last week's
> worth of logs and hit "A" (dired-do-search) to search them for the
> string.
>
> Emacs told me "All files processed" - it didn't find the string.
>
> "grep" tells me differently - the string is there.
>
> It turns out that I had visited one of the logs when it still being
> written a few days ago.  Emacs had the first half of the file in a
> buffer, and the string I wanted was in the 2nd half - on disk, but not
> in the buffer.
>
> I would expect Emacs to say "File ... changed on disk.  Reread from
> disk? (yes or no) " when I try searching a file that's changed, but it
> silently assumes I don't want to know that it is using an old copy.
>
> It's pretty simple to reproduce:  make an empty file, visit it, append
> 'xxx' to it outside of Emacs, mark the file in dired and search it for
> 'xxx' using the "A" (dired-do-search) key.  It won't find the 'xxx'.

This can be fixed by setting tags-loop-revert-buffers to non-nil.

Maybe dired-do-search and the other commands that use etags should
automatically bind tags-loop-revert-buffers to t?




      reply	other threads:[~2008-02-01 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 18:35 tags-search doesn't check files are up-to-date Chris Moore
2008-02-01 23:46 ` Chong Yidong [this message]

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=87fxwcutnl.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=christopher.ian.moore@gmail.com \
    --cc=emacs-pretest-bug@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.