adjustments to avoid breaking
compatibility. I wouldn't recklessly jump into trying to making direct
modifications.
Parsing these timestamps manually isn’t a big deal, but I’m
curious — has there ever been discussion about extending this to a
triplet structure (date, date+time, date+time+seconds) for more
flexibility?
Regards
Yue Yi
Ihor Radchenko 2025.04.14 01:07 writes:
> > Parsing these timestamps manually isn’t a big deal, but I’m
> > curious — has there ever been discussion about extending this to a
> > triplet structure (date, date+time, date+time+seconds) for more
> > flexibility?
>
> I do not recall any requests about
Hello, org-mode maintainers,
Out of interest in the org babel feature and frequent use of org-mode,
after reading https://orgmode.org/worg/org-contribute.html and some
discussions, I think I have some time to help maintain ob-emacs-lisp.el or
some other modules later.
Is there anything I can do?
> Please check out
> https://orgmode.org/worg/org-maintenance.html#maintainer-role page to
> familiarize yourself with our maintenance practices.
> Then, follow https://orgmode.org/worg/org-contribute.html#devs
>
> I note that you joined the mailing list recently, so I'd like to see a
> couple of p
Ihor Radchenko 于2025年6月19日周四 18:10写道：
>
> Yue Yi writes:
>
> > When exporting a file containing many timestamps, I noticed while
> > inspecting the HTML code that the timestamps inside elements have
> > an extra space. Here's a minimal example:
>
> Fixed, o
Hello, Org-mode maintainers,
When exporting a file containing many timestamps, I noticed while
inspecting the HTML code that the timestamps inside elements have
an extra space. Here's a minimal example:
(org-export-string-as "Hello [2025-05-05] world" 'html t) ;;=>
"
Hello [2025-05-05 Mon] worl
Hello Org-mode maintainers,
I'd like to submit a patch to fix a bug in ox-html's Table of Contents
(TOC) generation. The bug occurs when an Org document's first headline
is not at level 1 (e.g., it starts with **), causing an unbalanced
tag in the exported HTML. Try `C-c C-e h H' for text below:
Ihor Radchenko writes:
> > #+title: test
> > #+options: html-style:nil html-preamble:nil html-postamble:nil
> > ** a
> > * b
> ...
>
> > toc-id-counter) ""))
> > - (org-html--toc-text toc-entries)
> > + (org-html--toc-text toc-entries scope)
>
> Why do you need to pass SCOPE?
In ox-html.el,
Ihor Radchenko writes:
> > In other words, when scope is non-nil, we can always obtain an Org
> > element with a logical hierarchical structure. However, when scope is
> > nil, we may not be able to do so, as explained in my previous
> > email. This is why I introduced the scope parameter.
>
> Ok
Yue Yi writes:
> > > In other words, when scope is non-nil, we can always obtain an Org
> > > element with a logical hierarchical structure. However, when scope is
> > > nil, we may not be able to do so, as explained in my previous
> > > email. This is
Ihor Radchenko writes:
> I have a few comments about the commit message.
> [...]
> We generally put changelog entries at the beginning, optionally
> following by explanation, not wise versa. We also `quote' Elisp symbols
> and leave two spaces between sentences. See
> https://orgmode.org/worg/o
Ihor Radchenko writes:
>
> Yue Yi writes:
>
> > Here is the improved patch.
> > From 7db5f6fa55f6d082e911b8e852fe5ecd47878ebd Mon Sep 17 00:00:00 2001
> > From: Yue Yi
> > Date: Sat, 9 Aug 2025 12:31:41 +0800
> > Subject: [PATCH] ox-html: Fix TO
12 matches
Mail list logo
