From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH worg v2] ob-doc-gnuplot.org: Fix broken link to source.
Date: Tue, 10 Dec 2024 19:25:52 +0000 [thread overview]
Message-ID: <87ikrrwda7.fsf@localhost> (raw)
In-Reply-To: <vine52$16fh$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
> On 03/12/2024 02:32, Suhail Singh wrote:
>> Max Nikulin writes:
>>
>> For now, I simply wanted to ensure the link was no longer broken. Feel
>> free to discard the patch in favor of another that addresses the issue
>> generically.
>
> I have pushed a commit changing worg/sources/ links to git.sr.ht in 3
> files. Accordingly to
>
> git grep --count \
> '\[https://git\.sr\.ht/~bzg/worg/tree/master/item/[^]]*\.org\]'
> git grep --count '\[https://orgmode.org/[^]]*\.org\]'
>
> the former used more often. HTML files will be updated when Ihor push
> some changes next time.
Ideally, we want to use a simple [[./file.org]] links. But it is
actually tricky because of `org-html-link-org-files-as-html'.
So, direct http link has to do for now.
> I recall a discussion whether a link to source file should be added to
> every worg page.
Do you have a link to that discussion?
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-12-10 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 16:26 [PATCH worg v2] ob-doc-gnuplot.org: Fix broken link to source Suhail Singh
2024-12-02 15:23 ` Max Nikulin
2024-12-02 19:32 ` Suhail Singh
2024-12-03 17:11 ` Max Nikulin
2024-12-10 19:25 ` Ihor Radchenko [this message]
2024-12-05 15:44 ` Max Nikulin
2024-12-10 15:09 ` Suhail Singh
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=87ikrrwda7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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 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).