From: David Kastrup <David.Kastrup@t-online.de>
Subject: Re: dired-do-hardlink should update link count we see
Date: 09 Jul 2002 14:33:01 +0200 [thread overview]
Message-ID: <x5lm8lxerm.fsf@tupik.goethe.zz> (raw)
In-Reply-To: Pine.SUN.3.91.1020709143628.15595A-100000@is
eliz@is.elta.co.il (Eli Zaretskii) writes:
> On 9 Jul 2002, David Kastrup wrote:
>
> > > I think Dired doesn't automatically refresh the directory view as a
> > > matter of principle. It's not something specific to
> > > dired-do-hardlink.
> >
> > So if you rename a file from within dired, dired displays the same
> > file name? If you change its permissions from within dired, it
> > displays the same permissions? If you move it or delete it from
> > within dired, it stays there as if it existed before? If you copy to
> > some other directory under dired, the files don't arrive in the
> > display there?
> >
> > Could you substantiate your claim?
>
> The claim is that Dired never queries the filesystem after any operation,
> it just manipulates the buffer contents.
Well, that's what Dan complained about: that it did not manipulate the
buffer contents after doing a hard link. So if your claim was to be
what you claim, it was utterly irrelevant to the report.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de
next prev parent reply other threads:[~2002-07-09 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 13:15 dired-do-hardlink should update link count we see Dan Jacobson
2002-07-09 5:28 ` Eli Zaretskii
2002-07-09 7:20 ` David Kastrup
2002-07-09 11:37 ` Eli Zaretskii
2002-07-09 12:33 ` David Kastrup [this message]
2002-07-09 13:19 ` Eli Zaretskii
2002-07-09 13:34 ` David Kastrup
2002-07-09 15:21 ` Eli Zaretskii
2002-07-09 16:26 ` David Kastrup
2002-07-10 5:40 ` Dan Jacobson
2002-07-10 15:45 ` David Kastrup
2002-07-10 10:42 ` Richard Stallman
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=x5lm8lxerm.fsf@tupik.goethe.zz \
--to=david.kastrup@t-online.de \
/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.