From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Directory Links (and a bug?)
Date: Tue, 07 Sep 2010 21:35:11 +0200 [thread overview]
Message-ID: <87lj7dxs7k.fsf@Rainer.invalid> (raw)
Making a directory link like this: [[file://bla/fasel/]] will open that
folder in explorer on Windows at work, which is nice since I can just
keep a bunch of those in my notes.org file and fire them up whenever I
need to (the history in Explorer is never that helpful). I have since
learned that there's a special form to make that link open in EMACS
[[file+emacs://bla/fasel/]] and that fires up dired. Or, if I had set
up org-mode so that file:-links would open inside EMACS, I could use
[[file+sys://bla/fasel/]] to force the link to open in an external
application. So far so good... what I'd want in addition is to have the
link open in dired with wildcard patterns (giving a file name that
doesn't exist or looks like a directory gets me into dired, but doesn't
give it the "file" part as a wildcard argument) or alternatively
directly into vc-dir like [[file+dired://bla/fasel/*.org]] and
[[file+vc-dir://bla/fasel/]]. Whatever the part after the "+", the
links should be exported like normal file: links.
The link abbrevs don't really work for this as they are supposed to
return a string and not go off into another buffer (it does sort-of
work, but I suspect it breaks exporting etc.). An elisp link works, but
gets me a Yes/no question and shows up verbatim in export, not as link.
The +sys/+emacs links (and some abbrevs) export as file:-links with the
complete link-syntax appended as anchor (like
file:///bla/fasel/#file+emacs://bla/fasel/ - this works, but that looks
like a bug to me or an accidental feature at least).
Now, looking into the code I see that there's a lot of special casing
going on and no obvious hooks to tap into and that I don't really
understand what's going on... If anybody could shed light on how this
is all supposed to work "under the hood" and how some extra link methods
would need to be implemented, please discuss.
Achim.
next reply other threads:[~2010-09-07 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 19:35 Achim Gratz [this message]
2010-09-07 22:18 ` Directory Links (and a bug?) Noorul Islam
2010-09-08 15:51 ` Achim Gratz
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lj7dxs7k.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).