Re: Suggestion with footnotes when toggling headlines into plain lists

2022-11-10 Thread Ihor Radchenko
Ihor Radchenko writes: >> ~C-c -~ turns that into a list where footnotes definitions can't be >> found. It gives, for example, problems when exporting or when more >> footnotes are added: >> >> * Main headline >> - Headline 1 >>   [fn:1] >> >>   [fn:1] >> - Headline

[MAINTENANCE] Do we have any backwards-compatibility policy for third-party packages?

2022-11-10 Thread Ihor Radchenko
Hi, Org promises to support the last three Emacs releases. However, it is less clear what is our policy wrt third-party packages. We do need third-party packages, for example, in babel backends. Sometimes, we have to make changes to the ob-*.el files in order to accommodate changes in the require

Re: [PATCH] Bind calendar-debug-sexp to non-nil when running tests (was: problem with diary sexps)

2022-11-10 Thread Ihor Radchenko
Ihor Radchenko writes: > I guess we can permanently bind calendar-debug-sexp to non-nil in tests. > It should help if we encounter diary-related issues in future. Applied onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c41a2198f2d7a3fbae5953f4b25c84cbe6692e2e -- Ihor

Re: [PATCH] Re: [BUG] Make org-html-htmlize-output-type safe [9.5.2 (release_9.5.2-9-g7ba24c @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]

2022-11-10 Thread Ihor Radchenko
Ihor Radchenko writes: > Can be done. Like in the attached patch. Applied onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4517fba441444fa6a2fb167787a6e813d7004c80 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG] phantom newlines while moving headings [9.6-pre ( @ /home/chomwitt/.config/emacs/elpa/org-9.6pre0.20221110.85807/)]

2022-11-10 Thread Ihor Radchenko
chomw...@posteo.eu writes: > It follows a possible org chunk that reproduce the phantom newlines that > are created while trying to move a headline from a state where there > are no newlines between the headers. Could you please provide more information? Which headline should I move to reproduce

Re: [BUG] org-babel-comint-with-output: incorrect prompt detection [9.6-pre]

2022-11-10 Thread Ihor Radchenko
Bruno Barbier writes: > For example, using a haskell prompt, let say the prompt is "Prelude> ", > the first incoming text is "Pre", the second incoming text is > "lude> ", o-b-c-w-o will wrongly infer that "lude> " is the prompt, > and that "Pre" was part of the previous value/output. The proble

Re: [BUG] LaTeX export in non-English language [9.6-pre (release_9.5.5-1087-g620a96.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

2022-11-10 Thread Ihor Radchenko
Juan Manuel Macías writes: >> And exported to pdf (C-c C-e l o). >> Surprisingly, the output is in English. >> >> Am I missing something? > > You need to explicitly load babel or polyglossia: > > For polyglossia (`org-latex-guess-polyglossia-language'): > > #+LaTeX_Header: \usepackage[AUTO]{polyg

[BUG] phantom newlines while moving headings [9.6-pre ( @ /home/chomwitt/.config/emacs/elpa/org-9.6pre0.20221110.85807/)]

2022-11-10 Thread chomwitt
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. --

[BUG] org-babel-comint-with-output: incorrect prompt detection [9.6-pre]

2022-11-10 Thread Bruno Barbier
Hi, The function `org-babel-comint-with-output' (o-b-c-w-o) may not detect prompts correctly. The function o-b-c-w-o checks if the incoming arbitrary chunk of text contains whole prompts, and replace them. But the incoming text may contain an incomplete prompt at the end. When this happens, it

Re: [PATCH] ob-java: Define the list of all supported header arguments

2022-11-10 Thread Bruno Barbier
Ihor Radchenko writes: > Then, it sounds like local.mk does not enable java tests. > > I fixed such scenario on main. > Now, java tests will be skipped when ob-java testing is not requested. That works for me now, with or without java in local.mk. Thanks for the patch and the explanation! Bru

Re: [BUG] LaTeX export in non-English language [9.6-pre (release_9.5.5-1087-g620a96.dirty @ /home/yantar92/.emacs.d/straight/build/org/)]

2022-11-10 Thread Juan Manuel Macías
Ihor Radchenko writes: > I am trying to look into RTL language exports. > > I tried the following simple-minded Org file: > > #+title: Temp > #+LATEX_COMPILER: lualatex > > #+LANGUAGE: HE > > \begin{equation} > f(x) = \frac{8}{7} > \end{equation} > > #+begin_src python :exports code > for i in ran

Re: Volunteering to maintain ob-asymptote.el within Org

2022-11-10 Thread Jarmo Hurri
Greetings Ihor. Ihor Radchenko writes: > Jarmo, did you hear anything from Luc? There was no action in > ob-asymptote for over a year. If the current maintainer does not reply > to email requests related to ob-asymptote, I'd rather transfer to > maintenance to someone more active. Nope. I sen

Re: [PATCH] ob-java: Define the list of all supported header arguments

2022-11-10 Thread Ihor Radchenko
Bruno Barbier writes: > I'm seeing these 3 failures too, running the tests from the command > line. The failure looks like this: > > FAILED ob-java/lint-header-args-block ((should-not (org-lint > '(wrong-header-argument))) :form (org-lint (wrong-header-argument)) > :value ((1 ["8" "ni

Re: [PATCH] ob-java: Define the list of all supported header arguments

2022-11-10 Thread Bruno Barbier
Ihor Radchenko writes: > Rudolf Adamkovič writes: > >> Overall, I now see the following failures on the main branch: >> >>FAILED ob-java/lint-header-args-block >>FAILED ob-java/lint-header-args-buffer >>FAILED ob-java/lint-header-args-heading > > AFAIK, Max is using Linux. This

Re: [FR] Allow TITLE to be used as default export file name (was: [BUG] EXPORT_FILE_NAME keyword is used by `org-export-output-file-name' before macro expansion/INCLUDEs/removing COMMENTed trees (was:

2022-11-10 Thread Ihor Radchenko
alain.coch...@unistra.fr writes: > > > > I recommend you to use :EXPORT_FILE_NAME: headline property and > > > > export using subtree scope. > > > > > > Thanks a lot for the tip. A suggestion: that the :TITLE: > > > property be used if it exists. > > > > We currently fall back to file nam