Juan Manuel Macías writes:
> How about this (pre-)patch? With the `:literal' attr., the content of the
> block is exported "as is", with all manual formatting preserved.
Looks reasonable in general.
Of course, we will also need to document the new attribute.
> I have made some modifications in
On 11/08/2023 23:27, Ihor Radchenko wrote:
Max Nikulin writes:
Loading /home/ubuntu/src/org-mode/lisp/org-compat.el (source)...
Eager macro-expansion failure: (wrong-number-of-arguments (2 . 2) 6)
That failure does not really point to where it happened... I am
wondering how you managed to fin
Rudolf Adamkovič writes:
> From 34f28236366affb510bfdb70a3577e765d9e0abb Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?=
> Date: Wed, 3 May 2023 14:59:03 +0200
> Subject: [PATCH] ob-sqlite: Use a transient in-memory database by default
>
> * etc/ORG-NEWS (New features): Add
Morgan Smith writes:
> Hello! This fix allows me to run the tests without giving it access to the
> filesystem outside of the repository. I have no clue what org-id-locations
> are
> and I'm hoping someone else does so I don't have to learn. I'm not sure if
> this is the best fix, but it work
On 06/08/2023 07:22, Rudolf Adamkovič wrote:
* lisp/ob-sqlite.el (org-babel-execute:sqlite): Default ':db' to
":memory:" instead of throwing an error.
This commit message entry does not reflect changed approach clearly
enough. Not passing :db is a bit different from default :memory:. Sorry
th
Hello, how can I get the output of a =#+begin_src org= in the current buffer?
#+begin_src emacs-lisp
(org-babel-do-load-languages
'org-babel-load-languages
'((shell . t)
(latex . t)
(emacs-lisp . t)
(org . t)
))
#+end_src
#+caption: T
Ihor Radchenko writes:
> Juan Manuel Macías writes:
>> + (vwidth (if (not lit)
>> + (if versewidth (format "\\settowidth{\\versewidth}{%s}\n"
>> versewidth) "")
>> + ""))
>
> Can just do (if (and versewidth (not lit)) (format ...) "")
>
>> + (linres
Edgar Lux writes:
> #+begin_src org
> #+latex_header: \usepackage{nil}
> #+end_src
>
> What I want is to get =#+latex_header: \usepackage{nil}= in the current
> buffer. The documentation (Org-info and the docstring of
> =org-babel-execute-src-block=) says that this command would
> #+begin_quo
Ihor Radchenko writes:
> Yes, org-mouse modifies the behavior of certain key bindings. Not
> directly, but by advising `org-open-at-point'.
IIRC Emacs core libraries should not advise functions.
This is something we should fix.
Also, I'm not sure org-mouse.el has its place in Org's core nowaday
Thanks!!!
Regarding the typo, it does not show here. But in the info buffer, the =(see
*note...= becomes (see see ...).
See (:P) attachment
On Aug 12, 2023 at 1:07 PM, Ihor Radchenko wrote:Edgar
Lux writes:
> #+begin_src org
> #+latex_header: \usepackage{nil}
> #+end_src
>
> What I want i
On 12/08/2023 16:29, Ihor Radchenko wrote:
Morgan Smith writes:
Hello! This fix allows me to run the tests without giving it access to the
filesystem outside of the repository. I have no clue what org-id-locations are
and I'm hoping someone else does so I don't have to learn. I'm not sure if
may i post a few notes?
i've had tehse previously.
1.
i rely on org-mouse for accessibility, as i often cannot use keyboard
at all, so there is a personal stake in having it be part of org so
that it is fully integrated. of course i have no problem with having
to enable it instead of only load
On Friday, August 11, 2023 at 09:34:31 AM PDT, J. G.
wrote:
> Hi, I'm trying to figure out why I'm getting consistent failures using
> org-bibtex-yank. This appears to be identical to the problem posted here:
On further investigation I have pinpointed the precise error as referenced by
the com
The following Warning message appeared while I was entering text into an
Org-Roam file.
[BUG] Warning (org-element-cache): org-elemt--cache: Org parser error
in 2023073121272-student_reports_august_2023.org::7669. Resetting. The
error was: (wrong-type-argument integer-or-marker-p nil) Backtra
--text follows this line--
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.
--
Hi, I'm trying to figure out why I'm getting consistent failures using
org-bibtex-yank. This appears to be identical to the problem posted here:
https://stackoverflow.com/questions/31174281/org-bibtex-yank-fails-with-wrong-type-argument-stringp-nil
On my system I am using a fresh Ubuntu 23.04 VM
>> By the way, using Ihor's suggestion, I was able to debug the issue.
>> There is nothing wrong with my configuration. The issue is that the
>> font cannot deal with that symbol, and LaTeX just skips it. Still, it
>> would be convenient not to have to create a separate .tex to debug
>> the preview
17 matches
Mail list logo
