Ihor, sorry for the late reply.
Ihor Radchenko 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+:place
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" (ox-html), or "" (ox-latex).
I wo
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> I tried
>> ,
>> |
>> | #+options: SELECT_TAGS: noexport
>> | #+options: EXCLUDE_TAGS: export
> This is not a correct format. Please, review the manual section I linked
> to.
So it should be
#+options: SELECT_TAGS: ("noexport")
> Uwe Brauer writes:
> My mistake: I didn't reload the file after adding the local
> variables: your example didn't work for me either. Sorry.
> Just follow what Ihor told you, it's simpler.
> About exporting the tags, the following option seem to do the trick:
> #+OPTIONS: tags:nil
Ah, th
Sorry for the late reply. I haven't had much time these days to
keep up with the list...
Max Nikulin writes:
> It was long time ago...
>
> On 18/02/2022 07:47, Juan Manuel Macías wrote:
>> Otherwise, if you export to LaTeX with pandoc (v. 2.14.2), the result is
>> (to my surprise) correct:
>> #+b
Uwe Brauer writes:
> I tried
> ,
> |
> | #+options: SELECT_TAGS: noexport
> | #+options: EXCLUDE_TAGS: export
This is not a correct format. Please, review the manual section I linked
to.
(side note: this is odd to set selected tags to "noexport")
#+SELECT_TAGS: noexport
#+EXCLUDE_TAGS: ex
Uwe Brauer writes:
>> Uwe Brauer writes:
>
>
>> I just tested your example. It works for me, exporting to HTML. I'm
>> using org version 9.7-pre.
>
>> What is the error ?
>
> Well since I did not set a list, org mode complained about it. Not in
> your case? I exported to LaTeX but it should mak
> Uwe Brauer writes:
> I just tested your example. It works for me, exporting to HTML. I'm
> using org version 9.7-pre.
> What is the error ?
Well since I did not set a list, org mode complained about it. Not in
your case? I exported to LaTeX but it should make any difference
> Unrelated, b
On 22/10/2023 16:13, Ihor Radchenko wrote:
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
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> | # org-export-select-tags: noexport
>> | # org-export-exclude-tags: export
> This is not right. The value must be a list.
Ok that triggered the error then
> Alternatively to file-local variables, you can also use SELECT_TAGS
> keywor
Uwe Brauer writes:
"BB" == Bruno Barbier writes:
>
>> Did you try org-export-select-tags ?
>
>> (I didn't but, from its documentation, it might be what you're looking
>> for).
> ,
> |
> | Yes I tried the following
> | Some test
> | * First section
> | * Second
Uwe Brauer writes:
> | # org-export-select-tags: noexport
> | # org-export-exclude-tags: export
This is not right. The value must be a list.
Alternatively to file-local variables, you can also use SELECT_TAGS
keyword. See 13.2 Export Settings section of the manual.
--
Ihor Radchenko // yantar9
>>> "BB" == Bruno Barbier writes:
Hi
> Hi,
> Uwe Brauer writes:
>>
>> So it would be very handy to configure the exporter for that file
>> locally that he only exports sections that have a export tag
>>
>> Is this possible?
> Did you try org-export-select-tags ?
> (I didn't but, from its
Hi,
Uwe Brauer writes:
>
> So it would be very handy to configure the exporter for that file
> locally that he only exports sections that have a export tag
>
> Is this possible?
Did you try org-export-select-tags ?
(I didn't but, from its documentation, it might be what you're looking
for).
Hi
I usually have org files with say a dozen or more sections, and if I
wish not to export a specific section I just add the noexport tag.
However, sometimes I am faces with the opposite problem. The documents
contains dozens or more section and I only want to export one or two.
So it would b
>>> "JK" == Jambunathan K writes:
> 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
> This is a fork of the ODT exporter in Emacs Orgmode.
Hello
Since I have used this exporter for some time now, I would
"brillenfi...@bluewin.ch" writes:
> I updated to org. 9.6.10 and the bug is gone!
Handled.
em...@supporter.mailer.me writes:
> I have gone through a half of the githowto and have watched the magit video
> in full.
> I will explain what I am doing step by step, so that you can comment on each
> of them;
>
> 1. git clone git://git.savannah.gnu.org/emacs/org-mode.git/
> 2. git config use
Ihor Radchenko writes:
> Jorge P. de Morais Neto writes:
>
>>> Would you be interested to submit a patch?
>>
>> Yes, I suppose I can do it! I will try do do it this weekend, but it
>> could take longer because, although it will be a simple patch, I am
>> disorganized.
It has been over one mon
Max Nikulin writes:
> it was discussed that attempts to customize export to plain text of link
> types such as "elisp:" and "shell:" break formatting as notes at the end
> of the heading (`org-ascii-links-to-notes').
>
> The attached patches is a draft implementing this feature (new functions
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, keyword, and also ^L.
--
Ihor Radchenko //
Marvin Gülker writes:
> ...
> On the other hand, there are semantic page breaks. The page break I
> described in the OP is of this kind – it has been added specifically to
> hide the proposed solution from the first page and allow me to just
> print page 1 and hand that one to the students. For t
Max Nikulin writes:
> On 21/10/2023 16:19, Ihor Radchenko wrote:
>> - page breaks location is very much backend-dependent; typographic
>> detail https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost
>
> Is the link correct?
Indeed, it is not.
The right link is:
https://list.orgmode.org/o
Björn Bidar writes:
> * How to reproduce
> 1. emacs -Q or minimal org config
> 2. create a todo file like this one:
> * TODO bar
> foo
> * NOT-VALID foo
> bar
> 3. Set org-icalendar-include-todo to '("TODO")
> 4. C-c C-e c f
> 5. inspect the created ics file
Fixed, on main.
https://git.savannah.
Rudolf Adamkovič writes:
> Consider the sentence
>
> "This is a [[link]]."
>
> in a document with a "<>" target.
>
> Org exports the sentence to HTML as
>
> "This is a No description for this link."
>
> and to PDF as
>
> "This is a ."
Confirmed.
> How about we export it as
>
> "This is
"Fraga, Eric" writes:
> Confirmed: same issue for me.
>
> However, having looked at the LaTeX generated, I do not believe this is
> a bug in org; rather, it is likely an issue with beamer so you may need
> to bring this up on one of the LaTeX lists/groups.
Guillaume, may I know if you posted a b
26 matches
Mail list logo
