unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: eliz@gnu.org, storm@cua.dk, nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: (emacs)Antinews
Date: Wed, 25 Jan 2006 18:14:50 -0600 (CST)	[thread overview]
Message-ID: <200601260014.k0Q0Eo019915@raven.dms.auburn.edu> (raw)
In-Reply-To: <jezmljsvvf.fsf@sykes.suse.de> (message from Andreas Schwab on Thu, 26 Jan 2006 00:58:28 +0100)

Andreas Schwab wrote:

   Luc Teirlinck <teirllm@dms.auburn.edu> writes:

   > Its primary purpose is to provide accurate and useful info about
   > differences with earlier Emacs versions.

   That's what NEWS is about.

   Andreas.

The purpose of NEWS is different: it tells a user who starts out using
a new Emacs version what is new in that version.  It also aims to be
rather comprehensive (it is huge).

As I understand it, the purpose of antinews is to point out to a user
of the present version what the main difficulties could be if he has
to use an older version.  (_Having_ to use an older version is very
common for several reasons: you might not be using your own computer
and the Emacs version on that computer may not be the latest version,
or you might have to use some package that does not work with the
latest version, because of backward incompatible changes).

For instance, the current Elisp manual says about naming a keyboard macro:

  If you wish to save a keyboard macro for later use, you can give it a
  name using `C-x C-k n' (`kmacro-name-last-macro').

It is impossible to figure out from NEWS that you have to do
`M-x name-last-kbd-macro' in 21.4 and earlier, because 
`C- h n C-s name-last' fails.

Sincerely,

Luc.

  reply	other threads:[~2006-01-26  0:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-25  0:09 (emacs)Antinews Luc Teirlinck
2006-01-25  1:08 ` (emacs)Antinews Nick Roberts
2006-01-25  2:19   ` (emacs)Antinews Luc Teirlinck
2006-01-25  2:53     ` (emacs)Antinews Nick Roberts
2006-01-25  3:44       ` (emacs)Antinews Luc Teirlinck
2006-01-25  4:36     ` (emacs)Antinews Eli Zaretskii
2006-01-25  8:54       ` (emacs)Antinews Kim F. Storm
2006-01-25 17:52         ` (emacs)Antinews Eli Zaretskii
2006-01-25 19:47           ` (emacs)Antinews Andreas Schwab
2006-01-25 23:38         ` (emacs)Antinews Luc Teirlinck
2006-01-25 23:58           ` (emacs)Antinews Andreas Schwab
2006-01-26  0:14             ` Luc Teirlinck [this message]
2006-01-26  4:31               ` (emacs)Antinews Eli Zaretskii
2006-01-26  1:39           ` (emacs)Antinews Miles Bader
2006-01-26  4:30           ` (emacs)Antinews Eli Zaretskii
2006-01-26  5:13             ` (emacs)Antinews Chong Yidong
2006-01-27 22:32             ` (emacs)Antinews Richard M. Stallman
2006-01-26 17:46           ` (emacs)Antinews Richard M. Stallman
2006-01-26  2:47         ` (emacs)Antinews Richard M. Stallman
2006-01-25 15:45     ` (emacs)Antinews Richard M. Stallman
2006-01-25  2:27   ` (emacs)Antinews Luc Teirlinck
2006-01-25  2:55     ` (emacs)Antinews Nick Roberts

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=200601260014.k0Q0Eo019915@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=storm@cua.dk \
    /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).