Re: [orgweb/zh-CN] [DRAFT PATCH v7] Tentative zh-CN translation

Ihor Radchenko writes: > Ruijie Yu writes: > >>> -org-mode-parser >>> +/org-mode-parser/ >>> >>> This probably belongs to the English version as well. >> >> Should the English version change belong to a new commit, unrelated to >> the translation patchset? Or would I just modify it in the

Re: Major mode of orgweb/publish.sh?

Bastien Guerry writes: > Ihor Radchenko writes: > >>> Converted the `load' into `require' because it allows someone working on a >>> local >>> repo to `eval-buffer' successfully, given that the individual installs these >>> dependencies from GNU/NonGNU Elpa. Previously, due to the

Re: [BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

Ihor Radchenko writes: > "Garid Z." writes: > >> | 3 | =>>>=| =<<<=| >> | 4 | == | == | >> ... >> Resulted PDF file has » and « symbols (maybe: U+00BB, U+00AB) >> instead of 2 normal < symbols. >> ... >> Solution for this might be almost identical with the previous fix. >>

Re: [BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

On 20/04/2023 22:00, Ihor Radchenko wrote: Max Nikulin writes: While \texttt is used, this source of bugs would not exhaust soon. Maybe we can somehow use `org-latex--protect-text' in `org-latex--protect-texttt'. Unfortunately it does not cover the case of babel shortcuts like "<">.

Re: [BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

Max Nikulin writes: > While \texttt is used, this source of bugs would not exhaust soon. Maybe we can somehow use `org-latex--protect-text' in `org-latex--protect-texttt'. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org

Re: [BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

On 20/04/2023 21:18, Ihor Radchenko wrote: +(cond ((equal m ">>") ">{}>{}") +(cond ((equal m "<<") "<{}<{}") Thanks for reporting! Fixed, on bugfix. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=27ee55ebf While \texttt is used, this source of bugs would not exhaust

Re: [BUG] No font lock in src blocks for shells in org-babel-shell-names (was Re: Font lock for org-babel shell scripts?)

On 17/04/2023 22:21, Ihor Radchenko wrote: Matt writes: I was able to resolve it by simply requiring `sh-script' in `org-src'. Committed and pushed. Note that it will break Emacs 26. org-protocol.el defines polyfill for `flatten-tree'.

Re: [BUG] Org-LaTeX-export: >> and << (inside of ~code~/=verbatim=) gets exported to single monospace symbol instead of 2 monospace symbols [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

"Garid Z." writes: > | 3 | =>>>=| =<<<=| > | 4 | == | == | > ... > Resulted PDF file has » and « symbols (maybe: U+00BB, U+00AB) > instead of 2 normal < symbols. > ... > Solution for this might be almost identical with the previous fix. > Maybe something like: > > +(cond

Re: [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table)

Ihor Radchenko writes: > It looks like "backend" is more popular at the end. > > I will go for it everywhere unless there are objections. Done on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f81ba451a -- Ihor Radchenko // yantar92, Org mode contributor, Learn more

How to set priority of a heading with the highest one among its children

Given this tree : * TODO Main [#2] ** DONE Child1 [#0] ** TODO Child2 [#3] ** TODO Child3 [#4] *** TODO Subchild1 [#1] *** TODO Subchild2 [#2] I would like that the priority of parent headings be automatically set to the highest priority among its note done children. So, in previous example,

Re: [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)]

Ihor Radchenko writes: > Ruijie Yu writes: > >>> Compiler list may also be nil. >> >> This should be covered by the repeat case? Unless you want to be explicit >> about this, in which case you can wrap it in a choice, whose first choice >> being (const :tag “description” nil), and the second

Re: [PATCH v2] Add compat.el support to Org (was: [POLL] Use compat.el in Org? (was: Useful package? Compat.el))

Max Nikulin writes: >> Sure. And you will have such option (EFLAGS). >> However, I decided to enable auto-downloading by default to not break >> the previous working compilation instructions. > > For me adding external dependencies is strong enough reason to change > compiling instructions. My

Re: [ANN] org-jami-bot

Hanno Perrey writes: > Do you know of a maintained XMPP client written in Elisp to start looking > into? Also, consider ERC and ement.el. For XMPP, https://codeberg.org/emacs-jabber/emacs-jabber, AFAIK. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)]

Ruijie Yu writes: >> Compiler list may also be nil. > > This should be covered by the repeat case? Unless you want to be explicit > about this, in which case you can wrap it in a choice, whose first choice > being (const :tag “description” nil), and the second choice being the repeat > case.

Re: [PATCH] ox.el: Customize org-export-dispatch options

Jim Wisniewski writes: >> Now, need to wait until your copyright is in order. > > Okay, I just emailed back my signed copyright assignment. Thanks! Let us know when FSF replies with a countersignature. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG] Org publish makeindex doesn't work on symlinked path [9.6.4 ( @ /home/bence/src/org-mode/lisp/)]

Bence Fábián writes: > - org-publish calling `file-truename' inconsistently during the > publishing process. May you check which places are not calling `file-truename'? We should certainly be consistent here, either by preferring relative paths to the true paths. -- Ihor Radchenko //

Re: [BUG] Org publish makeindex doesn't work on symlinked path [9.6.4 ( @ /home/bence/src/org-mode/lisp/)]

Hi all, Upon further reflection I came to the following conclusions: There are multiple things at play here (I refrain from using the word "issue"): - emacs resolving or not resolving true path upon visiting files. This is not at all org-related. - org-publish calling `file-truename'

Re: [ANN] org-jami-bot

On 18/04/2023 02:22, Hanno Perrey wrote: =org-jami-bot= provides hooks and functions that extend this to Org mode captures. Thank you for the idea (I can not say anything concerning implementation yet) to take advantage of messenger infrastructure for CLI variant of org-capture. Certainly it