Am Sonntag, dem 22. Oktober 2023 schrieb Jambunathan K:
> I am the original author of ox-odt.el.
>
> The page break feature is available as part of
> https://github.com/kjambunathan/org-mode-ox-odt
I took a look at
https://github.com/kjambunathan/org-mode-ox-odt/blob/master/notes/SNIPPETS.org#imp
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
-
Ihor Radchenko writes:
>> My suggestion is to add a :environment attribute next to another
>> :environment-options attr (or something like that, to introduce any
>> arbitrary LaTeX code). A LaTeX image can be enclosed in many environment
>> types, float or non-float.
>
> As I said above, I feel th
In the following code block, a propertized (inverse video) before-string
overlay appears when "results: none" is used, but the property is absent
(the overlay text appears normal) when "results:silent" is used:
# with ":results none" it works as expected - inverse video Foo appears
# with ":result
Hi,
Below are some minor comma niggles.
Cheers,
Loris
Uwe Brauer writes:
"IR" == Ihor Radchenko writes:
>
>> Uwe Brauer writes:
>>> I recommend then to clarify this is in the manual: the expression in the
>>> manual is
>>> `("export")'
>
>> What about the attached patch?
>
> I added
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> I recommend then to clarify this is in the manual: the expression in the
>> manual is
>> `("export")'
> What about the attached patch?
I added some lines, and run rediff and I hoper therefore the modified patch is
ok.
Feel free to
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> I recommend then to clarify this is in the manual: the expression in the
>> manual is
>> `("export")'
> What about the attached patch?
> From f94d0c8dfa875983332dfe9432e6ec896c62bf59 Mon Sep 17 00:00:00 2001
> Message-ID:
>
> From:
Uwe Brauer writes:
> I recommend then to clarify this is in the manual: the expression in the
> manual is
> `("export")'
What about the attached patch?
>From f94d0c8dfa875983332dfe9432e6ec896c62bf59 Mon Sep 17 00:00:00 2001
Message-ID:
From: Ihor Radchenko
Date: Mon, 23 Oct 2023 15:30:42 +0
I heard everybody referencing "org-plantuml" several times here :-)
I gave it a try, and, for reference, this is how my "org-plantuml" is
being set up in my case:
(org-babel-do-load-languages 'org-babel-load-languages '(
[...]
(plantuml . t)
[...]
))
(setq org-plantuml-exec-mode 'pla
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> This is not a correct format. Please, review the manual section I linked
>>> to.
>>
>> So it should be
>> #+options: SELECT_TAGS: ("noexport")
>> #+options: EXCLUDE_TAGS: ("export")
>>
>> Right?
> No.
> #+SELECT_TAGS: tag1 tag2 ...
Max Nikulin writes:
>> I am not sure what you mean by callback.
>
> Originally I had an idea that :export should call some function that
> adds a note to info. Now I have another proposal. Instead of returning a
> cons, :export function should return result of some new function, e.g.
> (org-as
Ihor Radchenko writes:
Perhaps there's some reason why
point is not preserved in this case. But for me at least, this is not
what I'd expect, and I find it somewhat disrupting, especially when
I'm working on a folded tree (defeats speed keys, etc.).
>>>
>>> I see no particula
On Sat, Oct 21, 2023 at 10:50:08AM +0700, Max Nikulin wrote:
Does it work when executed from Emacs shell or eshell buffers?
Could you, please, provide complete sequence of commands to generate a
graphics file from a ditaa source for a shell running in Emacs?
"M-x shell" and then:
sh-5.1$ e
On 23/10/2023 16:17, Ihor Radchenko wrote:
Max Nikulin writes:
WRT cons vs. plist, I am mostly neutral. Slightly in favour of plist for
future extensibility.
I am not sure what you mean by callback.
Originally I had an idea that :export should call some function that
adds a note to info. Now
On 22/10/2023 16:00, Ihor Radchenko wrote:
Max Nikulin writes:
P.S. I am against using non-printable characters for markup. It might be
an \... entity for page break inside a paragraph, "#+...:" keyword
between block-level elements, etc.
What about all the above? We may provide entity, keywor
[திங்கள் அக்டோபர் 23, 2023] Ihor Radchenko wrote:
>>> Also, we might want to add a subsection describing the new customization to
>>> 17 Miscellaneous section of the manual. Otherwise, users might have
>>> difficulties discovering relevant settings to customize dnd and yank
>>> behavior.
>>
>> I h
Juan Manuel Macías writes:
>> So, the difference between :environment and :float is that :float also
>> encapsulates \caption in addition to the actual environment (like
>> tabularx or includegraphics) used for transcoded exported element.
>
>> I can see how :float+:placement can be imprecise and
Max Nikulin writes:
>>> For ascii backend :export function from `org-link-parameters' may return
>>> (PATH . DESCRIPTION) `cons' instead of string.
>>
>> This is non-standard. We should document it somewhere in the manual.
>
> Currently the question is whether it is acceptable or it should be
>
Visuwesh writes:
>> Is there any particular reason why you insert a newline after the image
>> link?
>
> I think this can stay here until Po Lu writes the platform-agnostic code
> that you requested further down this thread?
Sure.
>> Also, we might want to add a subsection describing the new cu
Hi,
Thanks for the follow up.
I found a similar issue in Beamer's GitHub issue and added my comment:
https://github.com/josephwright/beamer/issues/100#issuecomment-1731863334
Unfortunately, thanks to your follow up I just realized this issue was closed,
so I opened a brand new one:
https://git
Uwe Brauer writes:
>> This is not a correct format. Please, review the manual section I linked
>> to.
>
> So it should be
> #+options: SELECT_TAGS: ("noexport")
> #+options: EXCLUDE_TAGS: ("export")
>
> Right?
No.
#+SELECT_TAGS: tag1 tag2 ...
Same for #+EXCLUDE_TAGS.
> I am wondering why it wo
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> I think that we may need to introduce a customization for default link
>> description. Some backends hard-code the default description to
>> something non-trivial and some just use arbitrary fallback like ???
>> (ox-ascii), "No description"
22 matches
Mail list logo
