Sébastien Miquel writes:
> Hi,
>
> Ihor Radchenko writes:
>> Thanks for the clarification!
>> I did not mean to reduce the font size in affiliated keywords.
>> I was referring to replacing the display of affiliated keywords:
>>
>> #+name: A classic
>> #+tag: easy
>>
>> will be displayed by Emacs
Hi,
Ihor Radchenko writes:
Thanks for the clarification!
I did not mean to reduce the font size in affiliated keywords.
I was referring to replacing the display of affiliated keywords:
#+name: A classic
#+tag: easy
will be displayed by Emacs as
#+... A classic :easy:
The underlying text
Sébastien Miquel writes:
> To clarify, here are the two alternatives I have in mind.
>
> #+tag: easy
> #+attr_latex: A classic
> #+begin_exercice
> Find a necessary and sufficient condition on $N$ and $P$ for $P = NP$
> to hold.
> #+end_exercice
>
> #+begin_exercice A classic
Ihor Radchenko writes:
>> >> On a slightly related note, I find it quite unfortunate that one
>> >> presently cannot make use of the #+begin_ line of special blocks to
>> >> set some kind of optional title instead of using #+name or
>> >> #+attr_latex. That's a lot of wasted real
Sébastien Miquel writes:
> > We already have ":exports none" header argument.
>
> For src block yes, but not for special blocks.
>
> To explain where I'm coming from : I write mathematical content
> categorized using special blocks, such as theorems, exercices, proofs,
> personnal notes, etc.
Ihor Radchenko writes:
> Sébastien Miquel writes:
>
>> Ihor Radchenko writes:
>> > They do not. Tags are only considered inside headlines. Trying
to allow
>> > tags outside headlines will require major changes across the
whole Org
>> > codebase and will still make things incompatible
Sébastien Miquel writes:
> Ihor Radchenko writes:
> > They do not. Tags are only considered inside headlines. Trying to allow
> > tags outside headlines will require major changes across the whole Org
> > codebase and will still make things incompatible with third party
> > packages, like
Hi,
Ihor Radchenko writes:
> They do not. Tags are only considered inside headlines. Trying to allow
> tags outside headlines will require major changes across the whole Org
> codebase and will still make things incompatible with third party
> packages, like org-ql. Not to mention the whole new
On Wednesday, 31 Aug 2022 at 20:10, Sébastien Miquel wrote:
> Does anyone think this is useful and might warrant adding support for ?
I would welcome something like this, whether as tags on the src block
line or as a special header, as Kaushal suggests.
--
: Eric S Fraga, with org
Payas Relekar writes:
> Tags are bit more generic though, and allow searching across not just
> code blocks, but TODOs as well.
They do not. Tags are only considered inside headlines. Trying to allow
tags outside headlines will require major changes across the whole Org
codebase and will still
Kaushal Modi writes:
Tags are bit more generic though, and allow searching across not just
code blocks, but TODOs as well.
Thanks,
Payas
> On Wed, Aug 31, 2022 at 4:19 PM Sébastien Miquel
> wrote:
>
>> Hi,
>>
>> I've been using tags on special blocks, src blocks and other, for two
>>
On Wed, Aug 31, 2022 at 4:19 PM Sébastien Miquel
wrote:
> Hi,
>
> I've been using tags on special blocks, src blocks and other, for two
> purposes:
>
> 1. to control which blocks get exported, using the `#+exclude_tags`
> property.
> 2. to fine tune the export, according to tags, of
Hi,
I've been using tags on special blocks, src blocks and other, for two
purposes:
1. to control which blocks get exported, using the `#+exclude_tags`
property.
2. to fine tune the export, according to tags, of special blocks such as
#+BEGIN_exercice
13 matches
Mail list logo
