all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tino Calancha <f92capac@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 22828@debbugs.gnu.org
Subject: bug#22828: 25.1.50; Mark symlinks whose target matches regexp
Date: Mon, 29 Feb 2016 13:18:18 +1100	[thread overview]
Message-ID: <87mvqk45ud.fsf@gnus.org> (raw)
In-Reply-To: <alpine.LRH.2.20.1602281925040.4261@calancha-ilc.kek.jp> (Tino Calancha's message of "Sun, 28 Feb 2016 19:38:19 +0900 (JST)")

Tino Calancha <f92capac@gmail.com> writes:

>> Use dired-move-to-end-of-filename to find the proper place.
> I see, this way we forget about the '@ -> ' or ' -> ' (or any other?).
>
> Do you think is ok that fn contains such ' -> ' thing?
> I would prefer if fn doesn't contain that.
> So, the question is:
> do we have a portable way to get the target of one link?
> We may introduce something like:
> dired-symlink-target (if doesn't exist)

I thin kyou should just call `(dired-get-filename nil t)' on each line
to get the file names, and then call `file-truename' to get the name of
the target.  Inspecting the text in the buffer with regexps is bound to
be fragile.

But I'm still not sure this is a function that would be generally
useful.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-02-29  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 14:27 bug#22828: 25.1.50; Mark symlinks whose target matches regexp Tino Calancha
2016-02-28  5:36 ` Lars Ingebrigtsen
2016-02-28  6:48   ` Tino Calancha
2016-02-28  9:55     ` Andreas Schwab
2016-02-28 10:38       ` Tino Calancha
2016-02-29  2:18         ` Lars Ingebrigtsen [this message]
2016-03-01 11:12           ` Constantino Calancha

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=87mvqk45ud.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=22828@debbugs.gnu.org \
    --cc=f92capac@gmail.com \
    --cc=schwab@linux-m68k.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.
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.