unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Miles Bader'" <miles@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: display-buffer cleverness - how to tame?
Date: Mon, 4 May 2009 08:49:07 -0700	[thread overview]
Message-ID: <000001c9cccf$dc734c10$c2b22382@us.oracle.com> (raw)
In-Reply-To: <87ws8wkizo.fsf@catnip.gol.com>

> > It's a joke, right?  Emacs adding DWIM now means that if 
> > you want the simple, straightforward behavior of old you
> > need to write it yourself?
> 
> If almost nobody actually does, then that's not a problem, right?

That's sorry logic. The fact (unproven, BTW) that few people will actually go to
that trouble is no proof that almost nobody would appreciate such a result.

The fact that few people actually build an energy-efficient car themselves from
scratch is hardly proof that no one would appreciate such a car.

If the new `display-buffer' approach is so complex that just describing a simple
way to get back the old behavior is too difficult (even for the implementor!),
then, yes, I think we have a problem.

Introduce cleverness, if you must, but please give users a simple way to return
to the simple. "Write your own Emacs, if you don't like the new, improved
version" is one, knee-jerk response. It's not a very good response, IMO.

By a simple way, I mean, for example, just customizing a user option or two -
not implementing complex functions. It is merely punting to provide just a
function-valued option `do-it-yourself'. When DWIM -> DYI, something is amiss.





  reply	other threads:[~2009-05-04 15:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04  7:41 display-buffer cleverness - how to tame? Drew Adams
2009-05-04  8:38 ` martin rudalics
2009-05-04 14:39   ` Drew Adams
2009-05-04 15:03     ` Miles Bader
2009-05-04 15:49       ` Drew Adams [this message]
2009-05-04 18:58         ` Samuel Bronson
2009-05-05  2:50         ` Miles Bader
2009-05-04 16:36     ` Stefan Monnier
2009-05-04 16:41     ` martin rudalics
2009-05-04 17:13       ` Drew Adams
2009-05-05  7:02         ` martin rudalics
2009-05-05 14:18           ` Drew Adams
2009-05-05 16:33             ` martin rudalics
2009-05-05 16:58               ` Drew Adams
2009-05-05 18:55                 ` martin rudalics
2009-05-05 20:20                   ` Drew Adams
2009-05-06 16:21                     ` martin rudalics
2009-05-06 17:54                       ` Drew Adams
2009-05-07  9:37                         ` martin rudalics

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='000001c9cccf$dc734c10$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 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).