If I look at all my TODOs (org-todo-list) and filter to WAITING (4 r) then all
the tasks in this view are shown in the order they appear in the files where
the tasks are listed. Is there a way to sort them from old to new (or new to
old) so I can see which ones have been in that status for the
Dear org-mode developers, when shutting
down Emacs with save-buffers-kill-emacs,
I sometimes see shortly as the last
thing in the echo area "Deleting bad
index entry." And before some message
about wrong type of sth. I cannot read so
fast.
Is there anything I should do about
that?
Regards, Greg
Ouch, that part of the docstring totally slipped my eye.
The situation is a bit more complex than I imagined and am not
experienced enough to have a strong opinion on the matter. If things
are to stay as they are right now, I guess emphasizing even more in the
docstring that this function may hav
Antonio Romano writes:
> What I did was simply parse out a buffer, change all headlines's TODO
> keyword in its AST to "DONE", interpret the resulting AST and finally
> print out the resulting document to a new buffer. The issue I had
> encountered was that an headline like "* TODO Hello" would w
Pedro writes:
> How did you know that, should that be mentioned in the corresponding
> section? (I could not find another one) [1] [2].
It is written at the bottom of [2]:
When exporting subtrees, special node properties can override the
above keywords. These properties have an ‘EXPORT_’ p
Ihor Radchenko writes:
> ray writes:
>
>> 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
>>
>> ...
>
> Thanks for reporting, but may you please clarify what is the warning text?
More information ha
Hey!
And this is trivial, but it took me a while to figure it out
Of course, if you want to use more than one EXPORT_LATEX_HEADER for that
subtree export, you need to use multi-value property [0]:
:PROPERTIES:
:EXPORT_LATEX_HEADER: \usepackage{bookmark}
:EXPORT_LATEX_HEADER+: \usepackage{nopa
Hi Pedro,
You were right!
In my success of starting to have more diverse number of latex exports
in my yearly journal, it was being polluted because the global
~#+LATEX_HEADER~ stuff [1]
it went unnoticed because it was in lowcase and I was only searching for
the uppercase, these were the a
Emacs freezes upon opening the hours,org file.
This version comes up with a parser error, however this file has been
used and worked on at 7 july 2024. This file has been used after the
holidays up to 26 august 2024. Then at 28 august the file could not be
opened anymore. This was probably after a
Hi,
On a clocktable with hierarchy (see attached file
clocktable-link-bug.org), when ~:link t~ is used, it does not look
visually good; that was not an issue with the previous versions of orgmode
Find attached screenshot 2024-09-01_23-05_clocktable-detail.png, that
shows the inconsistency in
At some point in the last few months, org mode stopped fontifying my
latex export blocks. However, an older version of emacs on my computer
still does fontify.
(The difference is seen even opening emacs with the -q flag)
It seems that there was a change to the function
org-fontify-meta-lines-and-bl
Hi Rudy,
You nailed it!! Using property EXPORT_LATEX_HEADER exactly solves my
problem, thank you very much. For completeness, I will re-attach the
file with the solution
How did you know that, should that be mentioned in the corresponding
section? (I could not find another one) [1] [2]. Mayb
12 matches
Mail list logo
