unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: Replacing linum-mode by nlinum-mode
Date: Tue, 13 Aug 2013 19:50:35 -0700 (PDT)	[thread overview]
Message-ID: <f92c7e5a-949b-4dff-b7f0-0061a153cd79@default> (raw)
In-Reply-To: <jwvbo51uhkq.fsf-monnier+emacs@gnu.org>

> > If you want to "maximize backward compatibility", why rename anything?
> >
> > Why not just use nlinum functions wherever you want, in place of linum
> > functions?  Why gratuitously change user code at the same time?
> >
> > (To be clear, I don't knowingly use either, and I have no code that
> > does.  My question has nothing to do with my personal use of Emacs.)
> 
> Because the main reason to install nlinum-mode is to fix the bugs of
> linum-mode, so users of linum-mode will only benefit from those
> bug-fixes if they get transparently "upgraded" to nlinum-mode.

They will benefit if they are "upgraded" to nlinum-mode, whether
that happens "transparently" or they do it intentionally & knowingly.

Still sounds more user-friendly to me to (a) fix all Emacs source code
to use the nlinum functions and (b) encourage 3rd-party code to move
to using those functions also.

Changing the names is not so nice.  3rd-party programmers will not
know without digging a bit that completely different code is now being
run under the same names (even the library name is taken over).

Not a big deal, but not super considerate of users.  And you did say
you wanted to "maximize backward compatibility".



  reply	other threads:[~2013-08-14  2:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  1:02 Replacing linum-mode by nlinum-mode Stefan Monnier
2013-08-14  1:53 ` Drew Adams
2013-08-14  2:35   ` Stefan Monnier
2013-08-14  2:50     ` Drew Adams [this message]
2013-08-14 12:25     ` Juanma Barranquero
2013-08-14 15:40       ` Stefan Monnier
2013-08-14 15:41         ` Juanma Barranquero
2013-08-14 16:00           ` Stefan Monnier
2013-08-14 16:03             ` Juanma Barranquero
2013-08-19  2:18               ` Stefan Monnier

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=f92c7e5a-949b-4dff-b7f0-0061a153cd79@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).