* [2024-07-12 13:23] Ihor Radchenko:> Phil writes:
To tangle to multiple destinations
a logic extension of the existing tangle mechanism.
1) Introduce :tangle-directory parameter that defines
relative directory to be used as tangle target; this
directory, if defined, will be used instea
Hello Sébastien,
Remove the two dots after Review_all and everything will be fine.
#+PROPERTY: Review_ALL ⭐ ⭐⭐ ⭐⭐⭐ ⭐
Best,
Phil
* [2024-07-15 03:18] Sébastien Gendre:
Hello,
After reading the manual about property syntax[1], I want to set the
allowed values for a property at the f
i didn't do reply to all for some reason so sending to list.
idk if useful, but fwiw, for me at least, i think of org's mark ring as
primarily and usually a reliable back button, like a browser's. mainly for
links and link-like navigating actions. especially for use cases like
this: refile goto
Hello,
After reading the manual about property syntax[1], I want to set the
allowed values for a property at the file level.
So, at the beginning of my buffer, I have written this:
#+PROPERTY: Review_ALL: ⭐ ⭐⭐ ⭐⭐⭐ ⭐
But when I try to set the property of an heading, with keyboa
Florian Lindner writes:
>> Use 'time-of-day instead.
>
> Thanks for advise! However, I was unable to get something else but nil
> for time-of-day for these entries:
>
> * TODO dated and timed item
> SCHEDULED: <2024-07-14 So 14:00>
This item will have 'time-of-day property.
> * TODO timed item
Am 14.07.24 um 11:46 schrieb Ihor Radchenko:
Florian Lindner writes:
* TODO dated item
SCHEDULED: <2024-07-04 Do 14:00>
* TODO undated item
which is in org-agenda-files. Using "org-agenda t" and executing "C-x
C-x =" (what-cursor-position) yields "dotime t" for both entries.
I have found no
Ihor Radchenko writes:
> I do not think that we need an appendix - most of the terms are simply
> introduced one by one while reading the manual.
My problem may be in treating the user's manual as a reference manual.
So, if a term is introduced (and explained) in another section(s) that I
didn't
David Masterson writes:
> I'm getting old, but I think I'm seeing it now. I think the word
> "entry" in 10.2 threw me for awhile (entry as in a task hierarchy as
> opposed to a particular attachment). Maybe an Appendix for these generic
> words (entry, ID, header, task, ...) that explains their
Florian Lindner writes:
> * TODO dated item
> SCHEDULED: <2024-07-04 Do 14:00>
> * TODO undated item
>
> which is in org-agenda-files. Using "org-agenda t" and executing "C-x
> C-x =" (what-cursor-position) yields "dotime t" for both entries.
>
> I have found no documentation on the "dotime" pro
On 12/07/2024 23:34, Sébastien Gendre wrote:
Max Nikulin writes:
See specific store link functions, e.g. `org-gnus-store-link'.
Reading the `org-gnus-store-link' function, I see that is set: type,
file, node, link and description.
I see :from :to :subject :message-id :group, :date. Other key
10 matches
Mail list logo
