On Tuesday, March 5th, 2024 at 09:12, Esteban Venialgo
wrote:
> I'm a newbie with org-babel, but I think I'm facing a bug for R code
> execution. Basically, I have a simple code for testing:
>
> #+begin_src R :session test
> A = 1
> #+end_src
>
> I get a lisp error when I try to export this
Amy Grinn writes:
> I would like to add support for setting 'org-babel-noweb-wrap-start and
> 'org-babel-noweb-wrap-end for each src block individually using the
> header args :noweb-start and :noweb-end:
Here's another possible syntax we could use:
:noweb [wrap-start] [wrap-end]
#+name:
New version of the patch, which I believe address your comments.
Stefan
>From 53c8fab18625e8a722657181cb3c825a1d8c895c Mon Sep 17 00:00:00 2001
From: Stefan Monnier
Date: Tue, 5 Mar 2024 14:11:19 -0500
Subject: [PATCH 1/2] * lisp/org/ox-texinfo.el: Remove redundant `:group`s
---
I would like to add support for setting 'org-babel-noweb-wrap-start and
'org-babel-noweb-wrap-end for each src block individually using the
header args :noweb-start and :noweb-end:
#+name: firewall-safe-mode
#+begin_src sh
echo "Firewall is now in safe mode."
#+end_src
#+name: firewall
Hi,
just a very small issue I found, as I was wondering, why the agendas
file was included in the index, although it did not exist.
The problem is in org-mobile.el in Line 473, as the arguments to
expand-file-name are in the wrong order:
(when (file-exists-p (expand-file-name
hi Org-people,
I'm a newbie with org-babel, but I think I'm facing a bug for R code execution.
Basically, I have a simple code for testing:
#+begin_src R :session test
A = 1
#+end_src
I get a lisp error when I try to export this code to latex. Also, if I remove
the session name "test", the
Max Nikulin escribió:
> If some type is used through the document multiple times then it is
> better to avoid style="font-variant:small-caps" and use a CSS class
> instead. Even for LaTeX it may be better to define a dedicated command
> to be closer to semantic markup.
>
> Moreover different
On 02/03/2024 03:34, Juan Manuel Macías wrote:
│ Caesar's famous quote: ![:smallcaps t :color blue]{Alea iacta est}
==> LaTeX:
│ Caesar's famous quote:
{\scshape{}\color{blue}\foreignlanguage{latin}{\textit{Alea iacta est}}}
== HTML:
│ Caesar's famous quote: Alea iacta est
I am in doubts if
Ihor Radchenko writes:
> It looks like you are asking for a way to choose between multiple column
> specs when building column view. And that you have a very specific idea
> how to implement it. However, the details of the idea are elusive to me.
> May you elaborate?
Sure.
We have two COLUMNS
Suhail Singh writes:
> ... due to the similarity with "inline code blocks" (cf. "code
> blocks") as well as "special blocks".
.. due to the /relation/ with "inline code blocks" (cf. "code blocks")
as well as "special blocks".
> But if it were to, I do hope the names of other similar syntactic
Ihor Radchenko writes:
> In my mind, "fragment" implies no nesting.
FWIW, in the mind of this Org mode user as well.
> But the point of the "inline special blocks" is to allow nesting as
> needed.
Yes, exactly! As "inline code blocks" are to "code blocks" so too are
"inline special blocks"
Max Nikulin writes:
> Special blocks are really block-level elements. I see similarity,
> however with a better term we could avoid "inline" specifier. I think,
> the new beast may serve in some cases currently handled by macros.
> LaTeX snippets are named "fragments" in the manual.
>
> Custom
Stefan writes:
> since this patch was applied, there are now two functions in
> `org-store-link-functions` that feel responsible for id links from some
> buffers: the new `org-id-store-link-maybe` and `org-contacts-link-store`.
>
> This results in a prompt asking which one to use, which
with the given minimal example:
```
#+begin_parent
#+begin_child
#+end_child
#+end_parent
```
the code
```lisp
(org-block-map (lambda () (message "elem: %s" (org-element-at-point
```
goes through only the parent element and doesnt run the lambda on the
child block
the docstring of
Hi,
since this patch was applied, there are now two functions in
`org-store-link-functions` that feel responsible for id links from some
buffers: the new `org-id-store-link-maybe` and `org-contacts-link-store`.
This results in a prompt asking which one to use, which happens many times,
e.g.,
Ihor Radchenko writes:
> Bastien writes:
>
>> Adding [BLOG] or [TIP] in the subject prefix allows for such messages
>> to be referenced on https://tracker.orgmode.org/news (along with [ANN]
>> messages).
>>
>> It will then be possible to include these posts in the orgmode.org
>> homepage,
Bastien writes:
> Adding [BLOG] or [TIP] in the subject prefix allows for such messages
> to be referenced on https://tracker.orgmode.org/news (along with [ANN]
> messages).
>
> It will then be possible to include these posts in the orgmode.org
> homepage, using e.g.
Stefan Monnier writes:
> The "* DIRTITLE: (FILENAME)." syntax is Texinfo's syntax, and currently the
> Org user needs to know that syntax and abide by it (even though it's
> not well defined nor well documented, IME). My change mostly makes it
> unnecessary for the user to know that syntax
"Slawomir Grochowski" writes:
>:COLUMNS: %40ITEM(item) %OMEGA-3-1000(omega 3){+}
> %MULTIVITAMIN(multivitamin){+}
>:COLUMNS: ...
>:COLUMNS: ...
> ...
> Because the code for the view is 'reading' the last :COLUMNS: definition with
> function (org-entry-get nil "COLUMNS" t).
>
>
On 25/02/2024 17:41, Max Nikulin wrote:
Max Nikulin writes:
So `shell-quote-argument' is necessary and quotes around %i must be
stripped similar to %s in mailcap entries in `org-open-file'.
...
Please, revert the commit that added a misleading recommendation.
...
It should be more reliable
Philip Kaludercic writes:
> The issue is rather, I don't see the warning at all anymore ("cannot
> reproduce reliably" in the sense of might randomly occur at some point
> again).
If you see it again in future, you may add
(setq org-element--cache-self-verify 'backtrace)
to your config.
Then,
Ihor Radchenko writes:
> Philip Kaludercic writes:
>
>>> Thanks for reporting!
>>> Does the error persist if you upgrade Org mode to the latest 9.6.20
>>> version? If yes, what about the development version?
>>
>> Sorry, I cannot really reproduce the bug in any reliable way.
>
> Even if you
Max Nikulin writes:
> Special blocks are really block-level elements. I see similarity,
> however with a better term we could avoid "inline" specifier. I think,
> the new beast may serve in some cases currently handled by macros. LaTeX
> snippets are named "fragments" in the manual.
>
>
Philip Kaludercic writes:
>> Thanks for reporting!
>> Does the error persist if you upgrade Org mode to the latest 9.6.20
>> version? If yes, what about the development version?
>
> Sorry, I cannot really reproduce the bug in any reliable way.
Even if you cannot reproduce reliably, it is not a
On 05/03/2024 00:49, Juan Manuel Macías wrote:
Ihor Radchenko writes:
Max Nikulin writes:
Does anybody have an idea of a better name for a feature? Maybe
something like inline custom objects, snippets. "Objects" are used to
describe syntax, but not used in the manual though.
Custom inline
StrawberryTea writes:
> Hi, using the following test case with Emacs -Q:
> ...
> The most recent fix for the bug in 2da622cad seems to have made things
> worse. Now sometimes the background of the headline is not extended and
> other times we still have the trailing background color where it's
26 matches
Mail list logo
