From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tino Calancha Newsgroups: gmane.emacs.bugs Subject: bug#22828: 25.1.50; Mark symlinks whose target matches regexp Date: Sun, 28 Feb 2016 15:48:19 +0900 (JST) Message-ID: References: <87r3fxv1jx.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Trace: ger.gmane.org 1456641981 3227 80.91.229.3 (28 Feb 2016 06:46:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Feb 2016 06:46:21 +0000 (UTC) Cc: Tino Calancha , 22828@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Feb 28 07:46:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aZv7M-0002Zu-Bq for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Feb 2016 07:46:12 +0100 Original-Received: from localhost ([::1]:57769 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZv7L-0004zN-Qo for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Feb 2016 01:46:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZv7H-0004z1-KA for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2016 01:46:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZv7C-0003LB-HD for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2016 01:46:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:52359) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZv7C-0003L7-Dm for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2016 01:46:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aZv7C-0006wp-8K for bug-gnu-emacs@gnu.org; Sun, 28 Feb 2016 01:46:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Tino Calancha Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Feb 2016 06:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22828 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 22828-submit@debbugs.gnu.org id=B22828.145664191123903 (code B ref 22828); Sun, 28 Feb 2016 06:46:02 +0000 Original-Received: (at 22828) by debbugs.gnu.org; 28 Feb 2016 06:45:11 +0000 Original-Received: from localhost ([127.0.0.1]:49486 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aZv6M-0006D2-SE for submit@debbugs.gnu.org; Sun, 28 Feb 2016 01:45:11 -0500 Original-Received: from calancha-ilc.kek.jp ([130.87.234.234]:50290) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aZv6K-00065M-HF for 22828@debbugs.gnu.org; Sun, 28 Feb 2016 01:45:09 -0500 Original-Received: by calancha-ilc.kek.jp (Postfix, from userid 500) id 7F596D902; Sun, 28 Feb 2016 15:48:19 +0900 (JST) Original-Received: from localhost (localhost [127.0.0.1]) by calancha-ilc.kek.jp (Postfix) with ESMTP id 1ED049163; Sun, 28 Feb 2016 15:48:19 +0900 (JST) X-X-Sender: calancha@calancha-ilc.kek.jp In-Reply-To: <87r3fxv1jx.fsf@gnus.org> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:114028 Archived-At: > I'm not sure whether that's generally useful enough to include in > dired... I can't say that I remember ever wanting something like that. Sometimes the meaninful part of the symbolic link is in the target. Let's say you have a lot of files (thousands of them), in different locations and you create links to them: t1 t2 ... ti ... to all those files under the same directory for whatever processing/editing that you have in mind. In such case, the only mark which has sense to pick up some particular files with a regexp is something like the proposed command in this thread. > And this implementation also seems quite fragile. Will symlinks always > be presented as " -> "? And can " -> " be a valid part of a file name. Good point. I agree with this.