org-mode team on gratipay

org-mode team on gratipay

[Bastien Guerry]

Hi all,

I created a team for org-mode on gratipay.com:

https://gratipay.com/org-mode/

If you are contributing to org-mode, either in core, "contrib/"
or by publishing code related to Org, don't hesitate to join the
team to receive donations.

Thanks!

-- 
 Bastien

Bug: "file:" protocol link with "#anchor" bad HTML export [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)]

[Philip Hudson]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

    https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------

I add into Worg file "worg-faq.org" a hyperlink using the "file:"
protocol, linking to a sub-heading in Worg file "worg-git.org". Exact
syntax quoted below, from an email thread with Bastien.

Expected behavior:

I expect the HTML exporter automatically used by Worg to generate an
"https:" protocol hyperlink which links to a specific, existing HTML
anchor ID in file "worg-git.html".

Actual behavior:

The exporter generates an "https:" protocol hyperlink that points to a
non-existent anchor ID in file "worg-git.html".

I have left the mis-generated link in place on Worg for the time
being. (My previous push included a correct, explicit "https:"
protocol link; I can revert and push again at any time). You can
examine it at:

  https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development

at the bottom of list item 2.


See below for the exact syntax of the Org link.



Emacs  : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5)
of 2017-09-12 on hullmann, modified by Debian
Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpa @
/home/phil/.emacs.d/elpa/org-9.1.14/)



---------- Forwarded message ---------
From: Bastien <bzg@gnu.org>
Date: Mon, 12 Nov 2018 at 06:19
Subject: Re: Worg commit privs
To: Philip Hudson <phil.hudson@iname.com>


Hi Philip,

Philip Hudson <phil.hudson@iname.com> writes:

> Doesn't look right. The generated link points to a non-existent id:
>
>     https://orgmode.org/worg/worg-git.html#org2c2081f
>
> This is the link in the Org source, created using "C-c l" followed by "C-c C-l":
>
>     file:worg-git.org::*The%20first%20time%20you%20contribute%20to%20Worg

It looks like a bug.

The section has a CUSTOM_ID property, and the value of this property
is used as the HTML anchor, but the stored link uses another method
when exporting to HTML, hence the bug.

Could you report it to the mailing list?  Don't forget to mention your
Org version and a minimal recipe on how to reproduce the bug.  It is
important enough to block the release of Org 9.2.

I won't have time to look at it before nov. 19th, though.  I hope
Nicolas or someone else can have a look.

Thanks!

--
 Bastien


-- 
Phil Hudson                  http://hudson-it.ddns.net
Pretty Good Privacy (PGP) ID: 0x4E482F85

Re: Bug: "file:" protocol link with "#anchor" bad HTML export [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)]

[Nicolas Goaziou]

Hello,

Philip Hudson <phil.hudson@iname.com> writes:

> I add into Worg file "worg-faq.org" a hyperlink using the "file:"
> protocol, linking to a sub-heading in Worg file "worg-git.org". Exact
> syntax quoted below, from an email thread with Bastien.
>
> Expected behavior:
>
> I expect the HTML exporter automatically used by Worg to generate an
> "https:" protocol hyperlink which links to a specific, existing HTML
> anchor ID in file "worg-git.html".
>
> Actual behavior:
>
> The exporter generates an "https:" protocol hyperlink that points to a
> non-existent anchor ID in file "worg-git.html".
>
> I have left the mis-generated link in place on Worg for the time
> being. (My previous push included a correct, explicit "https:"
> protocol link; I can revert and push again at any time). You can
> examine it at:
>
>   https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development
>
> at the bottom of list item 2.

My guess is that Worg cache is invalid, somehow. I cannot debug it
further since I do not have acces to Worg.

Bastien, I think we should delete the cache file and re-publish
everything to get the cache right.

> Could you report it to the mailing list?  Don't forget to mention your
> Org version and a minimal recipe on how to reproduce the bug.  It is
> important enough to block the release of Org 9.2.

I don't see why it would be a blocker for Org 9.2.

Regards,

-- 
Nicolas Goaziou