emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suhail Singh <suhailsingh247@gmail.com>
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 10:09:05 -0500	[thread overview]
Message-ID: <87seqvk226.fsf@gmail.com> (raw)
In-Reply-To: <vishpb$ep4$2@ciao.gmane.io> (Max Nikulin's message of "Thu, 5 Dec 2024 22:44:43 +0700")

Max Nikulin <manikulin@gmail.com> writes:

> I have realized that ob-doc-gnuplot.org and org-babel-gnuplot.org files are
> quite similar.

Good catch!

The latter have not got some recent update though. I think, the
> former may use noweb to have source code blocks active while using the same
> content for exporting with header arguments.

> Are there any other reason why duplicated content exists? I would drop
> one file to avoid divergence.

Looking briefly into it, it's not clear to me that the inclusion of
org-babel-gnuplot.org in commit 394a6326881fc1f077ca8f4b891d8f133f80d305
wasn't an accident.

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.

PS: please include my address in replies.

-- 
Suhail


      reply	other threads:[~2024-12-10 15:10 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
2024-12-05 15:44 ` Max Nikulin
2024-12-10 15:09   ` Suhail Singh [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=87seqvk226.fsf@gmail.com \
    --to=suhailsingh247@gmail.com \
    --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).