all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Proulx <bob@proulx.com>
To: help-gnu-emacs@gnu.org
Subject: Re: I wish list-buffers used my current window when it listed my buffers
Date: Wed, 21 Aug 2013 16:55:32 -0600	[thread overview]
Message-ID: <20130821225532.GA5534@hysteria.proulx.com> (raw)
In-Reply-To: <9b7d2080-ca36-4a37-98bd-12d9a337c048@googlegroups.com>

Rustom Mody wrote:
> :-) I remember ducking the debris from the explosions around
> visual-line-mode :-)

I hate visual line mode.  I find it very frustrating to use.  I always
turn it off.  I can see where some people might want it.  But at the
same time since I mostly deal with line and column oriented editing I
find it really terrible and frustrating.

> - A comprehensive list of changes is drawn up without scrimping on
> - 'incompatible' including terminology (window/frame vs pane/window
> - etc)

I don't actually care as much about how it is documented.  Names of
things and so forth.  I would be okay with various documented names.
It is hard to change something that is documented one way for 30 years
in many places to something incompatibly different.  I know that the
documentation was the original topic point and just saying I don't
actually feel as strongly about it.  It is the other topic drift that
I feel much more concerned about.

> - 24 is declared as stable and supported for the next 7 years, ie
> - minor bugs will be fixed, major functionality will not be added

And if someone were to suggest the same thing of emacs 23?  Or 22?  Or
21?  Would you feel the same thing then?  Because two years from now
when emacs 27 is out (intentional exaggeration) I am sure people will
say that emacs 24 is so old.  The newest 27 is the only thing to use.
Emacs 24 is new now and everyone claims it is awesome.  But I
guarentee you that in two years the new Emacs XY.Z will heralded as
awesome and Emacs 24 will be disparaged as being terrible.  It is all
a matter of perspective.

> Personally it does not matter too much to me whether I press C-x or
> C-w to 'cut' but it matters a great deal to my students/their
> employers etc, so that more and more I am finding emacs a
> hard-sell. Hopefully you will consider that there are a
> thousand-fold guys like me 'at the fringes' who would give great
> deal to have emacs a little more mainstream/less weird

But think about those of us to whom it matters in the other direction.
I have been pressing C-w to cut for many years.  And C-x for extended
commands just makes sense.  You are claiming that it is holding it
back because new users don't want to use it.  But previous users of it
will want that model of operation and destroying it for them is just
as bad in reverse.  The model of operation of the editor is a major
thing.  Changing the operating model is so big that it really is a
dividing line between one editor and another.  If Emacs changes into
Word then it won't be Emacs anymore but will be a different editor.

This is the classic problem.  "I love you.  You are perfect.  Now
change."  Grr...  Instead if you want an editor with a different
operating model then I am all for it!  I think you should create an
editor with this different operating model.  Go for it!  It could be
very popular and very mainstream.  That would be awesome!  You would
like it.  I am sure that a very large number of people would like it.
And best of all it wouldn't hurt people who want the Emacs operating
model.  Please don't destroy one tool in order to convert it into
another different tool.

You can't please everyone all of the time.  Especially not with the
same tools.  It is okay to have a choice of different tools.  Then
people can use the one that fits them the best.

Bob



  reply	other threads:[~2013-08-21 22:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15  2:02 I wish list-buffers used my current window when it listed my buffers Jay Cotton
2013-08-15  4:56 ` Bob Proulx
     [not found] ` <mailman.16.1376542594.10748.help-gnu-emacs@gnu.org>
2013-08-15 12:45   ` Dan Espen
2013-08-15 23:23     ` Jay Cotton
2013-08-16 13:33       ` Michael Heerdegen
2013-08-16 13:33       ` Michael Heerdegen
2013-08-16 22:12         ` Jay Cotton
2013-08-16 23:24           ` Michael Heerdegen
     [not found]       ` <mailman.163.1376660121.10748.help-gnu-emacs@gnu.org>
2013-08-16 14:03         ` Dan Espen
2013-08-16 22:33           ` Jay Cotton
2013-08-16 22:51             ` Bob Proulx
2013-08-16 23:38               ` Jay Cotton
2013-08-20 23:07                 ` Stefan Monnier
     [not found]                 ` <mailman.447.1377040083.10748.help-gnu-emacs@gnu.org>
2013-08-21  4:51                   ` Rustom Mody
2013-08-21 22:55                     ` Bob Proulx [this message]
     [not found]                     ` <mailman.532.1377125749.10748.help-gnu-emacs@gnu.org>
2013-08-22  4:44                       ` Rustom Mody
2013-08-16 23:08             ` Michael Heerdegen
2013-08-16 23:44               ` Jay Cotton
2013-08-16 23:51               ` Jay Cotton
     [not found]             ` <mailman.210.1376693505.10748.help-gnu-emacs@gnu.org>
2013-08-16 23:14               ` Dan Espen
2013-08-19  3:41 ` Samuel Wales
     [not found] <mailman.11.1376532793.10748.help-gnu-emacs@gnu.org>
2013-08-15  3:42 ` Rustom Mody
2013-08-15  4:54   ` Eric Abrahamsen
2013-08-15  7:31     ` Thorsten Jolitz
2013-08-15 12:32     ` Michael Heerdegen
2013-08-15 12:59       ` Eric Abrahamsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130821225532.GA5534@hysteria.proulx.com \
    --to=bob@proulx.com \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.