Hi Ihor and Ignacio,
sorry for the late answer.
Ihor Radchenko writes:
> Bastien, could you kindly check if Ignacio Casso
> has FSF assignment and update contributors
> page accordingly?
I confirm Ignacio has FSF assignment (since 2022-03-28) and I updated
the Org contributors page.
Best,
Ignacio Casso writes:
>> I have added TINYCHANGE cookie as you don't appear to have FSF copyright
>
> I should have it, I did the paperwork for commit 2b564f504b in
> Emacs. Maybe I used a different email? Or maybe the problem is that now
> that I see it I don't have my full name configured in
> Thanks!
Thank you too!
> I have added TINYCHANGE cookie as you don't appear to have FSF copyright
I should have it, I did the paperwork for commit 2b564f504b in
Emacs. Maybe I used a different email? Or maybe the problem is that now
that I see it I don't have my full name configured in git.
Ignacio Casso writes:
> Done. I attach the patch:
Thanks!
Applied onto main as a3dd2 with minor amendments.
I have added TINYCHANGE cookie as you don't appear to have FSF copyright
assignment and capitalised "match" in the commit summary.
Best,
Ihor
> From
Ihor Radchenko writes:
> Ignacio Casso writes:
>
>>> Sounds reasonable. Could you prepare a patch?
>>> COMMENT should be inside a shy group and note that there might be an
>>> arbitrary number of space after COMMENT string.
>>
>> Here it is.
>
> Thanks! Could you also update the
Ignacio Casso writes:
>> Sounds reasonable. Could you prepare a patch?
>> COMMENT should be inside a shy group and note that there might be an
>> arbitrary number of space after COMMENT string.
>
> Here it is.
Thanks! Could you also update the org-complex-heading-regexp-format
docstring and
> Sounds reasonable. Could you prepare a patch?
> COMMENT should be inside a shy group and note that there might be an
> arbitrary number of space after COMMENT string.
Here it is.
>From 54cd366c97bd64c226cc6fc79e125ee9f026ff66 Mon Sep 17 00:00:00 2001
From: Ignacio
Date: Fri, 6 May 2022
Ignacio Casso writes:
>> Note that org-complex-heading-regexp-format does consider statistics
>> cookies, but only at the beginning/end of the headline title.
>> Unfortunately, it is impossible to provide generic printf format to
>> match a headline title with arbitrary statistics cookies
This topic was brought up again in
https://lists.gnu.org/archive/html/emacs-orgmode/2022-05/msg00058.html,
I continue the discussion here:
>> Still, I think it might be interesting to compare this topic with the
>> one I linked in my reply,
>>
Hello,
I think `org-complex-heading-regexp' and
`org-complex-heading-regexp-format' should consider COMMENT keywords, as
they do with TODO keywords, priorities, and tags.
Firstly, with things as they are, different methods for accessing the
headline text are inconsistent. For example, for the
10 matches
Mail list logo
