Re: Org mode links: Open a PDF file at a given page and highlight a given string

Rodrigo Morales writes: > Debugger entered--Lisp error: (wrong-type-argument stringp nil) I can no longer reproduce on the latest main. Closing the bug report. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at <

Re: Org and Hyperbole

Another good thought. Anyone can add an embeddable export of Koutlines; I don't think we'll find time to do that in the mainline development branch though. On Tue, Sep 27, 2022 at 10:45 AM Jean Louis wrote: > * Robert Weiner [2022-06-25 23:52]: > > 2. We have not yet integrated org-export with

Re: Org and Hyperbole

Thanks, Jean. We have started work on a note-taking subsystem for Hyperbole that will store UUIDs per note and will likely support backlinks too. We are seeing if we can make it support Koutlines, Emacs Outlines, Org mode files and Markdown files, searching across all formats at the same time. T

Habit tracking (add "DONE" state with configurable date/time)

Hello, I'm lately finding myself in this situation: I have a number of habits that I track, and I want to mark one of them to "DONE", but registering not the date when I change its state, but some other date/time (this usually happens, for example, with my "sports" habit, which I do late at night,

[PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

Hi, This patch fixes the bug originally reported in https://list.orgmode.org/59e02fb6.1462370a.fffe8.5...@mx.google.com/ with the following reproducing recipe. The bug still exists in latest org-mode. > To reproduce, take the following org file: > > ---8<--- > * Foo > :PROPERTIES: > :CATEGOR

Re: [PATCH] Unit-test for Please add support for dlangs packagemanager to ob-C.el

Christian Köstlin writes: >> If the programming language is using its own package manager, is it any >> different? Or do you refer to something else? >> > Most of the packages that a programming language like rust/crates, > ruby/rubygems > or dlang/dub-packages provide will probably never mak

Re: [PATCH 2-v4] New: auto display inline images under subtree when `org-cycle'.

"Christopher M. Miles" writes: > I think the patch is finished. Please review, Ihor. Thanks for helping. Thanks for the update! I have cleaned the manual and ORG-NEWS wordings. Upon reading the exported version of the manual, I realized that the part in 2.2.1 Global and local cycling section so

Re: Code block syntax highlighting in async export

Hi Ihor, >> Try it 😉 > > You are right. With default preset, engrave-faces does not need to query > Emacs about face colors and attributes and should not depend on the > `display-graphic-p’. Yep, it works because it’s basically implementing its own face-resolving layer. This was originally done t

Re: Code block syntax highlighting in async export

Timothy writes: > Hi Ihor, > >> I would not be so sure. If the issue is major-mode not doing >> fontification in batch mode, engrave-faces cannot do much. > > Try it 😉 You are right. With default preset, engrave-faces does not need to query Emacs about face colors and attributes and should not d

Re: Code block syntax highlighting in async export

David Lukeš writes: >> Could you please provide an example? > >> Certainly more details is necessary, even export format (backend) is not >> specified. > > Sorry for that! I somehow thought that the issue would sound familiar > to more seasoned Org users, and someone would come back with either >

Re: Concatenating results

On Mon, Oct 3, 2022 at 11:28 AM Ihor Radchenko wrote: > > #+begin_src emacs-lisp :noweb yes > > Thank you Ihor. Felix -- Linux. The choice of a GNU generation.

Re: Post-process table without changing result for empty table(/list)

Jonas Bernoulli writes: > It used to behave like that before 51a628bc5efc from 2009, which started > turning all symbols, including nil, into strings, but without giving any > reason why that should be done. > > It has worked like this for a long time now, so reverting that is > probably not feas

Re: Numbered footnotes in the manual interfere with diff

Bastien writes: > Hi Ihor, > > Ihor Radchenko writes: > >> Should we just inline the one-sentence footnotes? > > Yes, this would be a progress already. Done. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0641ece57b9d980b63e3a3bb6dc4d467eff3051b I also documented this in doc/D

Re: Code block syntax highlighting in async export

> I have realized that > https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-elisp.html > has colorized source blocks. The file is created using > https://git.sr.ht/~bzg/worg/blob/master/publish.sh and the script is > executed inside a container with no available DISPLAY. Well spotted! I t

Post-process table without changing result for empty table(/list)

Hello, If a code-block that is supposed to produce a table returns an empty list, then nothing at all is inserted, as demonstrated by the second example below: #+begin_src emacs-lisp :results table ;; Some sql query that returns one or more rows: '(("foo" "bar")) #+end_src #+RESULTS: | foo |

Re: Code block syntax highlighting in async export

On 03/10/2022 19:08, David Lukeš wrote: Could you please provide an example? A problem that has some similar symptoms: M. Pger. Re: no syntax highlighting for code blocks with org-publish. Mon, 18 Jul 2022 22:55:15 +. https://list.orgmode.org/inTtQOKWAhnFydjBE9fQOOdo_oV6kIPG5_E0d8DsfFiYMIJ

Re: Code block syntax highlighting in async export

Hi Ihor, > I would not be so sure. If the issue is major-mode not doing > fontification in batch mode, engrave-faces cannot do much. Try it 😉 All the best, Timothy -- Timothy (‘tecosaur’/‘TEC’), Org mode contributor. Learn more about Org mode at . Support Org development

Re: Code block syntax highlighting in async export

David Lukeš writes: >> I'll investigate if I can leverage any of the workarounds mentioned. > > So, for batch processing, avoiding --batch or --script and just using > --load with a script that either ends by killing Emacs, or killing it > via an additional --eval, works, i.e. syntax highlighting

Re: Code block syntax highlighting in async export

> I'll investigate if I can leverage any of the workarounds mentioned. So, for batch processing, avoiding --batch or --script and just using --load with a script that either ends by killing Emacs, or killing it via an additional --eval, works, i.e. syntax highlighting uses colors. This was suggest

Re: Code block syntax highlighting in async export

Hi David, > Sorry for that! I somehow thought that the issue would sound familiar > to more seasoned Org users, and someone would come back with either > “yeah, you need to do X” or “yeah, that’s a known limitation”. Each backend is its own beast, somewhat 🙂. > The export backend is HTML. In cas

Re: [PATCH] ox-odt: Prevent auto-formatting in export buffers

Noted, will do! David

Re: Code block syntax highlighting in async export

> Could you please provide an example? > Certainly more details is necessary, even export format (backend) is not > specified. Sorry for that! I somehow thought that the issue would sound familiar to more seasoned Org users, and someone would come back with either "yeah, you need to do X" or "yea

Re: Concatenating results

Felix Dorner writes: > I get an error with this: > executing Emacs-Lisp code block... > progn: Symbol’s value as variable is void: >> That's because noweb references are disabled by default (see https://orgmode.org/manual/Noweb-Reference-Syntax.html#Noweb-Reference-Syntax) With default Org sett

Re: Concatenating results

On Mon, Oct 3, 2022 at 10:44 AM Ihor Radchenko wrote: > #+name: block1 > #+begin_src emacs-lisp :results table > '((1 2) (3 4)) > #+end_src > > #+name: block2 > #+begin_src emacs-lisp :results table > '((5 6) (7 8)) > #+end_src > > > #+begin_src emacs-lisp > (append > '<> > '<>) > #+end_src > I

Re: `org-fill-paragraph' (`M-q') in Org Mode source blocks

Sébastien Miquel writes: >> Try >> 1. emacs -Q >> 2. insert >> ;; A comment >> (+ 2 2) >> 3. M-h M-q >> >> Is it emacs-lisp-mode bug? Or is it illegal to fill-region in source >> code buffers? > > I think the original report is about M-q, not M-h M-q. M-q behaves as > expected in emacs-lisp-mod

Re: Numbered footnotes in the manual interfere with diff

Hi Ihor, Ihor Radchenko writes: > Should we just inline the one-sentence footnotes? Yes, this would be a progress already. > Also, there is one footnote that is indexed (does it even work?): AFACT it does not work and I think it should not work, we can remove these index entries. -- Bastie

Re: Concatenating results

Felix Dorner writes: > I have a list of N source blocks, of which each produces a table, and all > these tables have the same column count. What is the easiest way to now > make a single table which is the result of calling all these blocks and > concatenating the result? > > Essentially, would b

Concatenating results

I have a list of N source blocks, of which each produces a table, and all these tables have the same column count. What is the easiest way to now make a single table which is the result of calling all these blocks and concatenating the result? Essentially, would be also the same as N CALL together

Re: Numbered footnotes in the manual interfere with diff

Bastien writes: > Ihor Radchenko writes: > >> Do you have any suggestion on how to deal with changing footnotes in the >> manual? When I delete this footnote, all the footnotes must be >> re-numbered creating a lot of garbage in the diff. Is it ok? Or should >> we prefer inline footnote definiti

Re: `org-fill-paragraph' (`M-q') in Org Mode source blocks

Hi, Ihor Radchenko writes: I am still getting the described behaviour. However, it does not happen in Org mode itself. `fill-paragraph' in emacs-lisp-mode does exactly the observed behaviour. Try 1. emacs -Q 2. insert ;; A comment (+ 2 2) 3. M-h M-q Is it emacs-lisp-mode bug? Or is it illegal

Re: Explicit page breaks

Juan Manuel Macías writes: > ... > With all this, I mean: to what extent should Org care about all these > details, more related to fine-tuning the output format? Thanks for the detailed explanation! It is now clear that pagebreak by itself may very much depend on the specifics of the export ba