From: Simon Thum <simon.thum@gmx.de>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: Org-link-escape-chars (was Incorrect hexification in URLs in LaTeX Export)
Date: Mon, 17 Mar 2014 13:24:24 +0100 [thread overview]
Message-ID: <5326E978.2020702@gmx.de> (raw)
In-Reply-To: <87y50nele8.fsf@med.uni-goettingen.de>
Hehe ;) No, I was merely suggesting that maybe someone tried too hard to
fix non-working urls becauase of other use cases.
Luckily it seems fixed now.
On 03/06/2014 10:17 AM, Andreas Leha wrote:
> "R. Michael Weylandt" <michael.weylandt@gmail.com> writes:
>
>> On Tue, Mar 4, 2014 at 3:45 PM, Simon Thum <simon.thum@gmx.de> wrote:
>>> This seems to be a question of objective. Do you want to encode, i.e.
>>> maintain some reversible original in an url no matter what, or do you want
>>> to fix url's which wouldn't otherwise be legal? In the latter case, the
>>> question mark should probably be retained.
>>>
>
> I am not sure, that I understand what you say here. But in case you
> want to convince me, that exporting non-working links when the user
> supplies working links is a feature and not a bug, you will have a hard
> time ;-)
>
> - Andreas
>
>>
>> I believe the former. If the user types in a working link, the
>> exporter shouldn't break it.
>>
>> This could be fixed by sprinkling org-url-decode through various
>> backends, but that suggests to me that the problem may be "upstream."
>>
>> Michael
>
>
>
next prev parent reply other threads:[~2014-03-17 12:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:51 Incorrect hexification in URLs in LaTeX Export R. Michael Weylandt <michael.weylandt@gmail.com>
2014-02-28 20:26 ` Andreas Leha
2014-03-03 20:06 ` Org-link-escape-chars (was Incorrect hexification in URLs in LaTeX Export) R. Michael Weylandt <michael.weylandt@gmail.com>
2014-03-04 20:45 ` Simon Thum
2014-03-06 2:58 ` R. Michael Weylandt
2014-03-06 9:17 ` Andreas Leha
2014-03-17 12:24 ` Simon Thum [this message]
2014-03-12 18:47 ` Incorrect hexification in URLs in LaTeX Export Bastien
2014-03-17 21:31 ` Andreas Leha
2014-03-18 15:41 ` Bastien
2014-03-18 21:24 ` R. Michael Weylandt <michael.weylandt@gmail.com>
2014-03-19 14:37 ` R. Michael Weylandt <michael.weylandt@gmail.com>
2014-05-25 5:56 ` Bastien
2014-05-25 7:09 ` David Maus
2014-05-25 7:18 ` Bastien
2014-05-25 7:22 ` David Maus
2014-05-26 5:16 ` Bastien
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=5326E978.2020702@gmx.de \
--to=simon.thum@gmx.de \
--cc=andreas.leha@med.uni-goettingen.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).