From: Ihor Radchenko <yantar92@posteo.net>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH worg v2] ob-doc-gnuplot.org: Fix broken link to source.
Date: Wed, 25 Dec 2024 13:02:20 +0000 [thread overview]
Message-ID: <871pxv29wj.fsf@localhost> (raw)
In-Reply-To: <87seqvk226.fsf@gmail.com>
Suhail Singh <suhailsingh247@gmail.com> writes:
> It might make sense to include an examples/plotting.org at some point,
> with very different content. But as things stand today I believe of the
> two files ob-doc-gnuplot.org is the one that should be retained and if
> there's any meaningful information contained in org-babel-gnuplot.org
> which isn't yet in ob-doc-gnuplot.org that it should be assimilated into
> ob-doc-gnuplot.org.
ob-doc-gnuplot.org should aim to become a part of the manual.
So, it should not be more verbose than necessary.
Any extra examples or discussion may move to a dedicated WORG page.
--
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>
prev parent reply other threads:[~2024-12-25 13:01 UTC|newest]
Thread overview: 9+ 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
2024-12-12 4:18 ` Linking source files on worg (was: Re: [PATCH worg v2] ob-doc-gnuplot.org: Fix broken link to source.) Max Nikulin
2024-12-05 15:44 ` [PATCH worg v2] ob-doc-gnuplot.org: Fix broken link to source Max Nikulin
2024-12-10 15:09 ` Suhail Singh
2024-12-25 13:02 ` Ihor Radchenko [this message]
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=871pxv29wj.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=suhailsingh247@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).