From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: 20403@debbugs.gnu.org
Subject: bug#20403: Format of NEWS (navigating in it)
Date: Wed, 22 Apr 2015 08:14:31 +0200 [thread overview]
Message-ID: <55375867020000A100019F48@gwsmtp1.uni-regensburg.de> (raw)
Hi!
As I was not running the latest version of Emacs, I started to read the NEWS file backwards (maybe life is just boring otherwise), beginning at the Emacs version I had before.
(while doing that the ghost of RMS appeared and asked: "Why don't you run the latest version when it's free?" ;-)
OK, serious again: I realized that when reading backwards it's rather hard to find out when you are done, because even that it's outline mode there is NOT ONE section per Emacs release (here 24.4) (with sub-sections), but multiple. To be concrete, the lop-level headings (when reading backwards) are:
* Changes in Emacs 24.4 on Non-Free Operating Systems
* Lisp Changes in Emacs 24.4
* Incompatible Lisp Changes in Emacs 24.4
* New Modes and Packages in Emacs 24.4
* Changes in Specialized Modes and Packages in Emacs 24.4
* Editing Changes in Emacs 24.4
* Changes in Emacs 24.4
(here I thought I'm done)
* Startup Changes in Emacs 24.4
* Installation Changes in Emacs 24.4
I know it's all a long tradition, but I'd prefer to have one major section per release. 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.
Is this the way it should be?
Regards,
Ulrich
next reply other threads:[~2015-04-22 6:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 6:14 Ulrich Windl [this message]
2019-09-30 0:24 ` bug#20403: Format of NEWS (navigating in it) Stefan Kangas
2019-10-30 20:34 ` Stefan Kangas
2019-10-31 9:56 ` Phil Sainty
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=55375867020000A100019F48@gwsmtp1.uni-regensburg.de \
--to=ulrich.windl@rz.uni-regensburg.de \
--cc=20403@debbugs.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).