emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Gustav Wikström" <gustav.erik@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Link abbreviations, org-files with searches
Date: Mon, 31 Oct 2011 14:55:27 +0100	[thread overview]
Message-ID: <CA+SyOP_D_gzWZyncZ9Z87O5m6kDy2bTRvUK4XY51jWR-XrWw2Q@mail.gmail.com> (raw)
In-Reply-To: <20111031140121.3a8d02de@kuru.homelinux.net>

2011/10/31 Suvayu Ali <fatkasuvayu+linux@gmail.com>:
...
>> 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

This works when adding "::" to the end of the link. But with this
setting I cannot use the link as a simple file-link, eg. the following
does not work:

#+LINK: foo     file:/long/path/to/file/foo.org::
[[foo][Description]]

When trying to follow this link I get an error saying that there is
"no such file: /long/path/to/file/foo.org::"

/Gustav

  reply	other threads:[~2011-10-31 13:55 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
2011-10-31 13:55       ` Gustav Wikström [this message]
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=CA+SyOP_D_gzWZyncZ9Z87O5m6kDy2bTRvUK4XY51jWR-XrWw2Q@mail.gmail.com \
    --to=gustav.erik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@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).