Hello all,
I'm looking for some advice. I do most (if not all) of my coding within
org, using src blocks which are tangled to create the actual code to
run. Although I usually edit the code from within the org file, using
org-edit-special, I sometimes, when debugging, edit the tangled code
file
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.
On 16/02/2024 21:57, Visuwesh wrote:
(dolist (desc org-odt-file-extensions)
;; Let Emacs open all OpenDocument files in archive mode.
(add-to-list 'auto-mode-alist
(cons (concat "\\." (car desc) "\\'") 'archive-mode)))
Package: Org mode version 9.7-pre (relea
Hi Matt, Jack, Ihor,
Sorry for the late reply. Cleaning the code took me longer than
expected.
Jack Kamm writes:
> Bruno Barbier writes:
>
>> FWIW, I've been trying to use asynchronous blocks for everything, not
>> only the source blocks that are based on the comint mode.
>> ...
>
> Sounds
using org-ai seemed to cause this bug. I wouldn't have recieved this
error otherwise.
Never filed a bug report before. Please ignore if this seems incomplete.
⛔ Warning (org-element): org-element--cache: Org parser error in
2024-02-14.org::898. Resetting.
The error was: (error "Invalid se
I've just been struggling with my custom setting for
`org-latex-to-html-convert-command` outputting many math snippets
wrong. The fault was mine: I didn't correctly shell-quote the input.
I propose to add a warning in the docstring, because many people will
trip the same problem.
The thing is that
Is it related with AUTHOR property?
I am starting to add these properties to every book, and chapter of the book,
that I study. I hope this doesn't lead to a suboptimal workflow.
Doesn't this work?
:PROPERTIES:
:AUTHOR: García-Ael, Cristina and Pérez-Garín, Daniel and Recio Saboya,
Patric
