From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#10393: 24.0.92; missing files in Dired Date: Thu, 29 Dec 2011 01:26:25 -0500 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1325140044 2835 80.91.229.12 (29 Dec 2011 06:27:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Dec 2011 06:27:24 +0000 (UTC) Cc: 10393@debbugs.gnu.org To: rms@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Dec 29 07:27:20 2011 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Rg9SS-0007lk-KU for geb-bug-gnu-emacs@m.gmane.org; Thu, 29 Dec 2011 07:27:20 +0100 Original-Received: from localhost ([::1]:40358 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rg9SR-0000H5-Op for geb-bug-gnu-emacs@m.gmane.org; Thu, 29 Dec 2011 01:27:19 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:34776) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rg9SN-0000Gm-WE for bug-gnu-emacs@gnu.org; Thu, 29 Dec 2011 01:27:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rg9SN-0004QQ-07 for bug-gnu-emacs@gnu.org; Thu, 29 Dec 2011 01:27:15 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:57128) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rg9SM-0004QM-Uu for bug-gnu-emacs@gnu.org; Thu, 29 Dec 2011 01:27:14 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1Rg9V4-000689-GB for bug-gnu-emacs@gnu.org; Thu, 29 Dec 2011 01:30:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 29 Dec 2011 06:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 10393 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 10393-submit@debbugs.gnu.org id=B10393.132514016323492 (code B ref 10393); Thu, 29 Dec 2011 06:30:02 +0000 Original-Received: (at 10393) by debbugs.gnu.org; 29 Dec 2011 06:29:23 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Rg9UQ-00066q-D0 for submit@debbugs.gnu.org; Thu, 29 Dec 2011 01:29:23 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Rg9UN-00066j-Nn for 10393@debbugs.gnu.org; Thu, 29 Dec 2011 01:29:20 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Rg9RZ-0001H8-0N; Thu, 29 Dec 2011 01:26:25 -0500 In-reply-to: (message from Richard Stallman on Wed, 28 Dec 2011 18:26:42 -0500) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Thu, 29 Dec 2011 01:30:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:55263 Archived-At: > Date: Wed, 28 Dec 2011 18:26:42 -0500 > From: Richard Stallman > Reply-To: rms@gnu.org > > I can't reproduce this, but I have seen it several times. > > I have a Dired buffer displaying the directory ~/outgoing. I type g, > and some file whose name starts in .# does not show up. > I see that file when I type ls outside Emacs, but it is missing > from the Dired buffer. When it does happen, is it reproducible? That is, if you repeatedly type `g', does that file never show up? If so, could you perhaps step in a debugger through dired-redin and its subroutines, when you do encounter the bug, and see what is going on there? Btw, does that happen in Dired buffers that read the entire directory, or buffers that show only some files specified by a wildcard (or both)?