unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Stefan Kangas <stefan@marxist.se>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, 20403@debbugs.gnu.org
Subject: bug#20403: Format of NEWS (navigating in it)
Date: Thu, 31 Oct 2019 22:56:50 +1300	[thread overview]
Message-ID: <2ecef70596fda1bcaaaa31944a01a39a@webmail.orcon.net.nz> (raw)
In-Reply-To: <87pniex9a4.fsf@joffe.skangas.se>

"Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> writes:
> I know it's all a long tradition, but I'd prefer to have one major
> section per release.

I'd be in favour of that myself (it does seem slightly cleaner), but
I'm also not especially bothered by the current format.


> While re-discovering outline-mode, I also realized that C-c C-f
> [<outline-forward-same-level>] (and C-c C-b) have to be used twice
> to get to the next heading if an ASCII FF (form feed) (plus newline)
> character preceeds the heading.

Note that the form feeds are there so that you can use page-based
commands.  e.g.:

C-x ] (forward-page)
C-x [ (backward-page)
C-x n p (narrow-to-page)

If I'm checking the history of something, I generally grep the NEWS
files, jump to the appropriate hit, and then use C-x [ to check
which specific version of Emacs that entry was for.


The change I'd actually like to see is for NEWS to just be a symlink
to the appropriate NEWS.xx file, which should exist under that name
from the outset of development on version xx.  That way every NEWS.xx
would contain its full history in version-control, rather than just
being a renamed NEWS with maybe a handful of retro-added additions.


-Phil






  reply	other threads:[~2019-10-31  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  6:14 bug#20403: Format of NEWS (navigating in it) Ulrich Windl
2019-09-30  0:24 ` Stefan Kangas
2019-10-30 20:34   ` Stefan Kangas
2019-10-31  9:56     ` Phil Sainty [this message]
2019-10-31 14:43       ` Eli Zaretskii
2019-10-31 16:04         ` Stefan Kangas
2019-10-31 16:11           ` Eli Zaretskii
2019-10-31 19:19         ` Glenn Morris
2019-10-31 20:08           ` Eli Zaretskii
2019-11-01  5:02           ` Stefan Kangas
2019-11-01  6:27             ` Eli Zaretskii
2019-11-11 19:06               ` Stefan Kangas
2019-11-04  7:16         ` bug#20403: Antw: " Ulrich Windl
2019-11-04 16:11           ` Eli Zaretskii

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=2ecef70596fda1bcaaaa31944a01a39a@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=20403@debbugs.gnu.org \
    --cc=Ulrich.Windl@rz.uni-regensburg.de \
    --cc=stefan@marxist.se \
    /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).