On 09/03/2024 22:24, Juan Manuel Macías wrote:
Well, I hope that in the last commit the two bugs that you mentioned
have been fixed. Please check:
Albha@Beta[
@sp@n{lorem ipsum}
{lorem ipsum}
Thanks, Juan Manuel. I do not see issues any more.
I would still consider unit tests to not
On 09/03/2024 22:23, Max Nikulin wrote:
On 08/03/2024 18:16, Ihor Radchenko wrote:
Attaching tentative patch that fixes the problem.
I propose to add unit tests, see first attachment.
I have tried to add some unit tests, but I faced an issue with
`org-create-math-formula'. It creates
Hello Org mode developer,
I've noticed that when using the :extend face property with org-fold,
the background color of the headline face will sometimes be left behind
after unfolding a heading. I have finally determined that this is
happening when the heading has a trailing newline and the
Hello,
How can I access to an in-buffer setting value, from Elisp code ?
Best regards
I'm thinking about adding a new global attribute, `:export', that
would granularly control whether or not to export the object and how to
export it.
Possible values: "noexport", "contents" (it would export only the content)
or the backends to which you want to export, separated by spaces. Each
On Thursday, March 7th, 2024 at 11:12, William Denton
wrote:
> I recompiled Emacs and Org last night and closed all my buffers except for
> two medium-sized ones, neither with any LaTeX in them. I restarted and spent
> a minute or two with one buffer, closing and expanding headings, and just
Juan Manuel Macías writes:
> Max Nikulin writes:
>
>> However it is still gives
>>
>> (org-export-string-as "Alpha@Beta["
>> 'html
>> '(:export-options (body-only)))
>> Debugger entered--Lisp error: (wrong-type-argument
>> number-or-marker-p nil)
>
> I think the
On 08/03/2024 18:16, Ihor Radchenko wrote:
Max Nikulin writes:
I decided not to introduce stdin. User can always use echo %i | ... instead.
printf "%%s" %i
should be safer. However in this particular case, input that may be
recognized like echo options ("-n") should be wrapped with LaTeX
Ihor Radchenko writes:
> Morgan Willcock writes:
>
>>> Would you be able to upgrade to the development version of Org mode and
>>> test if the warning disappear?
>>
>> I would be willing to for diagnostic purposes (presumably I would just
>> make sure the development version is earlier in the
Max Nikulin writes:
> However it is still gives
>
> (org-export-string-as "Alpha@Beta["
> 'html
> '(:export-options (body-only)))
> Debugger entered--Lisp error: (wrong-type-argument
> number-or-marker-p nil)
I think the problem is the contents-begin variable.
On 09/03/2024 01:57, Juan Manuel Macías wrote:
Ok, I think you and Maxim are right. This is a clear bug. I hope it
was fixed in the last commit.
(org-export-string-as "Alpha@Beta{" 'latex t))
==> Alpha@Beta\{
(org-export-string-as "Alpha@Beta{gamma}" 'latex t))
==> Alpha\Beta{gamma}
Hi Pedro,
On 2024-03-08 18:07, Pedro Andres Aranda Gutierrez writes:
> I’m very interested on how your document header looks like. Can you please
> send mee a file with your header
> and a couple of dummy slides? I’m not able to reproduce the problem…
The document header was not the problem,
Hi Laurence,
Laurence von Bottorff writes:
> I'm on Debian 12 and I just started using Haskell's ghcup tools, leaving
> the stack tools behind, as advised these days. ghcup puts executables for
> Haskell such as ghc, ghci (REPL), cabal, etc. in its ~/.ghcup/bin
> directory. Next, to stop
Ihor Radchenko writes:
> After
> https://git.sr.ht/~bzg/orgweb/commit/d7b6524cf62a947db64d29c5bf879499ab8951d7,
> not only blogs are included in the front page of orgmode.org, but also
> bug reports and everything else.
Yes, https://tracker.orgmode.org/index.org includes everything.
> I do not
Jup, of course. If you look in org-lint.el, one of the cases that would
trigger a message is when the frame environment uses "frame" directly and
there is a \begin{frame} in the org.
Line 1522 onwards in org-lint.el
Best, /PA
On Mon, 4 Mar 2024 at 12:06, Ihor Radchenko wrote:
> Pedro Andres
You are right. It is easy to do from emacs-lisp scripts, looking for
LATEX_CLASS in a document and then deciding to use the org-latex-... or the
org-beamer-... functions, but it looks much more difficult in org.el itself
:(
It's just that it would look much more elegant to have only one. For me
Bastien Guerry writes:
> A complementary suggestion: let's activate the "Blog" tab on Woof (at
> https://tracker.orgmode.org) so that when people send an email to the
> list prefixed with [BLOG], it is referenced on this tab. Then, a RSS
> feed is available from
17 matches
Mail list logo
