unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: emacs-devel@gnu.org
Subject: Re: Date in emacs man-file
Date: Wed, 16 Sep 2020 12:24:00 +0100	[thread overview]
Message-ID: <87zh5qdkxb.fsf@yandex.com> (raw)
In-Reply-To: CADwFkmkP3TcwZpoZQg0L5+jwUXbKHgejXMZ+xe6fBtqw-fYhzg@mail.gmail.com

>>>>> Stefan Kangas <stefankangas@gmail.com> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> I notice the second line of the file man/emacs.1.in has "2007
    >> April 13". Therefore "man emacs <RET>" will give this date at the
    >> foot of the manual, along side the emacs version (27.1 in the
    >> case of the latest release). Should not this date be amended to
    >> something more recent?

    > "man 7 man-pages" says:

    >        date The date of the last nontrivial change that was made
    > to the man page.  (Within the man-pages project, the necessary
    > updates to these timestamps are handled automatically by scripts,
    > so there is no need to manually update them as part of a patch.)
    > Dates should be written in the form YYYY-MM-DD.

    > Perhaps we could add a local timestamp variable to update it
    > automatically?  It would catch even insignificant changes, but it
    > would be up to the committer to update the timestamp or not.

Curiously, there's a recent reddit enquiry on just this very issue.

https://www.reddit.com/r/emacs/comments/hszg0a/hook_for_updating_manpage_timestamp_in_line_1/

The proposed lisp defun works on the first line only of the nroff file,
for a different date format - but it does work.

Best wishes,

Colin Baxter.




  reply	other threads:[~2020-09-16 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 10:50 Date in emacs man-file Colin Baxter
2020-09-13 12:12 ` Stefan Kangas
2020-09-16 11:24   ` Colin Baxter [this message]
2020-10-11 11:49   ` Stefan Kangas
2020-10-11 15:14     ` Colin Baxter
2020-10-12 19:05       ` Stefan Kangas

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=87zh5qdkxb.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@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).