From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: is ascii link format canonical? can it be made more linkifiable?
Date: Sat, 10 Feb 2018 14:18:40 +0100 [thread overview]
Message-ID: <87lgg1c79r.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJcAo8tbLhHb4NRwgvDadVkkcSo4XO99SBTGa83E+wLoZsyEtA@mail.gmail.com> (Samuel Wales's message of "Mon, 5 Feb 2018 21:26:14 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> recent maint.
>
> org-ascii-links-to-notes is t.
>
> i am exporting bare links that look in the source like
>
> http://whatever.com
>
> 1] seemingly, notes are not created.
This is expected. You wouldn't want to create an empty note, would you?
> actually i don't mind this, because i don't want notes in this case.
>
> 2] the links get exported like
>
> [http://whatever.com]
>
> i get the same result if i export source that looks like
>
> <http://whatever.com>
>
> or
>
> [[http://whatever.com]]
>
> i do not know the standard, but i think that some email clients will
> not linkify this because of the brackets. are we sure that [] are
> canonical? not <>? is it the clients that are wrong?
>
> can this be customized so that the link can be exported totally bare
> without any bracket-like characters for maximum client linkification?
I changed it in master. Now, external links are wrapped within angle
brackets. Please let me know if it fixes the issue.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-02-10 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 4:26 is ascii link format canonical? can it be made more linkifiable? Samuel Wales
2018-02-06 19:43 ` Ben McGinnes
2018-02-10 13:18 ` Nicolas Goaziou [this message]
2018-02-10 18:58 ` Samuel Wales
2018-02-11 9:16 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgg1c79r.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.