Ignacio Casso writes:
> In Emacs 27.2, with an up to date version of org from ELPA (9.5.2),
> org-agenda considers timestamps that appear in property drawers, so the
> entry below appears in the daily agenda view.
>
> * Heading
> :PROPERTIES:
> :timestamp: <2022-03-12 sáb>
> :END:
>
> Howev
sso
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Agenda no longer works for timestamps inside properties
drawer [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]
Ignacio Casso writes:
> In Emacs 27.2, with an up to date version of org from ELPA (9.5.2),
> org-agenda
>> What you see in the new Org version is not a bug. Property values are
>> treated as plain text by Org.
>>
>> I was unable to find a place in manual describing that timestamps cannot
>> be placed inside property values:
>> I personally see allowing timestamps (and links) inside property values
this is merely intuition, but i can
- understand why planning line tses should not be matched in various
places; they are closely tied to real org entries
- not quite grasp why bare active and inactive tses should not be
matched by ts agenda almost anywhere including blocks. perhaps the
idea is t
March 21, 2022 7:21 PM
To: t...@tomdavey.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Agenda no longer works for timestamps inside properties
drawer [9.5.2 (release_9.5.2-24-g668205 @
/home/ignacio/repos/emacs/lisp/org/)]
>> What you see in the new Org version is not a bug. Property va
Ignacio Casso writes:
>>> What you see in the new Org version is not a bug. Property values are
>>> treated as plain text by Org.
>
> I think that even if timestamps were never intended to be used inside
> property drawers before, the fact that it worked for a long time and
> nothing in the docum
Samuel Wales writes:
> - not quite grasp why bare active and inactive tses should not be
> matched by ts agenda almost anywhere including blocks. perhaps the
> idea is that you might wnt to store lots of data with tses and they
> would be too much clutter?
See
https://orgmode.org/list/202201011
Samuel Wales writes:
> so i guess i am interested in the rationale. example of ts [and text]
> search being useful might be an example or ledger block that contains
> ledger source, or something like that. i can get why bare ts not
> being matched inside links might be useful.
>
> otoh i can ge
Ihor Radchenko writes:
> Samuel Wales writes:
>
>> so i guess i am interested in the rationale. example of ts [and text]
>> search being useful might be an example or ledger block that contains
>> ledger source, or something like that. i can get why bare ts not
>> being matched inside links
On 3/22/22, Ihor Radchenko wrote:
> lax - agenda may match anything date-looking (with or without brackets).
> A specialized regex agenda matcher with regex constructed using current
> agenda date.
>
> Maybe we can introduce a new agenda view? Or maybe a special agenda
> mode, similar to org-agend
Tim Cross writes:
> Perhaps I simply don't understand, but I fail to see the need for adding
> such functionality. Org files are plain text and you can just use the
> build-in or any of the add-on search tools to search for anything,
> including timestamps or things which may look like timestamps
Samuel Wales writes:
> your idea of expanding to other date-like things is an interesting
> idea, and so is making an analogy with log mode.
>
> another possibility is to satisfy the preferences users have expressed
> [and those with n>1 needs] using a single variable that contains the
> contexts
* x2
> Could you elaborate? Maybe provide an example.
idk if this answers your q or not.
it rambles.
for context some goals include orthogonality, satisfying
strong differing views/needs with little complexity, and
having simple rules or transparency for knowing behavior
e.g. what shows up i
13 matches
Mail list logo
