Max Nikulin writes:
> To wrap up, I suggest (and I do not insist) to drop
> "-Djava.awt.headless=true" since "-headless" is anyway added in jar
> mode. Those who desperately need namely "-Djava.awt.headless=true" (for
> some unknown to me reason) may customize :java header argument. I do not
On 2022-05-07, at 10:16, Max Nikulin wrote:
> On 02/05/2022 23:52, Marcin Borkowski wrote:
>> On 2022-05-01, at 22:01, Berry, Charles wrote:
On May 1, 2022, at 2:20 AM, Marcin Borkowski wrote:
I'd like to export a Org-mode formatted string to markdown, but without
the table
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>> The time will be the same: 9pm SG time (4pm Kyiv; 2pm London; 9am New
>> York). Sat, May 7
>>
>> I will post the link to the meeting one hour before the meeting start.
>
> Meeting link: https://teamjoin
Aloha Max,
Max Nikulin writes:
On 08/05/2022 07:30, Juan Manuel Macías wrote:
Thomas S. Dye writes:
Is there a way to add an arbitrary LaTeX command between
\begin{figure} ... \end{figure} during LaTeX export? I want
to end up
with the following snippet, but can't figure out how to slip
On 08/05/2022 07:30, Juan Manuel Macías wrote:
Thomas S. Dye writes:
Is there a way to add an arbitrary LaTeX command between
\begin{figure} ... \end{figure} during LaTeX export? I want to end up
with the following snippet, but can't figure out how to slip in
\setfloatalignment{b}. \begin{fig
Max Nikulin writes:
> On 28/10/2021 11:04, Greg Minshall wrote:
>>
>> i wonder if it would be reasonable to add an option such that, when
>> tangling, `org-babel-tangle` would not write a file with the
>> already-existing contents of the target file?
>>
>> this would be helpful, e.g., for those
Aloha Juan Manuel,
Juan Manuel Macías writes:
Hi, Thomas,
Thomas S. Dye writes:
Is there a way to add an arbitrary LaTeX command between
\begin{figure} ... \end{figure} during LaTeX export? I want to
end up
with the following snippet, but can't figure out how to slip in
\setfloatalignmen
Hi, Thomas,
Thomas S. Dye writes:
> Is there a way to add an arbitrary LaTeX command between
> \begin{figure} ... \end{figure} during LaTeX export? I want to end up
> with the following snippet, but can't figure out how to slip in
> \setfloatalignment{b}. \begin{figure}[htb]
> \centering
> \inc
Aloha all,
Is there a way to add an arbitrary LaTeX command between
\begin{figure} ... \end{figure} during LaTeX export? I want to
end up with the following snippet, but can't figure out how to
slip in \setfloatalignment{b}.
\begin{figure}[htb]
\centering
\includegraphics[width=.9\linewid
Ihor Radchenko writes:
> Ignacio Casso writes:
>
>>> Sounds reasonable. Could you prepare a patch?
>>> COMMENT should be inside a shy group and note that there might be an
>>> arbitrary number of space after COMMENT string.
>>
>> Here it is.
>
> Thanks! Could you also update the org-complex-hea
Hi all,
In the attached patch I add a new command for org-attach: save *all*
attachments from the current Gnus article to the current org-attach-dir.
(Sorry for repeating the word "attach" so much :-))
NB:
1. If no Gnus article is open, it returns an error message.
2. I've only tested it on Em
John Kitchin writes:
> Where did you add that?
>
> John
>
> ---
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.c
Where did you add that?
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Fri, May 6, 2022 at 11:40 AM
John Kitchin writes:
> I like the variable idea. I would make it a concatenation string for
> joining. That way “” would concatenate the way Tyler wants, “ “ would
> preserve current behavior, and “,” could lead to a comma separated
> list for example. Other things like “\n” might lead to a colum
Ihor Radchenko writes:
>
> Thanks! Since Felipe has no objections, your patch should be good to apply.
>
> Could you kindly add the geiser version info as a comment inside code?
> Commit message is an unlikely place to be checked regularly and be
> noticed as geiser is updated in future.
>
> Com
Ihor Radchenko writes:
> The time will be the same: 9pm SG time (4pm Kyiv; 2pm London; 9am New
> York). Sat, May 7
>
> I will post the link to the meeting one hour before the meeting start.
Meeting link: https://teamjoin.de/Org-dev-profiling-20220507-d708k
Best,
Ihor
I like the variable idea. I would make it a concatenation string for
joining. That way “” would concatenate the way Tyler wants, “ “ would
preserve current behavior, and “,” could lead to a comma separated list for
example. Other things like “\n” might lead to a column, etc.
On Sat, May 7, 2022 at
Hi Timothy,
Very nice set of patches, it looks good. Listings and minted are still
workable options and your new engrave library is available. I must admit
it's not clear how to customize faces since engrave is a bridge between
major modes choices and latex but maybe show one or two examples (say
Ooops, a paren error managed to slip in there.
Here’s a new set, with a little extra refactoring slipped in.
–
Timothy
>From d231437e2c9f96bf70520d9ddda810a95667fcdd Mon Sep 17 00:00:00 2001
From: TEC
Date: Sun, 21 Nov 2021 14:35:34 +0800
Subject: [PATCH 1/7] ox-latex: Refactor `org-latex-src-bl
On Saturday, 7 May 2022 at 14:55, Vikas Rawal wrote:
> I am not sure I understand fully, but are you suggesting that the
> problem is because I forgot to compile org and therefore these files
> were being compiled during runtime? Would running "make" solve it
> then? I have done that anyway since
>
> These are native-comp warnings. They are not uncommon when
> native-compiling Org (not only org-fold.el) and generally harmless.
> If you are sufficiently annoyed with them, most of these warnings can be
> "fixed" by declaring the missing functions. The functions are available
> at runtime, but
Hi Ihor,
On Saturday, 7 May 2022 at 13:30, Ihor Radchenko wrote:
> While you are at the deadline, feel free to switch org-fold-core-style
> back to overlays.
Thank you. I should have done that (had I thought if it ;-)) but
deadline met in any case. Next time.
> If you get some time and encoun
On 02/05/2022 23:52, Marcin Borkowski wrote:
On 2022-05-01, at 22:01, Berry, Charles wrote:
On May 1, 2022, at 2:20 AM, Marcin Borkowski wrote:
I'd like to export a Org-mode formatted string to markdown, but without
the table of contents.
(org-export-string-as my-string 'md t '(toc nil))
didn
A couple additional notes for the case that someone will find this
thread in future.
On 28/10/2021 11:04, Greg Minshall wrote:
i wonder if it would be reasonable to add an option such that, when
tangling, `org-babel-tangle` would not write a file with the
already-existing contents of the targe
On 07/05/2022 11:15, Ihor Radchenko wrote:
Vikas Rawal writes:
After upgrading to 9.5.3, I am getting warnings such as this, which I
suspect are due to org-fold.et.
Warning (comp): org-fold.el:834:27: Warning: Unused lexical variable
`org-hide-macro-markers' Disable showing Disable logging
War
Hi Ihor,
Find attached an updated patchset, and comments below :)
Ihor Radchenko writes:
> Maybe “The other two options”? Also, using first/second here is a bit
> confusing because: (1) they are actually 3/4 in the above list; (2)
> engraved is listed last.
Docstring changed.
>> +The second m
Ihor Radchenko [2022-05-07 Sat 12:22] wrote:
> Now, we have different kinds of hidden text at hand:
> - folded headlines/lists
> - folded drawers
> - folded blocks
> - folded links/emphasis
>
> The question is what should be the logical behaviour of Org when editing
> text inside or at the border
27 matches
Mail list logo
