Jens Schmidt writes:
> I was trying to decipher and document the acronyms used for the
> let-bindings in that `let*' sexp. I think I got them right but was
> unsure about the "gv". Removed the question mark, let's just assume
> that "gv" means "getter value" and be done with it.
Yeah. I also t
On 2023-08-07 13:53, Ihor Radchenko wrote:
Thanks for reviewing.
- If the comparison value is a plain number, a numerical comparison is
done, and the allowed operators are =<=, ===, =>=, =<==, =>==, and
- =<>=.
+ =<>=. As synonym for the equality operator there is also , as
+ syn
Jens Schmidt writes:
> Documented that in the Org manual, added tests, looks good. Please
> check.
Thanks!
Two minor comments.
> - If the comparison value is a plain number, a numerical comparison is
>done, and the allowed operators are =<=, ===, =>=, =<==, =>==, and
> - =<>=.
> + =<>=.
On 2023-08-06 11:19, Jens Schmidt wrote:
I
will also add tests for matching property names having minuses and then
we can see how it goes.
Went well. With a property name regexp
"\\(?5:[[:alnum:]_-]+\\)"
and the following Org file
--
* H1
On 2023-08-06 09:55, Ihor Radchenko wrote:
But from here it gets more intersting:
- The code uses subre "-" in property names to (supposedly) allow
for inclusion of minus characters in property names, which (probably)
could be confused with term negation.
Not probably. It is know
Jens Schmidt writes:
> - I used "\(?NUM: ... \)" constructs to explicitly number the subres.
>Hope this is OK w.r.t. style and backward-compatibility.
Yes, it is ok.
> - I fixed the operator-matching subre to also include `==', `!=', `/='
>but exclude `<<' and the like which currently g
On 2023-08-02 08:45, Ihor Radchenko wrote:
> `rx' would be great.
> But even adding comments like in your example would be an improvement.
Since the future of this code snippet seems to be uncertain I went for
comments only.
And I thought I was pretty much done when I noticed at least one majo
Jens Schmidt writes:
> On 2023-07-31 08:45, Ihor Radchenko wrote:
>
>> If you are up to a job of adding this to `org-make-tags-matcher' and
>> not breaking things, you can try.
>
> Depends a bit on the required collateral changes: Updating ORG-NEWS and
> doc/org-guide.org should be no problem.
On 2023-07-31 08:45, Ihor Radchenko wrote:
If you are up to a job of adding this to `org-make-tags-matcher' and
not breaking things, you can try.
Depends a bit on the required collateral changes: Updating ORG-NEWS and
doc/org-guide.org should be no problem. Doing a naive grep-based search
I
Jens Schmidt writes:
> The following was initially meant as bug report until I understood that
> it's actually some sort of feature ...
>
> since the absent property "patchday" on the "relax" todo entry is
> defaulted to value zero, obviously.
This is a side effect of handling comparison operato
The following was initially meant as bug report until I understood that
it's actually some sort of feature ...
Consider the following todo list:
todos.org
* TODO relax
* TODO do this
:PROPERTIES:
:patchday: 202302
:END:
* TODO do that
:PROPERTIES:
:pat
11 matches
Mail list logo
