Timothy writes:
> Thanks for bumping your patch, unfortunately many of us (people who can push
> to
> Org) seem to be stretched a bit thin as of late. I’ve just gone over it, it
> reads well IMO and I think looking at the non-trivial changes in your patch
> it’s
> possible to charitably interpr
Hi Daniel,
Thanks for bumping your patch, unfortunately many of us (people who can push to
Org) seem to be stretched a bit thin as of late. I’ve just gone over it, it
reads well IMO and I think looking at the non-trivial changes in your patch it’s
possible to charitably interpret this as <=15 non-
> Attached is a patch with improvement to documentation regarding regular
> expressions.
Hi, how do I get the patch approved/committed to org?
--
Daniel Fleischer
Attached is a patch with improvement to documentation regarding regular
expressions.
Best,
Daniel Fleischer
>From d3d1dcbc5f62ea111e7bcd1741114cae6b1280c5 Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Tue, 31 Aug 2021 20:01:47 +0300
Subject: [PATCH] org-manual: added section about regul
Timothy [2021-09-01 Wed 18:28] wrote:
> Hi Daniel,
>
> Thanks Daniel, I’ve just had a quick read and it looks good to me. If anyone
> else has comments this would be a great time to jump in :)
>
> I haven’t seen `' links before, it seems like there’s one
> other in the manual. Do you know if they
Hi Daniel,
Thanks Daniel, I’ve just had a quick read and it looks good to me. If anyone
else has comments this would be a great time to jump in :)
I haven’t seen `[[info:elisp::page]]' links before, it seems like there’s one
other in the manual. Do you know if they work well with the exported for
Hi Timothy,
Attached is my patch.
Best,
*Daniel Fleischer*
>From 05602a3eb453672893e7e92cc0384e1b6b7784aa Mon Sep 17 00:00:00 2001
From: Daniel Fleischer
Date: Tue, 31 Aug 2021 20:01:47 +0300
Subject: [PATCH] org-manual: added section about regular expressions
Telling users it's based on Elis
Timothy [2021-08-31 Tue 19:27] wrote:
> Hi Cassio,
>
>> Ah! Can’t believe I didn’t try that. Well, at least the docs can
>> benefit from my confusion.
>
> Would you be interested in making a patch for the docs, or would you rather
> leave that to someone else?
Actually I want to do that. I had a
Hi Daniel,
>> Would you be interested in making a patch for the docs, or would you rather
>> leave that to someone else?
>
> Actually I want to do that. I had an idea to add a node (in org)
> “reminding” people that all mentions of regex refer to elisp regex,
> which could be different than what p
Hey, great! I was going to patch the example (was just reading the commit
guidelines) but I'll leave it in your hands then. Thanks!
Best,
On Tue, Aug 31, 2021 at 9:33 AM Daniel Fleischer wrote:
>
> Timothy [2021-08-31 Tue 19:27] wrote:
>
> > Hi Cassio,
> >
> >> Ah! Can’t believe I didn’t try th
Hi Cassio,
> Ah! Can’t believe I didn’t try that. Well, at least the docs can
> benefit from my confusion.
Would you be interested in making a patch for the docs, or would you rather
leave that to someone else?
All the best,
Timothy
Ah! Can't believe I didn't try that. Well, at least the docs can
benefit from my confusion.
Thanks,
On Wed, Aug 25, 2021 at 6:05 PM Daniel Fleischer wrote:
>
> On Wed, Aug 25 2021, Cassio Koshikumo wrote:
> > Hello all,
> >
> > I think there's a bug with `org-make-tags-matcher' when creating a s
On Wed, Aug 25 2021, Cassio Koshikumo wrote:
> Hello all,
>
> I think there's a bug with `org-make-tags-matcher' when creating a sparse tree
> using property matching with regular expressions and "or" terms. Take the
> example given in the manual:
>
> +work-boss+PRIORITY="A"+Coffee="unlimited"+Ef
Hello all,
I think there's a bug with `org-make-tags-matcher' when creating a sparse tree
using property matching with regular expressions and "or" terms. Take the
example given in the manual:
+work-boss+PRIORITY="A"+Coffee="unlimited"+Effort<2
+With={Sarah|Denny}+SCHEDULED>="<2008-10-11
14 matches
Mail list logo
