unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 10323@debbugs.gnu.org
Subject: bug#10323: 24.0.92; docstring diary-date-forms
Date: Wed, 02 Jun 2021 09:26:37 +0200	[thread overview]
Message-ID: <87a6o87mmq.fsf@gnus.org> (raw)
In-Reply-To: <87mxapsbhd.fsf@niu.edu> (Roland Winkler's message of "Sun, 18 Dec 2011 17:31:42 -0600")

"Roland Winkler" <winkler@gnu.org> writes:

> Maybe this is too pedantic: If one tries to separate a diary entry
> into the date and the text part, the question comes up: what about
> the separator (usually some whitespace character(s)) between the
> date and the text part? The docstring of diary-date-forms says
>
>   The patterns on the list must be MUTUALLY EXCLUSIVE and should not match
>   any portion of the diary entry itself, just the date component.
>
> Originally I thought this would exclude the separator from the date
> component (so that I had to deal with it myself). But the patterns
> are designed the other way round. For the regexp matcher the
> separator is an important part of the date component. So I suggest
> to modify the docstring of diary-date-forms to say something like
>
>   The patterns on the list must be MUTUALLY EXCLUSIVE and should not match
>   any portion of the diary entry itself, just the date component.
>   Here the first character following the date itself is considered part of
>   the date.

(I'm going through old bug reports that unfortunately got no response at
the time.)

This was nine years ago, but the doc string is still the same here.
And...  I'm not quite sure I understand either the current doc string or
the proposed enhancement, really.  :-)

> Actually, this is not completely true either, and it becomes relevant if
> one wants to indent the diary entries for which the `backup' mechanism
> of diary-european-date-forms applies.  If one has the diary entries
>
> 18/12/2011$  foo bar
> 18/12/2011   foo baz
> 18 December  foo bar
>
> the first two entries are indented as one might expect it; yet the third
> one is not indented (i.e., with `backup' all whitespace characters 
> following immediately the date become part of the date)

Perhaps something from this discussion of the problem should be added to
the doc string?  If so, please do go ahead and modify it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-06-02  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 23:31 bug#10323: 24.0.92; docstring diary-date-forms Roland Winkler
     [not found] ` <handler.10323.B.13242512295184.ack@debbugs.gnu.org>
2011-12-19  8:02   ` Roland Winkler
2021-06-02  7:26 ` Lars Ingebrigtsen [this message]
2021-06-08 22:44   ` Roland Winkler
2021-06-09 10:11     ` Lars Ingebrigtsen
2021-06-09 23:01     ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6o87mmq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10323@debbugs.gnu.org \
    --cc=winkler@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).