From: David Kastrup <David.Kastrup@t-online.de>
Subject: Re: dired-do-hardlink should update link count we see
Date: 09 Jul 2002 18:26:54 +0200 [thread overview]
Message-ID: <x5ptxwvpdd.fsf@tupik.goethe.zz> (raw)
In-Reply-To: Pine.SUN.3.91.1020709182004.18085A-100000@is
eliz@is.elta.co.il (Eli Zaretskii) writes:
> On 9 Jul 2002, David Kastrup wrote:
>
> > It is perfectly understandable if one thinks some things not worth
> > fixing or doing correctly.
>
> I didn't say this isn't worth fixing, I just pointed out that it's a
> part of a general pattern.
Oh, surely, surely. Other operations (like changing permissions, the
file name, moving files, copying them) update the info in the dired
buffer without actually rereading the directory info, so the general
pattern would certainly imply that updating the info in the dired
buffer without actually rereading the directory info would be
something entirely different.
Again, if you are planning to make sense, you better try harder. And
just removing all relevant context from posts of mine (which you have
now done two times already) in order to repeat your unsubstantiated
claim is starting to look silly.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de
next prev parent reply other threads:[~2002-07-09 16:26 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
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 [this message]
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=x5ptxwvpdd.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.