On Mon, Dec 27 2021, Jose A. Ortega Ruiz wrote:
> On Mon, Dec 27 2021, Mandar Mitra wrote:
> i was surprised by this (new?) behaviour too. in my case, i "fixed" it
> with
>
> (setq org-adapt-indentation t)
>
> if memory serves, i found about this variable in the info manual.
>
> hope this
I just realized I was un-CCed out of the thread
Here's the updated patch with the requested changes (actually single one)
Lemme know if I'm missing anything else.
Felipediff --git a/lisp/org/ob-scheme.el b/lisp/org/ob-scheme.el
index f4836b23fe..8720bd099e 100644
--- a/lisp/org/ob-scheme.el
+++
Max Nikulin writes:
> Let's consider the following example:
>
> >8
> Test
>
> #+begin_src elisp
>(message "Test")
> #+end_src
> 8< -
>
> emacs -Q -L ~/src/org-mode/lisp/ --eval "(custom-set-variables
> '(org-babel-load-languages '((emacs-lisp . nil" babel-exec.org
>
>
Sebastian P. Luque writes:
> This is great, and very interesting to learn about the BIND keyword.
>
> Thank you,
You're welcome. Of course, if you use the filter very often, it is not
necessary to include it in a document or use the bind keyword. It
would be enough to add the function to your ini
Nicolas Goaziou writes:
> Hello,
>
> Thanks. Some comments follow.
Thanks for the review!
> Jonas Bernoulli writes:
>
>> +In description lists the used bullet is significant when exporting to
>> +Texinfo; when in doubt, then use =-=. An item that uses =+= instead
>> +becomes a new entry in th
Nicolas Goaziou writes:
> There's a mismatch between the keys.
Fixed.
> Simply put:
>
> Command in parenthesis, as done above, is optional.
Done.
>> +Regardless of which approach you use, you must define the =kbd= macro
>> +(see [[*Macro Replacement]]), which you can then use anywhere in the
On Mon, 27 Dec 2021 13:28:08 +,
Juan Manuel Macías wrote:
> Sebastian P. Luque writes:
>> Thank you, Juan. Unfortunately, there is a price for this solution
>> as it is now impossible to name and refer to this segment as usual:
> I see. Have you tried the option with LuaTeX that I put in my
On Mon, Dec 27 2021, Mandar Mitra wrote:
> I have org 20210929 installed.
>
> With emacs -Q and (package-initialize) evaluted in the *scratch*
> buffer, I see the following change in behaviour:
>
> * ABCD
>
>
>
>
> I'm fairly sure that, before the last upgrade, I used to get
>
> * ABCD
>
>
>
> Am 26.12.2021 um 16:03 schrieb Ihor Radchenko :
>
> Axel Kielhorn writes:
>
>> I have just installed Org mode 9.5 and get a few failing tests:
>>
>> Which LANG = de_DE.UTF-8 I get:
>>
>> But which LANG = C I get:
>
> I am unable to reproduce both the failures on my side
Neither can I wi
Sebastian P. Luque writes:
> Thank you, Juan. Unfortunately, there is a price for this solution as
> it is now impossible to name and refer to this segment as usual:
I see. Have you tried the option with LuaTeX that I put in my other
message? You can compile with LuaTeX also using latexmk:
(set
On Mon, 27 Dec 2021 07:41:59 +,
Juan Manuel Macías wrote:
[...]
> If you use the caption package (https://www.ctan.org/pkg/caption), you
> can indicate in each figure the width of the caption. In this case,
> you would have to introduce the code using raw latex via the
> `:caption' property:
I am sorry that I sent previous message to emacs-orgmode list only, not
to debbugs.
On 27/12/2021 02:51, Rudolf Adamkovič wrote:
Max Nikulin writes:
Rudolf, do have support BibTeX as babel language loaded to Org (by
customization of `org-babel-load-languages' or by explicit `require')?
I ha
P.S.: I have come up with another possibility, more automatic, on the
LaTeX side, if you compile with LuaTeX. This thread
(https://tex.stackexchange.com/questions/202046/width-of-the-caption-of-a-figure),
where someone proposes to use a \savebox for concrete images, gave me
the idea. We can automat
13 matches
Mail list logo