Please find attached another clean-up patch that fixes a small number of
typos.
From 2619a525d025a8d4359cff440264c1fd3e9581c8 Mon Sep 17 00:00:00 2001
From: Stefan Kangas
Date: Thu, 16 Sep 2021 21:58:35 +0200
Subject: [PATCH] ; Fix some typos
---
doc/org-manual.org | 4 ++--
etc/ORG-NEWS
Colin Baxter writes:
>> Colin Baxter writes:
>
> > Hello, Today I get a "wrong-number-of-arguments" publish
> > error. This was not present a few weeks ago. It is also not
> > present in Org-version 9.4.4 but does occur in the latest version
> > of org-mode.
>
> > I'd
> Colin Baxter writes:
> Hello, Today I get a "wrong-number-of-arguments" publish
> error. This was not present a few weeks ago. It is also not
> present in Org-version 9.4.4 but does occur in the latest version
> of org-mode.
> I'd appreciate some help in tracking down
Stefan Kangas writes:
> The attached patch cleans up some style errors in docstrings and
> comments that were found by checkdoc.
Thanks Stefan!
Your patch has been applied.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
> I understand the problem, but the solution should not be: "let's pretend
> export does not exist".
>From my perspective any org object that is not in a section that
allows org objects could in principle be parsed as such, but it would
not be in the core of the grammar, and it also would have to
> Attached is a patch with improvement to documentation regarding regular
> expressions.
Hi, how do I get the patch approved/committed to org?
--
Daniel Fleischer
The attached patch cleans up some style errors in docstrings and
comments that were found by checkdoc.
From 655c099b10d542207493580115789f3cbeb8b064 Mon Sep 17 00:00:00 2001
From: Stefan Kangas
Date: Thu, 16 Sep 2021 12:32:43 +0200
Subject: [PATCH] ; Various minor docfixes found by checkdoc
---
Hi Tom,
> You make sense. What you propose to substitute is easier to understand and
> concise:
>
> When FULL is non-nil but not t, skip planning information,
> properties, clocking lines and logbook drawers.
Thank you for the report and the confirmation!
I just committed
