[BUG] [PATCH] org-babel-execute-buffer: Prevent executing non-code blocks [9.6.20 ( @ /home/cassou/.emacs.d/lib/org/lisp/)]

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.

Re: [BUG] ob-shell async incorrect table and value results

On Fri, 08 Mar 2024 10:25:09 +0100 Ihor Radchenko wrote --- > Confirmed. > This is because `ob-shell-async-chunk-callback' never returns a list. > > In `org-babel-sh-evaluate', there is a part that is responsible for > detecting the result type: > > (when (and results value-is-

ob-haskell and changing executables?

I'm on Debian 12 and I just started using Haskell's ghcup tools, leaving the stack tools behind, as advised these days. ghcup puts executables for Haskell such as ghc, ghci (REPL), cabal, etc. in its ~/.ghcup/bin directory. Next, to stop using the stack tools that have executables in /usr/bin/ you

Re: [BUG] Org-Agenda leaves frame around [9.7-pre (release_9.6.8-785-g72bbf8.dirty @ /home/bidar/.local/private/etc/emacs/lib/org/lisp/)]

Ihor Radchenko writes: > Ihor Radchenko writes: > >>> 0. emacs -Q >>> 1. Paste this into the scratch buffer: >>> (setq org-agenda-window-setup 'other-frame) >>> (setq pop-up-frames t) >>> 2. Eval >>> 3. Org-agenda >> >> This is now expected. >> We changed Org agenda to respect user settings, inc

Re: false positives: Re: Experimental public branch for inline special blocks

Juan Manuel Macías escribió: > Ok, I think you and Maxim are right. This is a clear bug. I hope it > was fixed in the last commit. Now: (org-export-string-as "Alpha@Beta{" 'latex t)) ==> Alpha@Beta\{ (org-export-string-as "Alpha@Beta{gamma}" 'latex t)) ==> Alpha\Beta{gamma} -- Juan Manu

Re: false positives: Re: Experimental public branch for inline special blocks

Ihor Radchenko writes: > Juan Manuel Macías writes: > >>> Debugger entered--Lisp error: (wrong-type-argument >>> number-or-marker-p nil) >> >> Maybe in that case you could add a zero width space character. >> >> In any case, if someone has reasons to write "Alpha@Beta{" they may also >> have

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hi, I’m very interested on how your document header looks like. Can you please send mee a file with your header and a couple of dummy slides? I’m not able to reproduce the problem… Thx, /PA > El 7 mar 2024, a las 10:42, Alan Schmitt > escribió: > > Hi Pedro, > > On 2024-03-07 10:03, Pedro

Re: naming: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > Ihor, I see you intention, however I reserve my vote for some new unique > word, preferably a single one. That's fine. I do not insist on my preferences about naming. Rather see it as a minor issue that can be resolved at any moment after we implement the functionality. Ma

Re: naming: Re: Experimental public branch for inline special blocks

On 08/03/2024 12:26, Samuel Wales wrote: cannot follow discussion but is the role and scope of the proposed semantics settled and agreed upon by those who do? I think, there are enough issues with the proposed feature to discuss. Notice "naming" added to the message subject with hope to facili

Re: false positives: Re: Experimental public branch for inline special blocks

Juan Manuel Macías writes: >> Debugger entered--Lisp error: (wrong-type-argument >> number-or-marker-p nil) > > Maybe in that case you could add a zero width space character. > > In any case, if someone has reasons to write "Alpha@Beta{" they may also > have reasons to write "Alpha_Beta": 1.

Re: false positives: Re: Experimental public branch for inline special blocks

On 08/03/2024 22:44, Juan Manuel Macías wrote: Max Nikulin writes: (org-export-string-as "Alpha@Beta{" 'html '(:export-options (body-only))) "\nAlpha{\n" (org-export-string-as "Alpha@Beta[" 'html '(:export-options (body-only)

Re: false positives: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > (org-export-string-as "Alpha@Beta{" > 'html > '(:export-options (body-only))) > "\nAlpha{\n" > > (org-export-string-as "Alpha@Beta[" > 'html > '(:export-options (body-only))) > Debugger entered--Lisp error: (wron

Re: [DISCUSSION] Add "Recent News" to orgmode.org

Ihor Radchenko writes: > Something like the attached maybe. Thanks! Applied: https://git.sr.ht/~bzg/woof/commit/177ea5b1 -- Bastien Guerry

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

Hi Ihor, Ihor Radchenko writes: > Thanks! > I have some minor concerns about implementation, but you clearly > demonstrated the things can be working in general. Thanks! > While reading the library header and `org-pending' docstring (btw, it > should probably be a separate library, not a par

Re: false positives: Re: Experimental public branch for inline special blocks

On 08/03/2024 01:21, Juan Manuel Macías wrote: Ihor Radchenko escribió: I am wondering if @@[...]{...} would be better than @_... It should be slightly easier to type. Anyway, in the last commit I replaced _ with @. Let's see how it goes... Now the anonymous variant is @@[...]{...}. Unfortu

Re: Emacs slow-down

On Friday, 8 Mar 2024 at 07:54, Pedro Andres Aranda Gutierrez wrote: > In this case, one of the root causes for my insufferable > slowdown was not org-mode but jinx (the spell checker). I turned jinx off as well. The other culprit, for me, was wc-mode. I now count words explicitly when needed

Re: Warn about shell-expansion in the docstring of org-latex-to-html-convert-command

Max Nikulin writes: >>> It should be more reliable to pass fragment to command stdin. It can be >>> done if %i is missed in `org-latex-to-html-convert-command'. >> >> I agree that it will be more reliable to shell-escape argument. >> However, I am concerned that escaping may break certain uses l

Re: Provide sane default for the @direntry

Stefan Monnier writes: > I fixed those three issues (I still get test failures, but I get the > same with or without my patch 🙂). Applied, onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4fd869194 https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=b0c3c905

Re: [DISCUSSION] Add "Recent News" to orgmode.org

Ihor Radchenko writes: > +;; Display the latest first. > +resources (reverse (sort resources)) * (sort-by :date resources) -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at

Re: [DISCUSSION] Add "Recent News" to orgmode.org

Bastien Guerry writes: >> Also, it looks like https://tracker.orgmode.org/index.org does not sort >> links by date. It would be nice if top 5 links were also the most recent. > > Yes, indeed. I'll see when I can hack on this. Help from Clojure > hackers is welcome here: https://git.sr.ht/~bzg/woo

Re: [BUG] obscure error for invalid :exports

Max Nikulin writes: > Trying to export (to HTML buffer) > > src_elisp[:exports source]{a} > > I have got an obscure error > > org-export-as: Wrong type argument: char-or-string-p, nil > > I believe, some meaningful error should be signaled. > > I was quite surprised since the following

Re: [BUG] ob-shell async incorrect table and value results

Matt writes: > #+name: sync table > #+begin_src sh :session *test* :results table > echo "hello world" > #+end_src > > #+RESULTS: > | hello world | > > #+name: async table > #+begin_src sh :session *test* :results table :async t > echo "hello world" > #+end_src > > #+RESULTS: > : hello world Con

Re: Provide sane default for the @direntry

> Thanks! > Unfortunately, the patch causes some tests (make test) to fail. > Looks like export to temporary buffer is broken (temporary buffer does > not have a filename): > > 2 unexpected results: >FAILED test-ox-texinfo/end-to-end-inline stringp >FAILED test-ox-texinfo/end-to-end-sani