Marc Nieper-Wißkirchen writes:
> I have been talking to jao (from geiser). The following version of
> ob-scheme.el signals an error when executing Scheme code blocks.
> Besides two function declarations, the only change is in the function
> org-babel-scheme-execute-with-geiser.
Do you mean that
Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > I have been talking to jao (from geiser). The following version of
> > ob-scheme.el signals an error when executing Scheme code blocks.
> > Besides two function declarations, the only change is in
Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko
> :
> >
> > Marc Nieper-Wißkirchen writes:
> >
> > > I have been talking to jao (from geiser). The following version of
> > > ob-scheme.el signals an error when execu
On 2022-12-31, at 02:18, Thomas S. Dye wrote:
> David Masterson writes:
>
>> Anyone have a recommendation for a LaTeX tutorial that would
>> (especially) help me understand the LaTeX exported by Org and how to
>> enhance what is exported (new document classes, etc.). I don't want
>> to
>> bor
Am Sa., 31. Dez. 2022 um 11:19 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
> :
> >
> > Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko
> > :
> > >
> > > Marc Nieper-Wißkirchen writes:
[...]
> > > It is not what we usually
A couple of documents I have used in the past might be useful:
- https://archive.org/details/lshort
- https://texdoc.org/serve/visualFAQ.pdf/0
--
: Eric S Fraga, with org release_9.6-124-g036cc0 in Emacs 30.0.50
Marc Nieper-Wißkirchen writes:
> Please find attached a version that does not signal an Elisp user
> error, but calls `org-babel-eval-error-notify' instead.
If you can, could you please send the changes in form of a patch
instead? It is then easier to review.
See https://orgmode.org/worg/org-con
Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> I don't think we have an example.
>> Probably, we can create etc/org-news-images folder, set :DIR: property
>> in etc/ORG-NEWS to that folder, and then use attachments.
>
> I suggest we don't go in that direction: I'd rather keep etc/ORG-NEWS
Bastien writes:
>> 5. We can offer to move orphaned repositories to sr.ht under our control
>>and mention that we can do minimal maintenance then.
>
> I'm not sure about this.
>
> Another idea is to rename org-contrib to org-orphanage and to offer to
> add *.el files there? This way we make
-(dolist (org-file (directory-files-recursively default-directory "\\.org$"))
+(dolist (org-file (directory-files-recursively
+ default-directory "\\.org$"
+ nil (lambda (n) (not (string-match-p "archive" n)
Won't it also discard all the files with word "arc
"Berry, Charles" writes:
> So if elisp lists are to be converted to R lists, ob-R will need to know
> whether the list came from a table to decide whether to render top level
> elements as list elements or as data.frame rows.
This information should be available: lists are passed as Elisp list
Matt writes:
> > > +;; TODO refactor into macro. Currently violates (elisp) Coding
> > > +;; Conventions and is hard to debug.
> > > (defun org-babel-shell-initialize ()
> > >"Define execution functions associated to shell names.
> >
> > Could you please elaborate? Which particular c
Please find the patch file attached to this email.
Thank you,
Marc
Am Sa., 31. Dez. 2022 um 13:07 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > Please find attached a version that does not signal an Elisp user
> > error, but calls `org-babel-eval-error-notify' instead.
>
Stephen Eglen writes:
> I use straight.el for package management, and a recent package (I think
> it was todoist.el) pulled in org-mode. This then caused the warning
> about mismatch between the org-mode in Emacs and the one from the repo.
>
> I read the *Warning* and in particular this bit:
>
>
Marc Nieper-Wißkirchen writes:
> Please find the patch file attached to this email.
Thanks!
I will give some general comments and leave the ob-scheme changes for
Rudolf.
> Subject: [PATCH] Display evaluation errors for Scheme code blocks.
If you can, please provide changelog entries explaining
Eric Chun writes:
> I can't seem to use the M-g M-n keys to jump to occurrences in sparse tree
> search for second org file within same Emacs window.
> If I search first file by pressing C-c / r RET and then search second
> file by pressing C-c / r RET, I'm not able to jump to occurrences in
Sharon Kimble writes:
> I have a long-standing problem with a numerical ordered list which is broken
> by sub-headings, and exported to latex.
>
> On looking at the org manual, the most recent one that I have, on page 12, it
> shows something like '[@20]' which when exported shows exactly the s
Tom Gillespie writes:
>> What about modifying `org-confirm-babel-evaluate' to allow these values:
>>
>> - t : confirm header vars *and* code blocks
>> - 'code : confirm code blocks
>> - 'vars : confirm vars
>> - nil: don't confirm
>>
>> and set the default value to 'code, while allowin
nunnery-09-bays...@icloud.com writes:
> The HTML Export is a bit broken when the checkbox item has table
> content. See the HTML exporting difference between section A and B in follow
> code. (also attached a screenshot below)
>
> #+BEGIN_SRC org
> * A
> 1. [ ] test
> 2. [ ] foo
> 3. [ ] bar
>
>
Pedro Andres Aranda Gutierrez writes:
>> This is to be expected because of how Org parser works.
>
> In my experience, this also applies for some situations while creating
> listings.
> My question is if there would be space for a `:raw t` in the
> `#+begin_export latex` to produce a _verbatim_ c
Matt writes:
> I've backed out the `require' change and adjusted everything else based on
> your feedback. There is a separate patch for each refactor that created a
> new test. The remaining refactors are in a single patch. I was also able
> to resolve the issue I had with inserting the t
Done!
Am Sa., 31. Dez. 2022 um 14:24 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen writes:
>
> > Please find the patch file attached to this email.
>
> Thanks!
> I will give some general comments and leave the ob-scheme changes for
> Rudolf.
>
> > Subject: [PATCH] Display evaluation err
Under release_9.6-173-g24740a
I have file
#+begin_src org
,* h1
,** h2
#+end_src
I do
M-x org-promote-subtree
on h2, which works as expected; then
M-x undo
The file becomes
#+begin_src org
,* h1
,** * h2
#+end_src
and I have the message
primitive-undo: Changes to be undone by f
Ihor: "`org-occur-next-match' does not support multiple buffers.Looking at
the docstring of `next-error-function', I am also not sure if
we need to support this there. The docstring talks only about the
current buffer."
I'm assuming "current buffer" is the buffer which I can currently type input
> P.S. Considering intense discussion around the topic, what about
> reverting my commit from the release? We can then re-consider the whole
> design and apply something more elaborate later.
I was actually going to mention that in my previous
message but forgot. I think that given the potential
f
The manual says:
You can interactively insert a drawer at point by calling
‘org-insert-drawer’, which is bound to ‘C-c C-x d’. [...] With a
prefix argument, this command calls ‘org-insert-property-drawer’,
which creates a ‘PROPERTIES’ drawer right below the current
headline.
Fo
alain.coch...@unistra.fr writes:
> The manual says:
>
>You can interactively insert a drawer at point by calling
>‘org-insert-drawer’, which is bound to ‘C-c C-x d’. [...] With a
>prefix argument, this command calls ‘org-insert-property-drawer’,
>which creates a ‘PROPERTIES’ dra
> Il 30/12/2022 18:42 Colin Baxter ha scritto:
>
>
> > Angelo Graziosi writes:
>
> > tomas wrote:
> >> there is now a defvar `org-element-cache-persistent'
>
> > Ah! didn't knew that..
>
> > Setting
>
> > (setq org-element-cache-persistent nil)
>
> > seems to w
On 31/12/2022 21:08, Ihor Radchenko wrote:
nunnery-09-bayside writes:
a. [ ] foo
b. [ ] bar
| a | b | c |
[ ] foo
[ ] bar
I would expect e.g.
[ ] bar
Probably, the reason is tag in the first paragraph of the item.
I am not sure, however, if it is safe to drop it.
If an
"Fraga, Eric" writes:
> A couple of documents I have used in the past might be useful:
>
> - https://archive.org/details/lshort
This one sounds interesting and it's online.
> - https://texdoc.org/serve/visualFAQ.pdf/0
I'm not sure what language this one is in.
Thanks.
--
David Masterson
"Thomas S. Dye" writes:
> David Masterson writes:
>
>> Anyone have a recommendation for a LaTeX tutorial that would
>> (especially) help me understand the LaTeX exported by Org and how to
>> enhance what is exported (new document classes, etc.). I don't want
>> to
>> bore you all with a lot of
David Masterson writes:
> "Fraga, Eric" writes:
>
>> A couple of documents I have used in the past might be useful:
>>
>> - https://archive.org/details/lshort
>
> This one sounds interesting and it's online.
There is also LaTeX Tutorials. A primer
https://www.tug.org/twg/mactex/tutorials/ltxpri
32 matches
Mail list logo
