Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Hi, A quick fix (on main) attached. With this ALT_TITLE is ignored in the document with #+OPTIONS: num:nil and if #+OPTIONS: num:t and :PROPERTIES: :UNNUMBERED: t MWE: #+OPTIONS: num:t * Test :PROPERTIES: :UNNUMBERED: t :ALT_TITLE: alt :END: This is a test. * Numbered test :PROPERTIES: :a

Re: Plotting a table of date+time pairs

Ihor Radchenko writes: > Michael Heerdegen writes: > > > But the real problem is that the org table export mechanism thinks that > > the time field doesn't look like a numerical field, so it wraps every > > such field in quotes, and the exported data file will look like > > > > | 2024-09-18

Re: [BUG] org-link-preview-file emits image not supported in daemon [9.8-pre (release_9.7.10-127-g07dd3b @ /home/bidar/.local/etc/emacs/lib/org/lisp/)]

>> Ihor, what would be the best way of handling this? We can add a >> `display-graphic-p' test when running the inline-images part of >> org-startup, but then link previews that are not images won't be applied >> either. > > 1. As a minimum, we can remove that message and do nothing on >non-gr

Re: Link preview generation with new link preview property

>>> ... >>> Considering this, it might be better to just split >>> `org-link-preview-file' into two public functions, where the "inside" >>> function accepts an image instead of a file. >> >> Agree. >> Would you be interested to create a patch? > > Did you think of something like this? It looks li

Re: Completions Registry

>> Not just a problem for dslide but for org in general, any time a >> package adds keys to configure blocks or properties, these do not >> complete except through dabbrev etc. >> ... > > I am sorry, but it is not clear for me from your email what concrete > improvement you want to see. > > There a

Re: Dslide 1.0 Feature Roadmap & RFC

>>> (I'd also add SPC DEL) >> >> What would they do? I know SPC is often some kind of progress, but I don't >> use DEL bindings enough to know them. > > See view-mode-map. In many terminal pagers SPC is to scroll to next > screen and DEL to scroll to previous screen. Similar convention is used > i

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

A MWE: —— \documentclass{article} \title{test} \author{paranda } \date{December 2024} \begin{document} \maketitle \tableofcontents \section{Introduction} \subsection[Sub - shown 1]{Sub intro - shown} This section shows up with a modified heading \subsection*{Sub intro - hidden} This subsectio

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Hi Rudolf, After playing around with the generated LaTeX in overleaf, I have to conclude that the problem is that ALT_TITLE should be not generated for unnumbered chapters, sections, etc. As far as my LaTeX goes, you use the [alt_title] to get something different in the TOC, so it makes no sens

Re: [BUG] Org-protocol bookmarklets in Firefox behaving badly after recent upgrade [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.4/lisp/org/)]

On 12/12/2024 15:12, Rehan Deen wrote: on the webpage https://orgmode.org/, Emacs is able to capture the link and title ("Org mode for GNU Emacs") as desired, but the browser displays a blank page with the following text: org-protocol://store-link?url=https%3A%2F%2Forgmode.org%2F&title=Org

Re: Some hacks on top of org-publish

On Wed, Dec 25, 2024 at 8:47 AM Ihor Radchenko wrote: > > Nikolaos Chatzikonstantinou writes: > > > Finally a highlight of the hacks I had to pull off: apparently > > #+INCLUDE: will strip away inline backend information such as > > @@html:@@. I figured out that if I write something like > > @@ht

Re: [BUG] yank-media doesn't work

It gives this: [TIMESTAMP TARGETS SAVE_TARGETS MULTIPLE STRING UTF8_STRING TEXT chromium/x-source-url text/html text/plain text/plain\;charset=utf-8] Also, it works correctly if i switch from wayland to X11. On Thursday, December 19th, 2024 at 8:24, Visuwesh wrote: > [Monday December 16, 20

Re: Plotting a table of date+time pairs

Michael Heerdegen writes: > But the real problem is that the org table export mechanism thinks that > the time field doesn't look like a numerical field, so it wraps every > such field in quotes, and the exported data file will look like > > | 2024-09-18 "11:40 CEST" > | 2024-09-19 "11:

Re: LaTeX export is broken with 'num:nil` and 'ALT_TITLE`

Rudolf Adamkovič writes: > REPRODUCTION: > > 1. Create a file containing: > >#+OPTIONS: num:nil > >* Test >:PROPERTIES: >:ALT_TITLE: alt >:END: > >This is a test. > > 2. Open the file. > 3. Export to a PDF file with LaTeX. Confirmed. This is because [] is inserted

Re: Unexpected error using org-gnus-follow-link

[வியாழன் டிசம்பர் 26, 2024] Ihor Radchenko wrote: > Visuwesh writes: > >>> Also, (cdr (assq 'gnus org-link-frame-setup)) = nil is not the only >>> possible incorrect customization. I'd rather check if the cdr is a >>> function and throw a descriptive error otherwise asking to fix >>> `org-link-fr

Re: The less ambiguous math delimiters in tables

Rudolf Adamkovič writes: >> Maybe, but it is also much more complex in terms of parser. >> Backtracking will introduce non-linear complexity to the parser, >> degrading the performance significantly. > > Is that so? I thought it is all about simple precedence rules. In this > case, once the par

Re: The less ambiguous math delimiters in tables

Ihor Radchenko writes: > Maybe, but it is also much more complex in terms of parser. > Backtracking will introduce non-linear complexity to the parser, > degrading the performance significantly. Is that so? I thought it is all about simple precedence rules. In this case, once the parser finds

Re: Unexpected error using org-gnus-follow-link

Visuwesh writes: >> Also, (cdr (assq 'gnus org-link-frame-setup)) = nil is not the only >> possible incorrect customization. I'd rather check if the cdr is a >> function and throw a descriptive error otherwise asking to fix >> `org-link-frame-setup'. > > How about the attached? You still do not

[PATCH] Turn org-mouse features into minor-modes

[ Resending it as it seems like it never reached the mailing list. ] To make loading org-mouse less annoying for all, I was thinking of introducing minor-modes like in the attached patch. If this approach is acceptable, I will get to calling out the change in NEWS and updating the manual if requ

Re: [PATCH] ob-calc: Format vector and matrix results as Org table

[செவ்வாய் டிசம்பர் 24, 2024] Ihor Radchenko wrote: > Visuwesh writes: > >> Attached patch formats vector and matrix results from a Calc source >> block as Org table. To test, try >> ... >> now. The patch passes the old tests, and I added three new tests to >> check the correctness of this conve

Re: Unexpected error using org-gnus-follow-link

[திங்கள் டிசம்பர் 23, 2024] Ihor Radchenko wrote: > Visuwesh writes: > >>> Do you want to make a patch to that effect? >> >> How about the attached? It falls back to the default value if the key >> is not found in the alist. > > I'd rather just throw an error. If the value is not right in the >

Re: Unexpected error using org-gnus-follow-link

[திங்கள் டிசம்பர் 23, 2024] Ihor Radchenko wrote: > Visuwesh writes: > >>> Do you want to make a patch to that effect? >> >> How about the attached? It falls back to the default value if the key >> is not found in the alist. > > I'd rather just throw an error. If the value is not right in the >

Re: Generating the filename from name and file-ext for blocks with side-effects

Rudolf Adamkovič writes: >> The aim is to not need to define a filename for each image, to minimise >> the boilerplate. > > +1 This should be built into Org and enabled by default. > > I currently generate image names with a custom snippet, but it gets > trying and should not be necessary in the

Re: Dslide 1.0 Feature Roadmap & RFC

Psionic K writes: >> (I'd also add SPC DEL) > > What would they do? I know SPC is often some kind of progress, but I don't > use DEL bindings enough to know them. See view-mode-map. In many terminal pagers SPC is to scroll to next screen and DEL to scroll to previous screen. Similar convention

Re: The less ambiguous math delimiters in tables

Rudolf Adamkovič writes: >> 1. \(x\) >> 2. |x| >> >> Org parser chooses one. It has to choose some. >> Org parser also chooses a simpler interpretation that does not require >> backtracking. > > But (2) is a *much, much, much* better choice (for the user). Maybe, but it is also much more com

Re: Generating the filename from name and file-ext for blocks with side-effects

Aitenate writes: >>> ~:var outFile=(alist-get :file (nth 2 (org-babel-get-src-block-info >>> 't)))~ >> >> Seems right, but I do not understand why you would need such thing. >> > The aim is to not need to define a filename for each image, to minimise > the boilerplate. Org has a mechanism for

Re: Tiny patch: add onlyenv to beamer environments

Ihor Radchenko writes: > Please, check the attached updated patch. Applied, onto main, after fixing a typo. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8e141ec24e -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Suppor

Re: Generating the filename from name and file-ext for blocks with side-effects

Ihor Radchenko writes: > Seems right, but I do not understand why you would need such thing. Aitenate writes: > The aim is to not need to define a filename for each image, to minimise > the boilerplate. +1 This should be built into Org and enabled by default. I currently generate image na