GNU bug report logs - #26335
time-stamp-pattern examples unclear

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26335 in the body.
You can then email your comments to 26335 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <bug-gnu-emacs <at> gnu.org>
Subject: time-stamp-pattern examples unclear
Date: Sun, 02 Apr 2017 06:30:37 +0800

time-stamp-pattern is a variable defined in ‘time-stamp.el’.
...
This string has four parts, each of which is optional.
...
Examples:
"-10/"
"-9/^Last modified: %%$"
"@set Time-stamp: %:b %:d, %:y$"
"newcommand{\\\\timestamp}{%%}"

Please say
Examples:

This only has the first part:
"-10/"

This has the first part, followed by the second and maybe? the third part:
"-9/^Last modified: %%$"

This has the second part followed by the ??th part:
"@set Time-stamp: %:b %:d, %:y$"

This has the ??nd part followed by the ??th part:
"newcommand{\\\\timestamp}{%%}"

Message #8 received at 26335 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 26335 <at> debbugs.gnu.org
Subject: Re: bug#26335: time-stamp-pattern examples unclear
Date: Fri, 26 Jul 2019 12:40:49 +0200

積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> time-stamp-pattern is a variable defined in ‘time-stamp.el’.
> ...
> This string has four parts, each of which is optional.
> ...
> Examples:
> "-10/"
> "-9/^Last modified: %%$"
> "@set Time-stamp: %:b %:d, %:y$"
> "newcommand{\\\\timestamp}{%%}"
>
> Please say
> Examples:
>
> This only has the first part:
> "-10/"
>
> This has the first part, followed by the second and maybe? the third part:
> "-9/^Last modified: %%$"
>
> This has the second part followed by the ??th part:
> "@set Time-stamp: %:b %:d, %:y$"
>
> This has the ??nd part followed by the ??th part:
> "newcommand{\\\\timestamp}{%%}"

Well, all that stuff is pretty much incomprehensible, so I went through
the examples using the code like this:

(progn
  (string-match "\\`\\(\\(-?[0-9]+\\)/\\)?\\([^%]+\\)?\\(\\(%[-.,:@+_ #^()0-9]*[A-Za-z%][^%]*\\)*%[-.,:@+_ #^()0-9]*[A-Za-z%]\\)?\\([^%]+\\)?\\'"
		"newcommand{\\\\\\\\timestamp}{%%}")
  (match-data))
=> (0 29 nil nil nil nil 0 26 26 28 nil nil 28 29)

and matched up to this code fragment:

	  (and (match-beginning 2)
	       (setq line-limit
		     (string-to-number (match-string 2 time-stamp-pattern))))
	  (and (match-beginning 3)
	       (setq ts-start (match-string 3 time-stamp-pattern)))
	  (and (match-beginning 4)
	       (not (string-equal (match-string 4 time-stamp-pattern) "%%"))
	       (setq ts-format (match-string 4 time-stamp-pattern)))
	  (and (match-beginning 6)
	       (setq ts-end (match-string 6 time-stamp-pattern)))))

and added the explanations about what's set.  It was probably not worth
it, though.

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.