From: "Andreas Röhler" <andreas.roehler@online.de>
To: help-gnu-emacs@gnu.org
Subject: Re: dired-mark
Date: Thu, 29 Nov 2007 07:47:22 +0100 [thread overview]
Message-ID: <200711290747.22690.andreas.roehler@online.de> (raw)
In-Reply-To: <97715768-5747-420B-90E2-C88BDC92D2FC@Web.DE>
Am Donnerstag, 29. November 2007 01:31 schrieb Peter Dyballa:
> Am 28.11.2007 um 17:39 schrieb Andreas Röhler:
> > Or exist known cases, where marks on directories are useful?
>
> Go up one level and try there! (It depends on what you intend, of
> course.)
>
Do you know any command which marks these
directory-chars and operates on them after marking?
> The problem could be that a user could delete . or .. or make it
> unreachable.
...
To prevent from deleting, OK. But then it seems better,
to skip i.e. block marking them from the very
beginning. (?)
Thanks
Andreas Röhler
next prev parent reply other threads:[~2007-11-29 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 16:39 dired-mark Andreas Röhler
2007-11-29 0:31 ` dired-mark Peter Dyballa
2007-11-29 6:47 ` Andreas Röhler [this message]
2007-11-29 11:07 ` dired-mark Peter Dyballa
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=200711290747.22690.andreas.roehler@online.de \
--to=andreas.roehler@online.de \
--cc=help-gnu-emacs@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.
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).