Re: Broken numerical ordered list when exported to latex

Sharon Kimble writes: > Could the manual be amended to show how to use it with an example like the > one you showed above please? Sure. Feel free to propose what to add. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org

Re: LaTeX tutorial (focused on what Org exports) ??

David Masterson writes: > "Fraga, Eric" writes: > >> On Sunday, 1 Jan 2023 at 13:43, Ihor Radchenko wrote: >>> I think that it is not very clear how to use it. >>> Abstract says that it is self-explaining, but it appears that not every >>> pdf viewer supports showing the explanations. >> >>

Re: LaTeX tutorial (focused on what Org exports) ??

"Fraga, Eric" writes: > On Sunday, 1 Jan 2023 at 13:43, Ihor Radchenko wrote: >> I think that it is not very clear how to use it. >> Abstract says that it is self-explaining, but it appears that not every >> pdf viewer supports showing the explanations. > > Yes, that's true. The PDF viewer has

Re: LaTeX tutorial (focused on what Org exports) ??

William Denton writes: > On 30 December 2022, Thomas S. Dye wrote: > >> Org's latex exporter is exceptionally capable. AFAICT, it doesn't >> have practical limits on the LaTeX it produces, at least for my >> academic use case. I'm able to use all of the LaTeX packages I've >> ever wanted to

Re: [BUG] worg-setup.org is outdated

Ihor Radchenko writes: > Tim Cross writes: > >> First step is to get a working local copy so that I have something to >> work with. AFter that and a bit of exploring, I should have a better >> understanding and idea how to go forward. > > Hi Tim, > > May I know if you got a chance to

Re: [SECURITY] Arbitrary code evaluation security in Org (was: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable)

Ihor Radchenko writes: > Ihor Radchenko writes: > >> P.S. Considering intense discussion around the topic, what about >> reverting my commit from the release? We can then re-consider the whole >> design and apply something more elaborate later. > > I now reverted the discussed commit. >

Re: LaTeX tutorial (focused on what Org exports) ??

On 30 December 2022, Thomas S. Dye wrote: Org's latex exporter is exceptionally capable. AFAICT, it doesn't have practical limits on the LaTeX it produces, at least for my academic use case. I'm able to use all of the LaTeX packages I've ever wanted to use. Me too, and the more I use Org

Re: [PATCH][WORG] replaces broken javascript with link

Ihor Radchenko writes: > Bastien, may you take a look? Applied, thanks Gerard. -- Bastien

Re: ob-shell intentions and paperwork (was Bash results broken?)

On Mon, 02 Jan 2023 04:47:10 -0500 Ihor Radchenko wrote --- > They will not be reliable when tests are executed interactively. > If the `should' condition fails, `kill-buffer' will never be executed > leaving dirty state, especially for sessions. >From my perspective, that's the

Re: [MAINTENANCE] Org orphanage?

Ihor Radchenko writes: > I do not really expect much interest as long as the orphaned packages > keep working. And, more importantly, as long as the original package > source (like Github) does not direct users to Org ML. > > Package users are the most likely people who will be interested to

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

Bastien Guerry writes: > Ihor Radchenko writes: > >> We may, however, make `org-confirm-babel-evaluate' function value accept >> an extra third argument - context ('code or 'vars). This will retain the >> required flexibility without introducing an extra variable. > > Yes, this is an

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

Hi Tom, thanks a lot for the detailed explanations: I get your point and I understand the need. I think the revert is a good move, though, as the solution was not really good enough. Thanks! -- Bastien

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

Ihor Radchenko writes: > We may, however, make `org-confirm-babel-evaluate' function value accept > an extra third argument - context ('code or 'vars). This will retain the > required flexibility without introducing an extra variable. Yes, this is an interesting possibility. > P.S. Considering

Re: [MAINTENANCE] Org orphanage?

Bastien writes: > Ihor Radchenko writes: > >> I do not think that it is a good idea: > > Fair enough. There seems to be very little interest in contributing > to https://orgmode.org/worg/org-orphanage.html with abandoned Org > packages so far: I suggest we worry on enhancing this page once

Re: Screenshots in ORG-NEWS

Ihor Radchenko writes: > I mostly had https://orgmode.org/Changes.html in mind here. > Considering the success of https://blog.tecosaur.com/tmio/, I was hoping > to provide some more elaborate NEWS file for users. > > Of course, we need to keep text-only version whenever possible for >

Re: [MAINTENANCE] Org orphanage?

Ihor Radchenko writes: > I do not think that it is a good idea: Fair enough. There seems to be very little interest in contributing to https://orgmode.org/worg/org-orphanage.html with abandoned Org packages so far: I suggest we worry on enhancing this page once there is enough contributions

Re: [WORG] Re: 0e6cdacc publish.sh: never publish the archive/ subdirectory

Ihor Radchenko writes: > -(dolist (org-file (directory-files-recursively default-directory "\\.org$")) > +(dolist (org-file (directory-files-recursively > +default-directory "\\.org$" > +nil (lambda (n) (not (string-match-p "archive" n) > > Won't it also

Re: Broken numerical ordered list when exported to latex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ihor Radchenko writes: > Sharon Kimble writes: > >> My org file is attached, and the original source was a web-page, a straight >> copy and paste, so its inheriting the same list structure as the original. > > This is expected. Lists are

Re: LaTeX tutorial (focused on what Org exports) ??

On Sunday, 1 Jan 2023 at 13:43, Ihor Radchenko wrote: > I think that it is not very clear how to use it. > Abstract says that it is self-explaining, but it appears that not every > pdf viewer supports showing the explanations. Yes, that's true. The PDF viewer has to support popups. I normally

Re: Export Org with Org concept -- Re: Problems with C-c C-e file.org,

I was reading about Orgdown, Karl, please keep the name, and don't mind the group. * Eduardo Ochs [2023-01-02 09:01]: > (3) _is_ my experience with the Org mailing list. > > What I meant by "the developers like your questions" was roughly: > "recognizing that that person deserves help, and

Re: [SECURITY] Arbitrary code evaluation security in Org

Ihor, thanks for this. one additional item (i don't *think* we discussed this before; apologies if i'm forgetting): tangling. if one is prompted to "merely" tangle ... #+begin_src sh :tangle /var/tmp/foo.org.tangled echo 'hi!' #+end_src one could imagine more sinister scenarios for

Re: [BUG] worg-setup.org is outdated

Tim Cross writes: > First step is to get a working local copy so that I have something to > work with. AFter that and a bit of exploring, I should have a better > understanding and idea how to go forward. Hi Tim, May I know if you got a chance to continue working on this? Let us know if you

Re: Babel (scheme): Evaluation errors are not shown

Am Mo., 2. Jan. 2023 um 10:38 Uhr schrieb Ihor Radchenko : > > Marc Nieper-Wißkirchen writes: > > > Fixed. > > Thanks! > Note that your patch does not apply onto main. Rebased against the latest main. Please see the appended patch. > > > - (setq result (if output > > +

Re: ob-shell intentions and paperwork (was Bash results broken?)

Matt writes: > If this set of patches look good, I can push them to main. Just one more comment. You are using constructs like (if (should ...) (kill-buffer ...)) They will not be reliable when tests are executed interactively. If the `should' condition fails, `kill-buffer' will never be

Re: Babel (scheme): Evaluation errors are not shown

Marc Nieper-Wißkirchen writes: > Fixed. Thanks! Note that your patch does not apply onto main. > - (setq result (if output > + (let ((err (geiser-eval--retort-error ret))) > +(setq result (cond > + (err nil) We may still

Re: org-up-element does not the same for all structural blocks

alain.coch...@unistra.fr writes: > With an org file like > >* h >#+begin_export ascii >foo >#+end_export > > putting the cursor on 'foo' and doing > >M-x org-up-element > > brings the cursor on '* h'. Same with the following blocks: > > ‘#+begin_comment’ ... ‘#+end_comment’ >

Re: Shouldn't #+EXP> complete to '#+EXPORT_FILE_NAME:'

alain.coch...@unistra.fr writes: > The manual (in 17.1) says that > >After ‘#+’, [‘M-’] complete[s] the special keywords [...] > > but if I do it after '#+EXP', it does not complete to > >#+EXPORT_FILE_NAME: > > Do I understand the manual incorrectly? Fixed on bugfix. Thanks for

Re: [BUG] Checkbox item is broken in html export with table content [9.6 (9.6-??-bed47b437 @ /Users/hw/.emacs.d/.local/straight/build-28.1/org/)]

Max Nikulin writes: > On 31/12/2022 21:08, Ihor Radchenko wrote: >> nunnery-09-bayside writes: >> >>> a. [ ] foo >>> b. [ ] bar >>> >>> | a | b | c | >> >> [] foo >> [] bar > > I would expect e.g. > > [] bar > >>> frame="hsides"> > >> Probably, the reason is tag in the first

Re: [PATCH] lisp/ob-octave.el, was [PATCH] rfc: using ert-deftest with side-effects

Ihor Radchenko writes: > Ihor Radchenko writes: > >>> There is a race condition between writing the contents of the graphics >>> file to disk and emacs checking the file size. My guess is that this is >>> causing the problem (and that the same failure applies for emacs-2{6,7}, >>> since only

[SECURITY] Arbitrary code evaluation security in Org (was: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable)

Ihor Radchenko writes: > P.S. Considering intense discussion around the topic, what about > reverting my commit from the release? We can then re-consider the whole > design and apply something more elaborate later. I now reverted the discussed commit.