[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mark-word
From: |
Stephen J. Turnbull |
Subject: |
Re: mark-word |
Date: |
Thu, 15 Nov 2007 01:35:28 +0900 |
Leo writes:
> > `mark-word' itself should remain compatible with `kill-word' and
> > `mark-sexp'.
>
> Why?
Erm, backward compatibility is a good thing. "Why *not* preserve it?"
is the right question, and it better have a good answer.
More specifically, mostly because it's a pain in the neck to deal with
functions whose specifications change for the convenience of the UI,
and because it's an offense against the general regularity of names
with no good reason. True, symbol names are somewhat scarce, but I
rather doubt anyone in their right mind would give `mark-entire-word'
anything but the proposed semantics. It should be easy for people who
actually prefer that behavior (if any, I admit) to revert. And some
of us support Emacsen that won't have the change, often simultaneously
with the latest code. XEmacs does so as project policy, and many
organizational environments will do so too.
- mark-word, Andreas Röhler, 2007/11/14
- mark-word, Stephen J. Turnbull, 2007/11/14
- Re: mark-word, Leo, 2007/11/14
- Re: mark-word,
Stephen J. Turnbull <=
- Re: mark-word, Richard Stallman, 2007/11/14
- Re: mark-word, David Kastrup, 2007/11/14
- Re: mark-word, Andreas Röhler, 2007/11/14
- Re: mark-word, Stephen J. Turnbull, 2007/11/14
- Re: mark-word, Lennart Borgman (gmail), 2007/11/14
- Re: mark-word, Miles Bader, 2007/11/14
- Re: mark-word, Lennart Borgman (gmail), 2007/11/15
- Re: mark-word, Miles Bader, 2007/11/15
- Re: mark-word, Lennart Borgman (gmail), 2007/11/15
- Re: mark-word, Andreas Röhler, 2007/11/15