Zeremonienmeister Berber Aab <[email protected]> writes: > When exporting an org timestamp with `org-display-custom-times` enabled, > it produces the timestamp as defined in `org-timestamp-custom-formats` > by calling `org-timestamp-translate` (at least in most org exporters). > > The documentation for `org-timestamp-custom-formats` says: `Leading "<" > and trailing ">" pair will be stripped from the format > strings.`, which is not the case, this does not happen. > > So, according to the documentation, within the function definition of > `org-timestamp-translate`, the function `org-time-stamp-format` should > be evaluated with argument 'no-brackets.
Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f7238772e For export, the original behavior is that the brackets (if any) are preserved. However, since Org 9.6, the brackets were added unconditionally regardless whether brackets are present in the custom format or not. I now fixed that regression. > As a side note: I used to think that the org-display-custom-times must > start and end with angled brackets. But apparently this is not true. > Or does this have advantages for something? It used to in Org 9.5.5 and earlier because first and last symol of the format were unconditionally stripped. Since Org 9.6, only [...] and <...> are stripped, so you no longer have to put brackets or anything else in the format to not break things. -- 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>
