unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Cc: Hrvoje Niksic <hniksic@xemacs.org>
Subject: RE: Saving minibuffer history
Date: Sun, 16 Oct 2005 10:58:32 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICMEHICNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87u0fhsauh.fsf-monnier+emacs@gnu.org>

    >     Uh, Emacs 20?  Why would one need to be compatible with that?
    > Many, many people do use Emacs 20, for a variety of reasons.

    Please remove emacs-devel from the Cc when discussing such issues.

Why? This was the gist of my reply:

 If nothing is gained by breaking backward compatibility, why break it?

Is that not worthy of consideration as a design/development consideration
for Emacs?

I'm not sure what the "such issues" are that you object to discussing. I did
not discuss Emacs 20 and its relative virtues or disadvantages. My point was
only the one quoted here - a suggestion of consideration, for future
development, of not breaking old code gratuitously - that is, not breaking
backward compatibility unless there is some advantage in doing so. The
advantage could be as slight as more readable code - I wasn't asking for
more than opting for compatibility when things are _equal_.

I didn't suggest testing new code with Emacs 20, or placing the burden of
showing zero cost for compatibility on Emacs developers, or anything of the
sort. I simply raised the design/development question, "_if_ other things
are equal, why not choose the backward-compatible solution?"

Even if there might be disagreement over the suggestion, is this not a
proper place for its discussion?

  reply	other threads:[~2005-10-16 17:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 13:40 Saving minibuffer history Hrvoje Niksic
2005-10-14 23:29 ` Hrvoje Niksic
2005-10-14 23:44   ` Drew Adams
2005-10-15 16:13 ` Richard M. Stallman
2005-10-15 22:28   ` Hrvoje Niksic
2005-10-15 23:29     ` Drew Adams
2005-10-16  7:28       ` David Kastrup
2005-10-16 15:49         ` Drew Adams
2005-10-16 16:16           ` Stefan Monnier
2005-10-16 17:58             ` Drew Adams [this message]
2005-10-16 21:52               ` David Kastrup
2005-10-17  1:10               ` Stefan Monnier
2005-10-17  8:25                 ` Hrvoje Niksic
2005-10-16 12:32       ` Hrvoje Niksic
2005-10-16 13:02       ` Stefan Monnier
2005-10-18 14:41         ` Hrvoje Niksic
2005-10-24 16:55           ` Drew Adams
2005-10-24 17:02             ` Drew Adams
2005-10-24 17:48               ` Stefan Monnier
2005-10-16 15:39     ` Stefan Monnier
2005-10-18 14:27       ` Hrvoje Niksic
2005-10-18 16:12         ` Stefan Monnier
2005-10-18 23:34           ` Hrvoje Niksic
2005-10-19 18:51             ` Stefan Monnier
2005-10-20  9:09               ` Hrvoje Niksic
2005-10-20  9:12                 ` Hrvoje Niksic
2005-10-20 16:25                   ` Stefan Monnier
2005-10-20 21:04                     ` Hrvoje Niksic
2005-10-24 16:02       ` Hrvoje Niksic
2005-10-24 17:16         ` Stefan Monnier
2005-10-25  9:04           ` Hrvoje Niksic
2005-10-26 16:46             ` Richard M. Stallman
2005-10-24 22:24         ` Stefan Monnier
2005-10-25  4:37           ` Stefan Monnier
2005-10-25  9:46             ` Hrvoje Niksic
2005-10-25 14:51               ` Stefan Monnier
2005-10-25 21:04             ` Hrvoje Niksic
2005-11-01  6:12               ` Stefan Monnier
2005-10-25  9:20           ` Hrvoje Niksic
2005-10-25 12:34             ` Miles Bader
2005-10-25 13:58               ` Hrvoje Niksic
2005-10-25 14:00                 ` Miles Bader
2005-10-25 14:39             ` Stefan Monnier
2005-10-25 19:07               ` Hrvoje Niksic
2005-10-25 15:58         ` Richard M. Stallman
2005-10-16 17:36     ` Richard M. Stallman
2005-10-16 20:18       ` Hrvoje Niksic
2005-10-16 21:55       ` David Kastrup

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=DNEMKBNJBGPAOPIJOOICMEHICNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=hniksic@xemacs.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).