The category of items in an "agenda" block view as returned by
org-agenda-get-category are truncated based on the value of the prefix
format; this isn't the case for e.g. the tags-todo view. For instance,
if an item has a category "marathon training", and your agenda and
tags-todo views both have
Juan Manuel Macías writes:
> Regarding the "optional parameters", there is nothing defined, although
> I think they should be adapted to each backend. A possible use that
> occurs to me:
>
> [prelatex: [lorem] postlatex: {ipsum} html: style="color:red;"]{blah blah}
>
> This should produce in
> Why is `:eval never` not as good ? You don't have to write it on each
> code block; you may set it globally, per file, per headline, etc.
The main reason is that I also use source blocks for babel blocks that are
runnable. So I cannot use per headline etc. solutions. I can use snippets
to
Sure. Just evaluate the following code after starting Emacs with `emacs -Q`:
┌
│ (require 'org)
│ (load-theme 'leuven t)
│
│ (dolist (face '(org-level-1 org-level-2 org-level-3 org-level-4 org-level-5
│ org-level-6 org-level-7 org-level-8))
│ (set-face-attribute face nil
Hello!
I am trying to exclude different sub-trees (a.k.a. headings or sections),
depending on the exporter backend. I am familiar with =:noexport:= to exclude
selected sections (disregarding the backend). I found a solution, but it is
only intended for a specific backend:
Hi there,
Thanks for maintaining this great piece of software.
I recently started to get the following warning from emacs when loading org
mode:
Warning (defvaralias): Overwriting value of ‘org-hide-block-startup’ by
aliasing to ‘org-cycle-hide-block-startup’
I have this in my init file:
On 21.02.2024 19:19, gerard.vermeu...@posteo.net wrote:
On 21.02.2024 10:40, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
[...]
May you please provide more details?
This is different of what I saw before:
When splitting python blocks in an org file I got a long list of
Hi Rudi,
Rudi C writes:
> After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer
> syntax highlighted in emacs. They used to be syntax highlighted when I
> specified the block's language. Any ideas?
>
> I use Doom, so it might have been a third-party feature.
>
> I know
On neděle 18. února 2024 15:29:09 CET Ihor Radchenko wrote:
> In the code, you do not check for t, but for non-nil. So, please say
> "non-nil" in the docstring as well.
As stated in the commit message, aligning with org-bibtex-create... ok, let me
update the
doc string of org-bibtex-create as
After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer
syntax highlighted in emacs. They used to be syntax highlighted when I
specified the block's language. Any ideas?
I use Doom, so it might have been a third-party feature.
I know org-mode officially suggests that example
10 matches
Mail list logo
