-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ihor Radchenko writes:
> Just trying to export to latex this afternoon and this showed in the
> mini-buffer -
> -
> | (void-variable org-latex-babel-language-alist) in org-latex-template
> -
>
> Please update again. The bug has been
Ihor Radchenko writes:
> Tim Cross writes:
>
>> As this module has never been part of org core, there is considerable
>> work which would need to be done as a prerequisite e.g. updating the
>> manual and adding documentation and examples, adding unit tests
>> etc. Therefore, I don't think ther
Greetings again, Ihor.
Ihor Radchenko writes:
> After removing org-contrib over a year ago, your email is the first
> issue raised regarding ob-asymptote removal.
This is an interesting observation.
I have been using Asymptote with Org all the time, with the latest Org
from ELPA. Only when m
Mamoru Miura writes:
>>But I am not even sure if this calculation is always same in different agenda
>>types...
>
> Where can I get the specification of agenda types? I'm interested in
> the refactoring (but cannot work on it immediately...)
1. 11.2 The Agenda Dispatcher section of the manual
2
Max Nikulin writes:
> Hi,
>
> I figured out why "make test" is passing successfully while the same
> with BTEST_RE="test-ol/insert-link-insert-description" is failing for a
> proposed patch. Default selection pattern is ignoring most test-ol
> cases. See the attachment.
Thanks a lot for narro
Sharon Kimble writes:
> Sorry, I forgot that I can do it from the menu. Now I've updated I get this
> error message -
>
> -
> | Debugger entered--Lisp error: (void-variable
> org-link--description-folding-spec)
> | org-fold-initialize(" ▶▶▶")
Please restart Emacs.
Best,
Ihor
Tor Kringeland writes:
> If our Org file is
>
> #+begin_example
> * a heading
>
> text
> #+end_example
>
> And we insert an empty note, we get
>
> #+begin_example
> * a heading
>
> - Note taken on [2022-07-26 Tue 16:10]
> text
> #+end_example
>
> instead of the expected
>
> #+begin_example
> * a
Tor Kringeland writes:
> Currently if you insert a note on a heading that has double newlines in
> it, the empty newlines will be padded with spaces. For example
>
> #+begin_example
> * heading
> - Note taken on [2022-07-26 Tue 16:00] \\
> note with
>
> newlines it in
> #+end_exam
On 26/07/2022 19:59, Ihor Radchenko wrote:
I am attaching a tentative patch that will make Org export remove
zero-width spaces when those spaces actually separate the object
boundaries.
Ihor, I have realized that you did not address another use case: zero
width spaces may be added to suppress
Jarmo Hurri writes:
>> The advantage of maintaining ob-asymptote.el in the main asymptote
>> repo is that people who are intimately familiar with the asymptote
>> features can directly contribute and enhance the Org
>> integration. Moreover, distributing together with the asymptote means
>> no he
Jarmo Hurri writes:
>> Then, it would help to have more practical examples compared to what
>> we have in
>> https://www.orgmode.org/worg/org-contrib/babel/languages/ob-doc-asymptote.html
>
> Absolutely. I have plenty of examples from the domains of math and
> computer science.
Feel free to subm
Jarmo Hurri writes:
>> Then, it would help to have more practical examples compared to what
>> we have in
>> https://www.orgmode.org/worg/org-contrib/babel/languages/ob-doc-asymptote.html
>
> Absolutely. I have plenty of examples from the domains of math and
> computer science.
Feel free to subm
Tim Cross writes:
> As this module has never been part of org core, there is considerable
> work which would need to be done as a prerequisite e.g. updating the
> manual and adding documentation and examples, adding unit tests
> etc. Therefore, I don't think there is any need to make a decision o
Ihor Radchenko writes:
> Another question is long-term maintainability. We have a limited
> manpower and cannot cater too many support requests or take care about
> parts of code not used by most people. After removing org-contrib over a
> year ago, your email is the first issue raised regardin
Thank you for reviewing my patch.
>Ideally, we should factor out the duration calculation from the depths of the
>agenda code into a separate function and then use it.
I agree with it.
>But I am not even sure if this calculation is always same in different agenda
>types...
Where can I get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ihor Radchenko writes:
> Just trying to export to latex this afternoon and this showed in the
> mini-buffer -
> -
> | (void-variable org-latex-babel-language-alist) in org-latex-template
> -
>
> Please update again. The bug has been
Hi Ihor,
A thousand apologies for my horrible carelessness with the parentheses.
I should have checked the code. Here goes the patch again corrected. I
hope it's alright now.
Ihor Radchenko writes:
> Also, the original code contained the clause:
> (or (get lang from the alist1)
> (get lang f
On 26/07/2022 19:59, Ihor Radchenko wrote:
This is a bug. While escape symbols do not affect export in most common
scenarios, your report is adding yet another case when zero-width space
is actually altering the export result.
I agree is zero-width space used as an escape character is too
int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ihor Radchenko writes:
> Just trying to export to latex this afternoon and this showed in the
> mini-buffer -
> -
> | (void-variable org-latex-babel-language-alist) in org-latex-template
> -
>
> Please update again. The bug has been
Hi,
I figured out why "make test" is passing successfully while the same
with BTEST_RE="test-ol/insert-link-insert-description" is failing for a
proposed patch. Default selection pattern is ignoring most test-ol
cases. See the attachment.From 0cb30c77d888a38360f11657f7a391ab72fa312e Mon Sep 17
>
> Just trying to export to latex this afternoon and this showed in the
> mini-buffer -
> -
> | (void-variable org-latex-babel-language-alist) in org-latex-template
> -
Please update again. The bug has been introduced recently, but should be
fixed on main already.
Best,
Ihor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Just trying to export to latex this afternoon and this showed in the
mini-buffer -
-
| (void-variable org-latex-babel-language-alist) in org-latex-template
-
and this showed in the debugger -
-
|Debugger entered--Lisp error
Dear All,
this might be a very stupid question as I'm not familiar with the
internals of the Org export engine, but couldn't this change lead to
problems with the Org-to-Org export of documents containing these
"semantic separators"?
thanks and best wishes,
András
On Tue, 26 Jul 2022 at 16:52, T
Hi Ihor,
> I am attaching a tentative patch that will make Org export remove
> zero-width spaces when those spaces actually separate the object
> boundaries.
>
> Any objections?
IMO this is an immanently sensible idea. I added an export filter like this to
my config basically as soon as I found o
If our Org file is
#+begin_example
* a heading
text
#+end_example
And we insert an empty note, we get
#+begin_example
* a heading
- Note taken on [2022-07-26 Tue 16:10]
text
#+end_example
instead of the expected
#+begin_example
* a heading
- Note taken on [2022-07-26 Tue 16:10]
text
#+end_e
Currently if you insert a note on a heading that has double newlines in
it, the empty newlines will be padded with spaces. For example
#+begin_example
* heading
- Note taken on [2022-07-26 Tue 16:00] \\
note with
newlines it in
#+end_example
It would be nice to (if this is not con
K K writes:
> My use case is to emphasize chinese characters without spaces being inserted,
> even those zero-width spaces. For example "中文*测*试" should be enough to
> emphasize "测".
>
> I am using zero-width spaces right now, and it works fine in org-mode
> buffers, but if exported to latex-pd
Juan Manuel Macías writes:
> Here is the new patch. I have realized that it is not necessary to put a
> cond, since in this case it is only necessary to obtain the name of the
> language for the metadata, so this new patch is simpler.
Thanks for the update!
The patch has some misplaced parenthe
Bhavin Gandhi writes:
>> Thanks for the idea, I'm exploring (recursion-depth),
>> (minibuffer-depth). I will come up with a patch to fix this bug.
>
> So, I saved this-command and (recursion-depth) value, and I'm checking
> for it in the org-add-log-note (attaching diff of my changes). But this
>
Hi All,
Short version
t...@tecosaur.com ⟶ g...@tecosaur.net (in commits) *
tecos...@gmail.com ⟶ orgm...@tec.tecosaur.net (in communications here)
* I've sent this email from the (old) commit address to leave a paper
trail so
it's (hopefully) clear to anybody who searches for the address
Den tis 19 juli 2022 kl 15:39 skrev Ihor Radchenko :
>
> There is nothing fancy there. Just
>
> "%{fetch-bibtex}* TODO %?%(org-capture-ref-get-bibtex-field :title)"
> ":PROPERTIES:"
> ":ID: %(org-capture-ref-get-bibtex-field :key)"
> ":CREATED: %U"
> ":END:"
> "#+begin_src bibtex"
> "%(org-capture
On Tue, 2022-07-26 at 13:30 +0700, Max Nikulin wrote:
> I have not tested it, but I expect you can use
> - export filter that removes zero-width spaces at the last export
> stage.
> I assume that your documents do not contain them besides markup
> workaround
> - #+latex_header: \DeclareUnicodeChar
Greetings Ihor.
Ihor Radchenko writes:
> Jarmo Hurri writes:
>
>>> Then, would it make more sense to include ob-asymptote.el into the
>>> asymptote distribution?
>>
>> I do not think this is a good idea:
>>
>> - I am not involved in the development of asymptote, so this solution
>> would pu
Ihor Radchenko writes:
> Jarmo Hurri writes:
>>> TBH, this is the first time I'm hearing about it. I've looked it
>>> up, and indeed it seems to be useful.
>>
>> For some reason, even people who would certainly benefit from
>> Asymptote often have not heard of it. The developers do not really
>
Hello Munyoki.
Munyoki Kilyungi writes:
>> I do not understand this. Why would supporting a professional-level
>> graphics programming language be distracting someone from their work
>> when using Org?
>
> I'm not _against_ supporting a proffesional-level graphics PL. What
> I'm trying to say
Dear all,
is there a package to use org-babel execute function on ConTeXt blocks?
I would like to do a presentation with org-mode about ConTeXt.
It would be nice if I could execute source blocks with the executable
"context" and store the result in a file.
I found the tangle option that exports
36 matches
Mail list logo
