From: Daniel Bausch <bausch@dvs.tu-darmstadt.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with links whose description looks like a link
Date: Thu, 20 Nov 2014 08:50:42 +0100 [thread overview]
Message-ID: <87lhn6cnu5.fsf@gelnhausen.dvs.informatik.tu-darmstadt.de> (raw)
In-Reply-To: 87y4r7dyz7.fsf@nicolasgoaziou.fr
Hello and thanks for the answer!
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Daniel Bausch <bausch@dvs.tu-darmstadt.de> writes:
>
>> I'm using Org from Git master. If I have a link like, e.g.
>>
>> [[file:somefile.c::int whatsoever][file:somefile.c::int whatsoever]]
>>
>> and a a file somefile.c with the lines
>>
>> int some;
>> int whatsoever;
>>
>> then opening the link with the cursor before the space jumps to the
>> first line, while opening the link on the word "whatsoever" jumps to the
>> second line. It seems like Org detects a link within the link as if the
>> brackets were missing.
>
> This is correct.
>
> Org allows plain links (e.g. file:foo.org) within bracket links. This is
> the sole way to have, for example, an inline image as a link.
Hmm, ok, I understand the intention regarding the detection and display
of inline images as part of a link description; however, even for inline
images following the link jumps to the target of the outer link and not
the image itself -- as long as inline images are toggled on. Without
showing inline images following the link opens the image regardless of
the original link target.
I think that the effective target of a link should never be affected by
its description. Even fontification and mouse hovering info thinks that
the link still targets at its target, i.e. when hovering over the link
the whole link gets highlighted and not just the inner one and the
tooltip shows the whole target of the outer link, while clicking jumps
to the link contained within the description.
If there is a real application/need for nested links (besides inline
images used as part of link description) I would rather expect them to
be written explicitly by typing another pair of brackets nested within
the description; however, this syntax is currently not parsed as such.
Regards,
Daniel
--
MSc. Daniel Bausch
Research Assistant (Computer Science)
Technische Universität Darmstadt
http://www.dvs.tu-darmstadt.de/staff/dbausch
next prev parent reply other threads:[~2014-11-20 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 8:30 Problem with links whose description looks like a link Daniel Bausch
2014-11-19 14:52 ` Nicolas Goaziou
2014-11-20 7:50 ` Daniel Bausch [this message]
2014-11-20 22:39 ` Nicolas Goaziou
2014-11-21 7:11 ` Daniel Bausch
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=87lhn6cnu5.fsf@gelnhausen.dvs.informatik.tu-darmstadt.de \
--to=bausch@dvs.tu-darmstadt.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).