From: Eli Zaretskii <eliz@gnu.org>
To: Alexis <flexibeast@gmail.com>
Cc: 15508@debbugs.gnu.org, larsi@gnus.org, rms@gnu.org
Subject: bug#15508: 24.3.50; file missing in dired
Date: Sat, 26 Dec 2015 12:21:52 +0200 [thread overview]
Message-ID: <83wps1ik73.fsf@gnu.org> (raw)
In-Reply-To: <87fuyqng6c.fsf@gmail.com> (message from Alexis on Sat, 26 Dec 2015 12:37:31 +1100)
> From: Alexis <flexibeast@gmail.com>
> Date: Sat, 26 Dec 2015 12:37:31 +1100
> Cc: 15508@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Richard Stallman <rms@gnu.org> writes:
> >
> >> In my dired buffer on the whole directory `outgoing', the lock
> >> file `.#out-3' does not appear. I typed g a couple of times,
> >> and that file continues not to show up.
> >>
> >> `ls -a' does show it.
> >
> > Are you still having these issues? I can't recall seeing
> > anybody else describing a problem like this...
>
> i faced what i believe to be a similar problem, which was caused
> by the default value of the `dired-omit-files' variable:
>
> "^\\.?#\\|^\\.$\\|^\\.\\.$"
>
> Changing the value of that variable to:
>
> "^\\.\\|^#"
>
> resulted in dired displaying things as i expect.
dired-omit-files only takes effect when the user invoked
dired-omit-mode, in which case they are asking for omitting the lock
files (and can customize dired-omit-files if they don't want to omit
lock files). Since dired-omit-mode is not turned on by default, I
think this is not a bug, but a cockpit error, perhaps an inadvertent
one.
Richard, do you turn on dired-omit-mode in your Dired buffers?
next prev parent reply other threads:[~2015-12-26 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 1:10 bug#15508: 24.3.50; file missing in dired Richard Stallman
2013-10-08 18:03 ` Glenn Morris
2015-12-26 1:02 ` Lars Ingebrigtsen
2015-12-26 1:37 ` Alexis
2015-12-26 10:21 ` Eli Zaretskii [this message]
2016-02-29 5:32 ` Lars Ingebrigtsen
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=83wps1ik73.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15508@debbugs.gnu.org \
--cc=flexibeast@gmail.com \
--cc=larsi@gnus.org \
--cc=rms@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 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).