all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43028@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>,
	uyennhi.qm@gmail.com, jidanni@jidanni.org
Subject: bug#43028: 28.0.50; Add dired commands to navigate symbolic links
Date: Tue, 25 Aug 2020 17:44:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.22.394.2008251733030.19452@localhost.example.com> (raw)
In-Reply-To: <87k0xndt7p.fsf@gnus.org>



On Tue, 25 Aug 2020, Lars Ingebrigtsen wrote:

> Hm...  I can't say that I can remember ever wanting to visit symlinks in
> a dired buffer in particular.  What's the use case?
Of course, it is of interest if you work a lot with symbolic links: to 
move promptly to them with short typing.
I do use them often, that's why I feel good with this.

Of course, if it is not see as something useful it's OK to 
discard this idea (that's why I wanted to ask first) :-)

> And I think that if I wanted to, I probably wouldn't remember these
> keystrokes -- I'd just isearch for -> instead.
I added the menu entry under 'Immediate' for discoverability.

For american keyboards is almost same exercise push < or > than { or }
Also, the curly braces suggested me some directionability in their shape 
that we haven't exploit yet.
I have noticed dired+ is not using this key either.





  reply	other threads:[~2020-08-25 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 19:12 bug#43028: 28.0.50; Add dired commands to navigate symbolic links Tino Calancha
2020-08-24 22:36 ` 積丹尼 Dan Jacobson
2020-08-25  8:29 ` Lars Ingebrigtsen
2020-08-25 15:44   ` Tino Calancha [this message]
2020-08-25 19:55     ` Lars Ingebrigtsen
2020-08-25 20:17       ` Drew Adams
2020-08-27  8:14         ` Tino Calancha
2020-08-27  8:17         ` Tino 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=alpine.LSU.2.22.394.2008251733030.19452@localhost.example.com \
    --to=tino.calancha@gmail.com \
    --cc=43028@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --cc=uyennhi.qm@gmail.com \
    /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.