Hello,
Michael Brand writes:
> I am not 100 % sure whether it is related with the above changes. But
> could you please check again if the merge conflict in lisp/ox-html.el
> between maint and master was resolved correctly with your merging
> commit fffd055ac5e920e744e350a1ad164494aec9fa91 on ma
Hi Nicolas
On Wed, Apr 16, 2014 at 9:15 AM, Nicolas Goaziou wrote:
> I suggest the following for the 8.2.6 release:
>
> - revert the whole patches line
>
> - at the parser level
>
> - if scheme is not "file" or derived (e.g., "file+sys" or
> "docview"), assume PATH is a correct URI
Nicolas Goaziou writes:
> Bastien writes:
>
>> Nicolas Goaziou writes:
>>
>>> FWIW, I vote for regular URI mailto:j...@doe.com?subject=Test.
>>
>> Yep, 100% agreed.
>
> Done in b9f2e17f07faf01109fc6f7f1eb5a34e0f97eafb.
Works fine, thanks!
--
Bastien
Bastien writes:
> Nicolas Goaziou writes:
>
>> FWIW, I vote for regular URI mailto:j...@doe.com?subject=Test.
>
> Yep, 100% agreed.
Done in b9f2e17f07faf01109fc6f7f1eb5a34e0f97eafb.
Regards,
--
Nicolas Goaziou
Hi Nicolas,
Nicolas Goaziou writes:
>> Indeed, please go ahead with this plan when you can.
>
> Done.
Thanks,
> FWIW, I vote for regular URI mailto:j...@doe.com?subject=Test.
Yep, 100% agreed.
--
Bastien
Hello,
Bastien writes:
> Indeed, please go ahead with this plan when you can.
Done.
> Also, `org-open-at-point' needs to correctly deal with links
> like mailto:j...@doe.com?subject=Test -- I think it used to
> work but the subject is not parsed correctly here.
I don't think it ever worked. A
Hi Nicolas,
Nicolas Goaziou writes:
> I suggest the following for the 8.2.6 release:
>
> - revert the whole patches line
>
> - at the parser level
>
> - if scheme is not "file" or derived (e.g., "file+sys" or
> "docview"), assume PATH is a correct URI and do not change
> anyt
Nicolas Goaziou writes:
[…]
> I think it is sufficient for 8.2.6. We can still discuss if more
> parsing is needed for 8.3.
I agree that this should take care of it. Unless Org honestly tries to
be RFC3986 conformant in the future, I don't really see the point in
further changes at the moment.
I suggest the following for the 8.2.6 release:
- revert the whole patches line
- at the parser level
- if scheme is not "file" or derived (e.g., "file+sys" or
"docview"), assume PATH is a correct URI and do not change
anything ;
- otherwise, if PATH is absolute and do no
Achim Gratz writes:
> groff has this snippet:
>
>
> (if (file-name-absolute-p raw-path)
> (concat "file://" (expand-file-name raw-path))
> (concat "file://" raw-path)))
This needs to be fixed, along with ox-man.el. Anyway, that wasn't
i
Nicolas Goaziou writes:
> With latest patch and following Org buffer
>
> file:test.org
> file:/test.org
> file:///test.org
>
> I get (HTML export)
>
> test.html
> file:///test.html
> file:///test.html
>
> So, it looks good so far.
groff has this snippet:
--8<---cut here---
Hello,
Achim Gratz writes:
> It still isn't correct. If you put "//" after a "file:" scheme, then
> you need to put an authority there (an empty authority means localhost
> in some contexts, but then the path has to start with a slash).
The patch didn't change "file" scheme handling. It chang
Nicolas Goaziou writes:
> Correct. It should be fixed.
It still isn't correct. If you put "//" after a "file:" scheme, then
you need to put an authority there (an empty authority means localhost
in some contexts, but then the path has to start with a slash). Also,
with the new implementation rel
Hello,
Bastien writes:
> 1. create a file with "http://orgmode.org"; as its contents
> 2. export it to HTML
> 3. the exported link is wrong: http:orgmode.org
>
> I guess it has to do with this commit:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=3589f6
>
> Can you double-check?
Correct
14 matches
Mail list logo
