From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andreas =?iso-8859-1?q?R=F6hler?= Newsgroups: gmane.emacs.devel Subject: Re: dired-mark Date: Thu, 29 Nov 2007 21:15:07 +0100 Message-ID: <200711292115.07889.andreas.roehler@online.de> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1196367391 25502 80.91.229.12 (29 Nov 2007 20:16:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 29 Nov 2007 20:16:31 +0000 (UTC) Cc: Tassilo Horn , Drew Adams To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 29 21:16:39 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IxpoL-0006Zz-Ep for ged-emacs-devel@m.gmane.org; Thu, 29 Nov 2007 21:16:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ixpo2-0008Gk-I8 for ged-emacs-devel@m.gmane.org; Thu, 29 Nov 2007 15:16:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ixpnz-0008GY-At for emacs-devel@gnu.org; Thu, 29 Nov 2007 15:16:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ixpnx-0008GJ-Oc for emacs-devel@gnu.org; Thu, 29 Nov 2007 15:16:14 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ixpnx-0008GE-KK for emacs-devel@gnu.org; Thu, 29 Nov 2007 15:16:13 -0500 Original-Received: from moutng.kundenserver.de ([212.227.126.188]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ixpnx-00084D-9b for emacs-devel@gnu.org; Thu, 29 Nov 2007 15:16:13 -0500 Original-Received: from noname (p54BEA9AF.dip0.t-ipconnect.de [84.190.169.175]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1Ixpn70Rul-0002t1; Thu, 29 Nov 2007 21:15:21 +0100 User-Agent: KMail/1.9.5 In-Reply-To: Content-Disposition: inline X-Provags-ID: V01U2FsdGVkX1/9SQr5oCuETE9PNXlayGax+8wkhWpRJEhOr1z gmmyBMavLVQIjsLj0TydR0BbY/pTQvUyzRj1iImY40kE/vB41l vE5eMUdeh7QGsiiVtAoDg== X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:84319 Archived-At: Am Donnerstag, 29. November 2007 18:07 schrieb Drew Adams: > > > But what if you really intend to mark "." or ".."? > > > > That's precisely the question. > > Yes. > > > I can't imagine any case I would need it. However, as > > experience tells our imagination runs short occasionally... > > It doesn't matter if you can't imagine a case where you would need it. > > As long as users can operate on marked files and directories, someone will > want to, well, mark `.' or `..' and then operate on it. > > Madame Lambda or Mister X might define a command that prints each marked > file and all files in each marked directory. Or search them. Or do whatev= er > to/with them. And s?he might use that command on `.' or `..' as well as on > other marked directories. > > There is no reason that users shouldn't be able to use `dired-mark' to ma= rk > `.' and `..'. If you don't want to mark them, then don't. If you have code > that does something to all marked files and dirs, but you don't want to > treat `.' and `..', then exclude those in your special-purpose code. > > Wrt subdirs, it is only when point is on a subdir header line that > `dired-mark' does not mark the subdir's `.' or `..' - in that case, it > marks all files and directories _contained_ in the subdir. `dired-mark' > always marks `.' and `..' whenever they are targeted (e.g. cursor on that > line). > > That's TRT, IMO. Acting on a directory is not (necessarily) the same thing > as acting on everything in it. It is useful to be able to mark and act on > any directory, including `.' and `..'. > I have no definite opinion in that point, just raised the question from my scenario. Should you know a precise case where marking the "." and ".." in the dired-buffer are useful, I would like to read about that. Andreas R=F6hler