org-agenda-skip-function now evaluated on line after headline?

Hello, It looks like the org-agenda-skip-function is now evaluated with point on the second line of the subtree, rather than on the headline? It always used to be evaluated with point on the headline. Seems like this might count as a regression? Thanks. -- Sean Whitton

[PATCH] Allow external libraries (org-roam) to supply org-id locations

Hi all, Since updating the org-id code [1] to use the standard org-link registered functions instead of hard-coding org-id opening, I have a problem using org-roam. org-roam overwrites the :follow function for "id" links from the build-in `org-id-open' to its own `org-roam-id-open'

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

Damien Cassou writes: > Ihor Radchenko writes: >> Thanks for the patch, but it is not obvious that skipping src blocks >> that cannot be executed is always a good idea. Consider, for example, >> that some blocks are used as input for other blocks. Then, failing to >> execute them means that

Re: org-id-locations as a large-scale database store?

Laurence von Bottorff writes: > Any docs on what org-id-locations is about, who/what uses it? It is an internal variable. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or

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

Hi Ihor, Ihor Radchenko writes: > Thanks for the patch, but it is not obvious that skipping src blocks > that cannot be executed is always a good idea. Consider, for example, > that some blocks are used as input for other blocks. Then, failing to > execute them means that other blocks may have

Re: org-id-locations as a large-scale database store?

Any docs on what org-id-locations is about, who/what uses it? On Tue, Mar 12, 2024 at 1:44 PM Ihor Radchenko wrote: > yeti writes: > > >> Does org-brain have anything to do with org-id-locations? > > > > I think so... > > > > E.g. org-brain.el 788-794: > > > >

Re: [BUG] Re: The orgframe construct in the Beamer exporter as a default needs a rethink

On Tue, Mar 12 2024, Ihor Radchenko wrote: > Pedro Andres Aranda Gutierrez writes: > >> Jup, of course. If you look in org-lint.el, one of the cases that would >> trigger a message is when the frame environment uses "frame" directly and >> there is a \begin{frame} in the org. >> Line 1522

Re: Just thinking...

Pedro Andres Aranda Gutierrez writes: > You are right. It is easy to do from emacs-lisp scripts, looking for > LATEX_CLASS in a document and then deciding to use the org-latex-... or the > org-beamer-... functions, but it looks much more difficult in org.el itself > :( > It's just that it would

Re: [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

[ Adding Org mailing list back to CC. Please use "reply all" to keep the conversation public ] Jerome writes: > This specific case (deleting a line and getting a bug) has only happened > once. Might also be worth noting that I only ever get bugs in this one org > file that I open, never in

Re: org-id-locations as a large-scale database store?

yeti writes: >> Does org-brain have anything to do with org-id-locations? > > I think so... > > E.g. org-brain.el 788-794: > > ---8<--- > (defun org-brain-entry-from-id (id) > "Get entry from ID." > (unless org-id-locations

Re: org-id-locations as a large-scale database store?

Ihor Radchenko writes: > yeti writes: > >> Laurence von Bottorff writes: >> >>> So again, is this org-brain approach DOA for anything big? >> >> I like it, but even my small pool of notes is slow with org-brain. >> >> ---8<--- >>

Re: org-id-locations as a large-scale database store?

yeti writes: > Laurence von Bottorff writes: > >> So again, is this org-brain approach DOA for anything big? > > I like it, but even my small pool of notes is slow with org-brain. > > ---8<--- > ~ $ hash-table-size

Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > It is not clear for me how to achieve the following. Add a link > > [[https://youtube.com/...][Org mode in action demo (video)]] > > for all backends (EPUB, LaTeX, ODT, text, etc.) besides HTML because > there is an #+export_html block with player embedded using an iframe.

Re: org-id-locations as a large-scale database store?

You might be interested in https://www.orgroam.com/ which is a broadly similar idea to org-brain but uses a SQLite database to track id locations and links.

Re: org-id-locations as a large-scale database store?

Laurence von Bottorff writes: > So again, is this org-brain approach DOA for anything big? I like it, but even my small pool of notes is slow with org-brain. ---8<--- ~ $ hash-table-size $org-id-locations 1322

Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

On 12/03/2024 20:45, Juan Manuel Macías wrote: backend-name = full export backend-name* = only contents And the "rest" option is introduced, with the same syntax as before. Examples: It is not clear for me how to achieve the following. Add a link [[https://youtube.com/...][Org mode in

Re: ob-haskell and changing executables?

Bruno Barbier writes: >> Only for sessions. For src blocks with :session none, we directly call >> `org-babel-haskell-compiler'. > > Good point. I didn't check that execution path (probably because I > assumed the OP was speaking only about GHCi). > > But, from what I see (function

Re: Table column formula with remote reference

Wu Ming writes: > Problem solved with > > $1 = remote(A,@@#$1) > > as described on the manual page > https://orgmode.org/manual/References.html#Field-coordinates-in-formulas-1 > > > Where is the coordinate @@#

Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

Ilya Konovalov writes: > On current master using ":sep" header argument does not work as > expected and records are always split on whitespaces. For example: > > #+begin_src sh :sep "\t" > echo hello world > echo test > #+end_src > > #+RESULTS: > | hello | world | > | test | | It

Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

Matt writes: > ...  According to my notes, :sep and :separator don't work for > anything beyond basic table layout. I'm not familiar with org-table > and there isn't much documentation on those keywords in the manual. > The :sep keyword shows up for Texinfo and LaTeX. It looks like :sep is >

Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

In the last commit I have introduced some changes. Now this new feature is no longer hardcoded in each backend but is controlled by an external function in ox.el. I think this can simplify the implementation for other backends. As Stefan Nobis proposed, the "+" sign is now not necessary:

Re: ob-haskell and changing executables?

Hi Ihor, Ihor Radchenko writes: > Bruno Barbier writes: > >>> If you've gotten this far you probably know more >>> about the Haskell Babel situation than you ever wanted to, but maybe you >>> can sniff out where this hardwire is happening. >> >> It's not hard coded (there is quite a lot of

Re: [BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Jerome Siljan writes: > I deleted a line in my file and I got this error and the prompt to > report it > > Emacs : GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version > 3.24.39, cairo version 1.18.0) > of 2024-01-10 > Package: Org mode version 9.6.6 (release_9.6.6 @ >

Re: [BUG] a bug [9.7-pre (release_9.6.14-1017-g518533 @ /home/saint/.emacs.d/straight/build/org/)]

MasterWQ writes: > 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 > ... Thanks for reporting, but may you please provide some details on

Re: [PATCH] lisp/ob-shell.el: Also override explicit-shell-file-name

Matt writes: > Thank you for your report and the patch. Matthew, you are free to apply patches relevant to ob-shell to savannah repository, if you think that they are fine. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org

Re: [PATCH] lisp/oc-basic.el: add missing function declarations

Gerard Vermeulen writes: > the attached patch adds two missing function declarations to oc-basic.el Applied, onto main. Thanks! https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e2caccfdf -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG] [PATCH] Use new face org-caption for #+caption lines [9.6.21 ( @ /home/cassou/.emacs.d/lib/org/lisp/)]

Damien Cassou writes: > Currently, the caption of a picture (here the text "Description of the > piture") has the face `org-block': > > #+CAPTION: Description of the picture. > #+RESULTS: > [[file:./picture.png]] > > I don't see any reason for the caption to use the same face as code

Re: [BUG] obscure error for invalid :exports

Max Nikulin writes: >> See the attached tentative patch. > > Thanks, Ihor. With this patch applied, behavior is improved. Applied, onto main. Fixed. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f08174a45 > Notice however that the *Warnings* buffer may be hidden by export

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

Max Nikulin writes: >> Even stripping quotes is unreliable when we use the example from >> docstring: 'literal:%i'. > > My idea is to recognize this case. If stripping is not performed then it > is necessary to detect if user command is safe. Otherwise apostrophe in > a formula (even after

Re: [BUG] org-fold :extend face backgrounds break with trailing newlines [9.7-pre (release_9.6.20-1267-gb0c3c9 @ /home/st/.config/emacs/.local/straight/build-30.0.50/org/)]

StrawberryTea writes: > I've noticed that when using the :extend face property with org-fold, > the background color of the headline face will sometimes be left behind > after unfolding a heading. I have finally determined that this is > happening when the heading has a trailing newline and the

Re: Things got very slow: profiler output

William Denton writes: >> 40255 60% - org-do-latex-and-related >> 40243 60% re-search-forward > ... > I spent a while with git bisect this afternoon and the problem (for me) > started here: > > commit 5d186b499dde97f59a91dc11f4c4a15113d29f4d > Author: Ihor Radchenko > Date: Sun Feb 25

Re: [BUG] Flyspell triggers "Warning (org-element-cache): org-element--cache" [9.6.18 ( @ /home/mwillcock/.emacs.d/elpa/org-9.6.18/)]

Morgan Willcock writes: >> org-element.el has been changed significantly on main compared to bugfix >> branch. > > I remained on the release version but the problem has not reappeared. > > Given that the development version has significant changes, and I am not > able to get a handle on what

Re: ob-haskell and changing executables?

Bruno Barbier writes: >> If you've gotten this far you probably know more >> about the Haskell Babel situation than you ever wanted to, but maybe you >> can sniff out where this hardwire is happening. > > It's not hard coded (there is quite a lot of code just to guess the > right interpreter).

Re: [BUG] Re: The orgframe construct in the Beamer exporter as a default needs a rethink

Pedro Andres Aranda Gutierrez writes: > Jup, of course. If you look in org-lint.el, one of the cases that would > trigger a message is when the frame environment uses "frame" directly and > there is a \begin{frame} in the org. > Line 1522 onwards in org-lint.el (1) Sure, but we should not

Re: [PATCH] Unindentation fixup for code blocks

Ihor Radchenko writes: > I am attaching an amended patch with modified commit message and > docstring describing the invisible text is accounted as visible. > I also added TINYCHANGE cookie as you do not appear to have FSF > copyright assignment. Applied, onto main.

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

Damien Cassou writes: > The command `org-babel-execute-buffer' tries to execute all source code > blocks of the current buffer. When it encounters a block that is not > executable the command crashes. The attached patch makes the command ignore > non-executable blocks and move on. > ... > -

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/)]

Björn Bidar writes: >> Fixed, on main. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fef873b1c > > I noticed that `org-insert-structure-template' and possibly others are > also affected > > Is a new bug needed or this one enough? This one is enough. Fixed, on main.

Re: ob-haskell and changing executables?

Laurence von Bottorff writes: > 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

Re: Testing issues for Ada/SPARK support in Babel

Francesc Rocher writes: > I'm starting from scratch the set of tests for Ada/SPARK support in Babel. > I've prepared a file with the first example: > > ---8<--- testing/examples/ob-ada-spark-test-org ---8<--- > ... > Then in the file testing/test-ob-ada-spark.el I've defined the following >

Re: [TASK] Please help updating blog generator list on https://orgmode.org/tools.html

Bruno Cardoso writes: >> If you know any actively developed working blog generators for Org mode, >> please share them. > I have in my notes this list of Static Site Generators projects, along with > their own descriptions: > ... Thanks! I have updated the tools page. Handled. -- Ihor

Re: [TASK] Please help updating parser list on https://orgmode.org/tools.html

Ihor Radchenko writes: > Org mode website has a page listing various third-party tools that work > with Org mode. > > However, that page is now severely outdated. There is a number of dead > links and projects last updated 10+ years ago. Closed. -- Ihor Radchenko // yantar92, Org mode

Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

I assumed that https://org-babel.readthedocs.io/ is at least somewhat related to org documentation. Looks like I was wrong. The :separator parameter seems to be related to how block's :var arguments are formatted when passing to the shell script. In most cases separator is not passed to

Re: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]

Ihor Radchenko writes: >> I still believe that fallback export should preserve link type. Code >> links should define their export functions. > > Let's get started on tackling this problem from not stripping the link > type. > > I am attaching tentative patch to that effect, as a first step.

Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

On Tue, 12 Mar 2024 10:27:46 +0100 Ilya Konovalov wrote --- > > After some usage I found that this exact patch breaks > `org-babel-import-elisp-from-file's own separator detection. It looks > like it's better to leave it as `nil' unless specified. Thanks for taking the time to look

Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

After some usage I found that this exact patch breaks `org-babel-import-elisp-from-file's own separator detection. It looks like it's better to leave it as `nil' unless specified. Ilya Konovalov writes: > On current master using ":sep" header argument does not work as > expected and records

Re: `:export' attribute?: Re: Experimental public branch for inline special blocks

Juan Manuel Macías writes: >>> :export "latex+ html+ rest*" >> "rest" might be a valid backend name. > I will try to implement the "rest" option. What about "others" or even ":others" as a placeholder for any not explicitly mentioned export backend? Another quick thought crossing my mind:

Table column formula with remote reference

Hello, #+NAME: A Table with header row here #+NAME: B Table with header row here #+TBLFML: $1 = remote(A,$1) Does nothing. $1 = remote(A,@0) referring current row w implicit column does not work. Debug shows on row 2 of current table it returns the value of row 1, the header, on table A.

The org--math-p advice around texmathp

Hi, I recently stumbled upon the fact that Org has some around advice for texmathp: org--math-p. For reasons that aren't entirely clear to me, this has some special handling for cdlatex-math-symbol, and recognises display and inline maths environments on its own, only calling out to texmathp if

[BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]

On current master using ":sep" header argument does not work as expected and records are always split on whitespaces. For example: #+begin_src sh :sep "\t" echo hello world echo test #+end_src #+RESULTS: | hello | world | | test | | It looks like the issue is in the

[BUG] Bug Report [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

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] a bug [9.7-pre (release_9.6.14-1017-g518533 @ /home/saint/.emacs.d/straight/build/org/)]

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: Table column formula with remote reference

Problem solved with $1 = remote(A,@@#$1) as described on the manual page https://orgmode.org/manual/References.html#Field-coordinates-in-formulas-1 Where is the coordinate @@# documented? > On 11 Mar 2024, at