From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: "Gustav Wikström" <gustav.erik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Link abbreviations, org-files with searches
Date: Mon, 31 Oct 2011 14:01:21 +0100 [thread overview]
Message-ID: <20111031140121.3a8d02de@kuru.homelinux.net> (raw)
In-Reply-To: <CA+SyOP_=WOwqeLnM-iXUWO-NbY9Vuw3cZYS2wYdXpuNfdr=Kkg@mail.gmail.com>
On Mon, 31 Oct 2011 13:33:31 +0100
Gustav Wikström <gustav.erik@gmail.com> wrote:
> Hi Suvayu!
>
> I know about the normal links and the possibility to search with
> these. The thing is that I want to use an abbreviation (see sec. 4.6
> in the manual) to not have to type the path for this particular link
> every time.
>
> Instead of typing (1)
>
> [[file:/path/to/file.org::*<Heading_text>][Description]]
>
> I want to be able to add an abbreviation in the beginning of the file
> the link is in, with (2):
>
> #+LINK: foo file:/long/path/to/file/foo.org
>
> and then use this abbreviation later in the text with (3):
>
> [[foo][Description]]
>
Okay now I follow you. I believe you are misunderstanding the syntax.
It should be like this (copying from my test example):
#+LINK: odir file:~/org/coding.org::
[[odir:Distributed%20analysis][Distributed analysis]]
[[odir:#ganga][Ganga]]
That said I had trouble getting the search to work with org files but I
will admit I did not try hard enough.
> ,and also be able to use searches with this abbreviation. And it is
> this syntax that seems a bit cumbersome to use when adding
> headline-searching to it (requiring four ":") and does not work when
> trying to use regular search. Unless I'm doing something wrong.
>
> I also know that I could add the "::%s" to the link, giving (4):
>
> #+LINK: foo file:/long/path/to/file/foo.org::%s
>
> but this makes it unusable as a simple file link without search. I
> intend to use the link in multiple places inside my document both
> with and without searches, thus I'm still wondering about this
> syntax-issue and the non-headline search.
>
How is it unusable? Shouldn't the following work with the above setting?
[[foo:<search_string>][Description]]
[[foo:*<Headline_string>][Description]]
Of course I didn't have the time to test this variation, so indeed there
could be a bug. :-p
> Regards
> Gustav
>
> (PS. sorry for the double-mail Suvayu. )
>
No worries. Hope the above suggestions help.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-10-31 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 11:36 Link abbreviations, org-files with searches Gustav Wikström
2011-10-31 12:10 ` suvayu ali
2011-10-31 12:33 ` Gustav Wikström
2011-10-31 13:01 ` Suvayu Ali [this message]
2011-10-31 13:55 ` Gustav Wikström
2011-10-31 14:09 ` Suvayu Ali
[not found] ` <CA+SyOP_+ywn8d5n-bngggc9LYSyZGNpiD3yvLbt=id7P=zmvmQ@mail.gmail.com>
2011-10-31 17:50 ` Gustav Wikström
2011-10-31 21:00 ` Gustav Wikström
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=20111031140121.3a8d02de@kuru.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gustav.erik@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 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).