From: Carsten Dominik <carsten.dominik@gmail.com>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems with hyperlinked files
Date: Wed, 24 Mar 2010 11:50:26 +0100 [thread overview]
Message-ID: <37BFCF57-A0AA-496B-89E1-6D0EC902F380@gmail.com> (raw)
In-Reply-To: <4e3ad401003232045o2ab47b42pb9148ed16a76e46d@mail.gmail.com>
On Mar 24, 2010, at 4:45 AM, Leo Alekseyev wrote:
>>
>> I could reproduce this, but I don't know if this is really a bug.
>> (I never heard of protecting spaces with angle brackets.)
>
> Actually, it's right there in section 4.3 of the manual, last
> sentence: "if you need to remove ambiguities about the end of the
> link, enclose them in angular brackets. "
>
>> You do not have to protect spaces, because the URL is surrounded by
>> the
>> square brackets. I could only insert angle brackets into a link by
>> editing it manually; when you edit a link with C-c C-l and enclose
>> the
>> URL in angle brackets, Org will automatically remove them.
>
> Thanks, both these methods work -- although I still think it would be
> nice if org mode could properly handle angle brackets inside square
> ones; the motivation here is that often I just paste in file paths
> instead of using C-c C-l, and then I have to use angle brackets to
> deal w/ spaces; if I later want to change it to an annotated link, it
> would be nice not to have to strip the angle brackets before wrapping
> it in square ones...
It would be hard for Org to make that distinction in a stable way. For
all it knows, the > might be part of the link.
Best habit is to always use [[..]] when you have a link
that contains spaces, just ignore the availability of
angular brackets as delimiters. These were used historically
in Org before the bracket notation was introduced.
I am keeping that syntax for backward compatibility, but had
I had bracket links from the start, the angular bracket
representation would not exist today.
Best wishes
- Carsten
next prev parent reply other threads:[~2010-03-24 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:13 Problems with hyperlinked files Leo Alekseyev
2010-03-23 20:26 ` Jan Böcker
2010-03-24 3:45 ` Leo Alekseyev
2010-03-24 10:50 ` Carsten Dominik [this message]
2010-03-24 13:42 ` Jan Böcker
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=37BFCF57-A0AA-496B-89E1-6D0EC902F380@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=dnquark@gmail.com \
--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).