Re: [ox-gfm]

[Corwin Brust]

On Tue, May 9, 2023 at 6:10 AM Uwe Brauer  wrote:
>
> > The README says loading ox-gfm adds it to the org-export-dispatch, I
> > tried doing (require 'ox-gfm) and it started showing up. But I don't
> > know if there is any other/better way to do that.
>
> Indeed, the require call is need.
>
> Sigh: the package system sometimes confuses me because the functions
> provided by ox-gfm were already available after installation, without
> the require command.
>

FWIW, I believe installing the package (at least, via package.el) will
load it (as a side effect?).

Can `org-capture` templates be made to result in a sub-heading of the current heading?

[Tim Visher]

Hey everyone,

Can `org-capture` templates be made to result in a sub-heading of the
current heading?

So

```
* This Week
** TODO A TODO Item

   [2023-05-05 Fri 10:47]

   A description 
```

and I whack my capture keychord and get

```
* This Week
** TODO A TODO Item

   [2023-05-05 Fri 10:47]

   A description
*** [2023-05-10 Wed 17:02]

[2023-05-10 Wed 17:02]


```

I have a tendency to make these items for longer running tasks that I want
to keep a journal on. The visibility cycling makes it easier to see my
progress over time.

Thanks in advance!

-- Tim Visher

Re: [ANN] lisp/ob-tangle-sync.el

[Mehmet Tekman]

Ihor Radchenko  writes:

> It will be great if you could do it.
> I have other things to work on.

Of course! I'm just a little unfamiliar on how one coordinates active
collaboration via mailing list :-)

Anyways - I did it, and it took less time than I thought

> We should modify it. For example like the following:
>
> 1. We will assume that :any can only occur one time in the exclusive
>groups. (Otherwise, there is no single definite way to parse header
>arguments)
> 2. Merge function will treat :any specially - when parameter does not
>match any of the argument values from all the groups combined, it is
>considered as :any and replace the previous corresponding values in
>its exclusive group, if any;
>In other words, we will need a special match for :any - "anything not
>equal to other values in all the groups combined".

I've modified the `merge' function within `org-babel-merge-params' so
that the main logic now accumulates a list of potential candidates that
could be the :any keyword, and selects the last added candidate as the
match.

The first two patches are very minor, simply adding
tangle-exclusive-groups using the existing code templates. The last
patch is the merge function rewrite.

It all seems to be passing tests, though I would like to add my toy.org
file to the org testing framework at some point.

Best,
Mehmet

>From eeb3f165498fcc420b862f67fb616b474a14b684 Mon Sep 17 00:00:00 2001
From: MT 
Date: Wed, 10 May 2023 17:38:22 +0200
Subject: [PATCH 1/3] * lisp/ob-core.el
 (org-babel-common-header-args-w-values): Added mutually exclusive tangle
 groups relating to desired tangle sync actions (e.g. :tangle
 (yes|no|) [(import|export|sync)])

---
 lisp/ob-core.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 65fa47ab5..013a37ce5 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -431,7 +431,8 @@ then run `org-babel-switch-to-session'."
 (sep	. :any)
 (session	. :any)
 (shebang	. :any)
-(tangle	. ((tangle yes no :any)))
+(tangle	. ((tangle yes no :any)
+   (import export skip sync)))
 (tangle-mode . ((#o755 #o555 #o444 :any)))
 (var	. :any)
 (wrap   . :any)))
-- 
2.40.1

>From 366a120a394d7783bf1640037ade31f826ef0277 Mon Sep 17 00:00:00 2001
From: MT 
Date: Wed, 10 May 2023 17:41:37 +0200
Subject: [PATCH 2/3] * lisp/ob-core.el (org-babel-merge-params): Tangle header
 with exclusive parameters can now be parsed, following the template of
 :exports and :results

---
 lisp/ob-core.el | 14 --
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index 013a37ce5..ed31a9de1 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2803,6 +2803,9 @@ parameters when merging lists."
 	 (exports-exclusive-groups
 	  (mapcar (lambda (group) (mapcar #'symbol-name group))
 		  (cdr (assq 'exports org-babel-common-header-args-w-values
+ (tangle-exclusive-groups
+	  (mapcar (lambda (group) (mapcar #'symbol-name group))
+		  (cdr (assq 'tangle org-babel-common-header-args-w-values
 	 (merge
 	  (lambda (exclusive-groups  result-params)
 	;; Maintain exclusivity of mutually exclusive parameters,
@@ -2822,7 +2825,7 @@ parameters when merging lists."
 	 params;Final parameters list.
 	 ;; Some keywords accept multiple values.  We need to treat
 	 ;; them specially.
-	 vars results exports)
+	 vars results exports tangle)
 (dolist (plist plists)
   (dolist (pair plist)
 	(pcase pair
@@ -2873,6 +2876,12 @@ parameters when merging lists."
(cond ((and value (functionp value)) (funcall value))
  (value value)
  (t ""))
+  (`(:tangle . ,value)
+   (setq tangle (funcall merge
+ tangle-exclusive-groups
+ tangle
+ (split-string
+  (or value "")
   ((or '(:dir . attach) '(:dir . "'attach"))
(unless (org-attach-dir nil t)
  (error "No attachment directory for element (add :ID: or :DIR: property)"))
@@ -2898,7 +2907,8 @@ parameters when merging lists."
 			  params)
 ;; Handle other special keywords, which accept multiple values.
 (setq params (nconc (list (cons :results (mapconcat #'identity results " "))
-			  (cons :exports (mapconcat #'identity exports " ")))
+			  (cons :exports (mapconcat #'identity exports " "))
+  (cons :tangle (mapconcat #'identity tangle " ")))
 			params))
 ;; Return merged params.
 (org-babel-eval-headers params)))
-- 
2.40.1

>From 6ce5313b7d3f0ab718072942f082bc259dccbae6 Mon Sep 17 00:00:00 2001
From: MT 
Date: Wed, 10 May 2023 17:44:42 +0200
Subject: [PATCH 3/3] * lisp/ob-core.el (org-babel-merge-params): Major 

Re: refiling heading onto itself

[General discussions about Org-mode.]

Oliver Epper  writes:

> When choosing the very same heading that is going to be refiled as its target 
> the message buffer states success but the heading is gone. This is
> version 9.5.5 of org-mode with emacs 28.2
>
> -*- mode: org -*-
> * one
> * two
> * three
>
> Try refiling two and choose two as the target. Result when started with emacs 
> -Q is:
>
> * one
> * three
>
> no error message.
>
> greetings
> Oliver Epper

Reproducible in built-in Org from 28.2 ("Org mode version 9.5.5
(release_9.5.5 @ /opt/src/emacs/base/emacs-28.2/lisp/org/)").

Also reproducible in built-in Org from recent master ("Org mode version
9.6.5 (release_9.6.5-3-g2993f4 @ /usr/share/emacs/30.0.50/lisp/org/)").

Didn't test the main branch -- haven't pulled in a few days and it is
too late today.  HTH.

Two problems I found in a hurry: (1) refiling "two" into "two" make the
entire thing gone.  (2) the completiong system shouldn't even provide
"two" as a completion candidate.

-- 
Best,


RY

Re: BUG: org-cycle does not unfold some subtrees

[William Denton]

On 10 May 2023, Ihor Radchenko wrote:


"Fraga, Eric"  writes:


And if it helps further, I have had this problem for some time now.  The
solution, for me, is to search for some text I know is present in the
folded section and it unfolds!  But the situation is sporadic and I
cannot reproduce it at will.


Does it also help if you run M-: (org-fold-core--clear-isearch-overlays)?


That worked!  I just had the problem.  I ran that, and the tree popped open!


Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
CO₂: 424.17 ppm (Mauna Loa Observatory, 2023-05-09)

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Jun Inoue]

On Wed, May 10, 2023 at 7:23 PM Timothy  wrote:

>
> Hi Jun,
>
> > You mention in a separate email that XeLaTeX is known to cause
> > hassles, but is this one of them? I could migrate to PDFLaTeX, but I'd
> > lose the convenience of editing with unicode-math.
>
> This is indeed one of the niggles we're currently aware of. Simply put,
> XeLaTeX seems to report sizing information differently, and that's
> rather unhelpful.
>
> Hopefully this will be addressed in the next few weeks, but in the
> meantime pdfLaTeX remains a good fallback.
>

Bummer, but it's good to know it's being worked on.   I'm no expert on this
stuff, so I'll just have to wait, I guess.  Thanks for clarifying!



>
> All the best,
> Timothy
>
> --
> Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at .
>


-- 
Jun Inoue

refiling heading onto itself

[Oliver Epper]

When choosing the very same heading that is going to be refiled as its
target the message buffer states success but the heading is gone. This is
version 9.5.5 of org-mode with emacs 28.2

-*- mode: org -*-
* one
* two
* three

Try refiling two and choose two as the target. Result when started with
emacs -Q is:

* one
* three

no error message.

greetings
Oliver Epper

Re: An Org-mode-based blogging engine?

[Vinícius Moraes]

Marcin Borkowski  writes:

> Hello fellow Orgers,
>
> I'm preparing to set up a new blog, and I'd like to have a fully
> Org-mode-based workflow.  Ideally, I'd like to be able to do everything
> - including publishing the posts - from within Emacs.
>
> I know about things like "Org publish" and ox-hugo, though I never used
> them - and there are probably others - but I'm asking specifically about
> two things:
>
> A. other people's experiences with similar workflows, and
> B. tool/workflow recommendations.
>
> Here are my requirements, in no particular order.
>
> 1. I want the blog to be fully static HTML+CSS, with a tiny sprinkling
> of (my custom) JS.
>
> 2. I want to publish a whole set of HTML files from a single Org mode
> file.  I will need to preserve internal links (so that I can link to
> another headline and the result will be one post linking to another),
> and of course I will need external links.  The blog will live on some
> server I will have ssh access to, so for publishing it should be enough
> to scp some files somewhere.
>
> 3. I want to be able to fully customize the HTML produced.  I want it to
> be as simple as possible (but see below).  I will also need it to be put
> in some kind of a template, so that every page will contain things like
> a header, footer and a sidebar.
>
> 4. I am going, though, to need some custom "blocks" - in HTML parlance,
> s and possibly also s.  I want to be able to mark them up
> somehow in my Org source and get  and  class="...">.  Reusing existing markup (like _underline_, which I'm not
> going to use) is not enough - I will need more than a dozen of those
> custom classes.
>
> Any thought, suggestions, recommendations?

I recommend using Hugo, since it supports org-mode files
directly. Setting up Hugo to meet your requirements can be done in
many ways, and you can find almost everything you need in their
documentation. Although there is a bit of a learning curve, it's nothing
that an Emacs user can't handle.

For integration and workflow, I've been using the easy-hugo package. It
has everything I've needed so far, from writing to publishing to
managing. While Hugo does support org files, there are some cases where
you need to tinker a bit to make it work properly. For example, the
other day, I was trying to publish a poem using verse blocks and it
didn't work. All I had to do was trying another way, which was adding
"//" at the end of each verse to have proper line breaking.

You'll learn many little things like this through experience, and if
needed, you can always use HTML/Go code to complement org-mode features.

Regardless of which tool path you choose, blogging with org-mode is a
great experience.

Enjoy the journey! :)

Best,
-- 
Vinícius Moraes
eternodevir.com

Re: [ANN] lisp/ob-tangle-sync.el

[Ihor Radchenko]

mtekma...@gmail.com writes:

>>In other words, we will need a special match for :any - "anything not
>>equal to other values in all the groups combined".
>
> Agreed, and I can try putting together something working in a day or
> two. Or, if this is something you can easily implement yourself, please
> do let me know.

It will be great if you could do it.
I have other things to work on.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Suggestion: for each listed keybinding, also name the command

[Ihor Radchenko]

Yuval Langer  writes:

> I have:
>
> - Added all the obvious commands to the `- {{{kbd(…)}}} ::` lines.

Thanks, but after your patch the manual does not compile.
Did you try to generate the guide via "make docs" after the patch?

> - Left several of these lines without a command where I've the manual
> do the same.

May you please list these?

> -- {{{kbd(S-TAB)}}}, {{{kbd(C-u TAB)}}} ::
> +- {{{kbd(S-TAB)}}} (~org-global-cycle~), {{{kbd(C-u TAB)}}} ::

Why nothing for C-u TAB?

> -- {{{kbd(C-c C-l)}}} (with point on existing link) ::
> +- {{{kbd(C-c C-l)}}} (with point on existing link) (~org-insert-link~) ::

This is inconsistent with other similar cases, where the key binding is
followed by some text. You added command name right after the key
binding, not after the text.
  
> -- {{{kbd(C-c C-c)}}} ::
> +- {{{kbd(C-c C-c)}}} (~org-toggle-checkbox~), {{{kbd(C-u C-c C-c)}}} ::

Why nothing for C-u ... ?
  
> -- {{{kbd(C-c / m)}}} or {{{kbd(C-c \)}}} ::
> +- {{{kbd(C-c / m)}}} or {{{kbd(C-c \)}}} (~org-match-sparse-tree~) ::

What about C-c / ?
  
>  #+attr_texinfo: :sep or
> -- {{{kbd(C-c [)}}} ::
> +- {{{kbd(C-c [)}}} (~org-agenda-file-to-front~) ::

Please, pay attention to :sep list attribute (see 13.14.9 Plain lists in
Tex info export). You need to change it here because "or" separator no
longer works as the command name contains "..or..". This change makes
the compilation fail.

Basically, you need to change the separator to, say, ";" and alter the
following list items accordingly. 

>Add current file to the list of agenda files.  The file is added to
>the front of the list.  If it was already in the list, it is moved
>to the front.  With a prefix argument, file is added/moved to the
>end.
>  
> -- {{{kbd(C-c ])}}} ::
> +- {{{kbd(C-c ])}}} (~org-remove-file~) ::

Same here.
  
> -- {{{kbd(r)}}}, {{{kbd(g)}}} ::
> +- {{{kbd(r)}}} (~org-agenda-redo~), {{{kbd(g)}}} ::

Why nothing for "g"?

>  #+attr_texinfo: :sep ,
> -- {{{kbd(C-c C-e t a)}}}, {{{kbd(C-c C-e t u)}}} ::
> +- {{{kbd(C-c C-e t a)}}} (~org-ascii-export-to-ascii~), {{{kbd(C-c C-e t 
> u)}}} ::

What about C-c C-e t u?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: BUG: org-cycle does not unfold some subtrees

[Fraga, Eric]

On Wednesday, 10 May 2023 at 08:19, Ihor Radchenko wrote:
> "Fraga, Eric"  writes:
>
>> And if it helps further, I have had this problem for some time now.  The
>> solution, for me, is to search for some text I know is present in the
>> folded section and it unfolds!  But the situation is sporadic and I
>> cannot reproduce it at will.
>
> Does it also help if you run M-: (org-fold-core--clear-isearch-overlays)?

I'll try to remember to try that next time the non-unfolding occurs.  I
should have added that I typically use evil-mode for org files, noting
that others have talked about spacemacs.

-- 
: Eric S Fraga, with org release_9.6.5-353-ge58bbd in Emacs 30.0.50

Re: [ANN] lisp/ob-tangle-sync.el

[mtekman89]

Ihor Radchenko  writes:

> 1. We will assume that :any can only occur one time in the exclusive
>groups. (Otherwise, there is no single definite way to parse header
>arguments)

Makes sense (or we could revamp all header parsing into some kind of
finite state machine… (I joke… for now…))

> 2. Merge function will treat :any specially - when parameter does not
>match any of the argument values from all the groups combined, it is
>considered as :any and replace the previous corresponding values in
>its exclusive group, if any; 

This is something that I do in my `org-babel--handle-tangle-args', where
the "filename" argument is the result of eliminating all other entries
in the group.

>In other words, we will need a special match for :any - "anything not
>equal to other values in all the groups combined".

Agreed, and I can try putting together something working in a day or
two. Or, if this is something you can easily implement yourself, please
do let me know.

Best,
Mehmet

Re: [PATCH] Highlight ANSI sequences in the whole buffer (was [PATCH] ANSI color on example blocks and fixed width elements)

[Ihor Radchenko]

Nathaniel Nicandro  writes:

> The attached patch now uses `org-element-at-point' and
> `org-element-context' to query for the bounds of elements.

Thanks!

> Note, I've also attached an updated example file which shows that the
> escape sequences in inline source blocks are now handled similarly to
> regular source blocks, i.e. they are not fontified.

I do not think that a single exception - source blocks is good enough.
When having something like
  ANSI opening term is ==, and closing term is ==
it will be not expected to get things fontified.

A better approach will be:
1. Do not allow ANSI sequences to intersect markup boundaries of the
   same AST depth:
   *bold * plain text  should not trigger fontification
   *bold  /italic/ * should trigger
   plain text  *bold* plain text  also should
2. Disallow fontification is certain contexts - 'inline-src-block

Further, your current code will do something weird when encountering
greater element:

:DRAWER:
Paragraph 

Another paragraph 
:END:

You should not consider greater elements when fontifying.

> +(cl-letf (((symbol-function #'delete-region)
> +   (lambda (beg end)
> + (add-text-properties beg end '(invisible t

This is fragile and relies on internal implementation details of
ansi-color.el. Is there another way?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Timothy]

Hi Jun,

> You mention in a separate email that XeLaTeX is known to cause
> hassles, but is this one of them? I could migrate to PDFLaTeX, but I'd
> lose the convenience of editing with unicode-math.

This is indeed one of the niggles we're currently aware of. Simply put,
XeLaTeX seems to report sizing information differently, and that's
rather unhelpful.

Hopefully this will be addressed in the next few weeks, but in the
meantime pdfLaTeX remains a good fallback.

All the best,
Timothy

--
Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
Learn more about Org mode at .
Support Org development at ,
or support my work at .

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Jun Inoue]

Hello Timothy, I love what you and Karthink have done here!  Typesetting is
so much faster now!  And the little nuggets like error reporting and
intelligent sizing & coloring is so going to boost my org QoL.  Thank you
so much for your work!

I've been trying this on and off for a few days now, and it works really
well, except for one thing.  I'm using XeLaTeX, and whenever I typeset a
LaTeX fragment containing a letter that sticks below the baseline (g, j, y,
etc), the fragment is typeset too small, almost like subscripts.  It
reproduces when this is the only setting I have:

(use-package org
:ensure nil
:custom
(org-latex-compiler "xelatex") ;; drop this line and the issue goes away
)

Minimal 1-line org file to trigger the bug:
abc $d$ $y$ -- the y is typeset too small compared to abc.  The d is just
the right size.

You mention in a separate email that XeLaTeX is known to cause hassles, but
is this one of them?  I could migrate to PDFLaTeX, but I'd lose the
convenience of editing with unicode-math.

On Sun, Mar 12, 2023 at 9:35 PM Timothy  wrote:

> Hi All,
>
> After months of work, Karthink and I have prepared a rather large patch-set
> completely overhauling the LaTeX preview system. I hope to have a patch set
> shortly, but in the mean time it would be good to get some more people
> testing
> this.
>
> To test this feature, please check out the `dev' branch of
>  (it’s the default branch).
> There are
> also some other changes there currently, but I don’t think anything is
> broken.
>
> You can view the almost-ready path set/diff here:
> , see the
> ORG-NEWS and org-manual entries to get a bit more of an idea of what’s
> changed.
> The short version is that now:
> • Previews are generated in bulk, and hundreds of LaTeX fragments can be
> processed per second.
> • Images are placed continuously as they are generated.
> • Preview generation is asynchronous and will not block Emacs.
> • Inline previews are aligned and scaled to match the font baseline and
> size.
> • Previews scale along with text when the text scale is changed.
> • Previews are coloured to match surrounding text and the active theme.
> • SVG previews automatically change colors when the active theme changes.
> • Error encountered when compiling LaTeX fragments can be accessed by
> mousing over preview images.
> • Preview overlays can hide and show themselves dynamically based on
> cursor position.
> • Org mode can auto-generate LaTeX previews as you type or edit the text
> of existing ones.
> • Org mode can keep equation numbering consistent by regenerating previews
> as needed.
>
> If you do come across any issues, please let me know either in a reply
> here or
> the org-mode matrix room. If you could also run
>  and
> share the
> diagnostic info, that would be quite helpful.
>
> Lastly, Karthink has prepared a video giving an overview of the new
> capabilities, you can give it a watch here:
> 
>
> All the best,
> Timothy
>
> --
> Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at .
>


-- 
Jun Inoue

Re: [ANN] lisp/ob-tangle-sync.el

[Ihor Radchenko]

Mehmet Tekman  writes:

> I'm having some problems getting:
>
>  `:tangle > [import/export/both/skip]'
>
> to work nicely with the existing framework. The main issue lies in the
> `:any` keyword in `org-babel-common-header-args-w-values' for the tangle
> entry making it difficult to determine where one exclusionary group
> begins and where the other ends.
>
> e.g.
>
> (defconst org-babel-common-header-args-w-values
> ...
> (tangle   . ((tangle yes no :any)
>  (import export skip sync)))
> ...
> )

And the reason is that tangle function inside `org-babel-merge-params'
does not know how to handle :any in exclusive groups.

We should modify it. For example like the following:

1. We will assume that :any can only occur one time in the exclusive
   groups. (Otherwise, there is no single definite way to parse header
   arguments)
2. Merge function will treat :any specially - when parameter does not
   match any of the argument values from all the groups combined, it is
   considered as :any and replace the previous corresponding values in
   its exclusive group, if any;
   In other words, we will need a special match for :any - "anything not
   equal to other values in all the groups combined".

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: BUG: org-cycle does not unfold some subtrees

[Ihor Radchenko]

"Fraga, Eric"  writes:

> And if it helps further, I have had this problem for some time now.  The
> solution, for me, is to search for some text I know is present in the
> folded section and it unfolds!  But the situation is sporadic and I
> cannot reproduce it at will.

Does it also help if you run M-: (org-fold-core--clear-isearch-overlays)?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: BUG: org-cycle does not unfold some subtrees

[Fraga, Eric]

On Saturday,  6 May 2023 at 07:46, Thomas S. Dye wrote:
> If it helps, I get this bug using the Spacemacs Org mode layer and
> Emacs 27.

And if it helps further, I have had this problem for some time now.  The
solution, for me, is to search for some text I know is present in the
folded section and it unfolds!  But the situation is sporadic and I
cannot reproduce it at will.

-- 
: Eric S Fraga, with org release_9.6.5-353-ge58bbd in Emacs 30.0.50

Re: Org-mode publish: Some questions when use it for a blog

[Christian Moe]

>> But, generate a RSS feed with ox-rss [1] give me some problems. The
>> README is not really clear on what the Org-mode file should look. And it
>> seems to be done to generate RSS when all blog posts are a headline in
>> the same document. But on my blog, each blog post is on a different
>> document.
>
> Well. You can define a derived dackend for ox-rss. It will require some
> Elisp though. Check out `org-export-define-derived-backend' call in
> ox-rss.el.
>
> Alternatively, I am pretty sure that a number of rss generators already
> exist for static blogs. They are more likely to work using multiple
> individual html pages as input.

I've seen several people solving this by adapting the sitemap
functionality in org-publish, since the sitemap already pulls together
information about different pages. You can configure org-publish to use
a bespoke sitemap-function that formats the sitemap as an Org file
suitable for RSS export with ox-rss. This looks like a clear explainer:

  https://writepermission.com/org-blogging-rss-feed.html

Yours,
Christian