unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <joakim@verona.se>
Cc: 'Emacs-Devel devel' <emacs-devel@gnu.org>,
	'Lennart Borgman' <lennart.borgman@gmail.com>,
	'Deniz Dogan' <deniz.a.m.dogan@gmail.com>
Subject: RE: Differences between ibuffer and dired
Date: Fri, 2 Jul 2010 07:26:00 -0700	[thread overview]
Message-ID: <562356F759744F228AAD6ED2EC0F26B7@us.oracle.com> (raw)
In-Reply-To: <m3zkyawb51.fsf@verona.se>

> There, I think I said it much better this time. Do you agree?

Do I agree you said it much better this time? You said something different. You
said what you said clearly each time.

Do I agree with a suggestion to provide different downloadable versions/skins of
Emacs for people to experiment with?  I have no comment on it, other than to
repeat that such experimenting would be no substitute for discussion about
whether and how to actually change Emacs.  It seems that you agree about that:

> The trunk will develop exactly like it always did, with healthy
> discussions for each change.

That was my only point.  I thought this thread was leading to a discussion about
a proposed change.  My bad if not.  If your point was only about providing some
code for people to try then I have no special comment on it.

Whether you put experimental code for people to try on a GNU site or on Emacs
Wiki or some other place, I have no objection, personally.  It's fine for people
to try different prototypes etc.  It's not unusual for someone to post a link
here to code that people can try, to get an idea about some suggestion.  You can
go try Aquamacs, for instance, and see whether some aspects of its UI (or
whatever) inspire good ideas for adoption by Emacs.  But any such ideas should
still be discussed here in order to be adopted.

Whether experimental code to try out takes the form of a snippet, a library, an
entire Emacs source tree, or an Emacs executable for some platform, the general
idea is the same.

As for myself, I will not be downloading a source tree or branch and building
Emacs from C, whether to test a "real" pretest or to try out someone's idea of a
nifty new look and feel.  I might try loading a Lisp library or two to try
something that is being proposed and discussed, but I will not be building Emacs
to see whether I think your key bindings or whatever are a good idea.

Just speaking for myself about that, and I'm not typical in that respect.
Perhaps most people discussing here will build your skinned versions and play
with them.




  reply	other threads:[~2010-07-02 14:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 13:49 Differences between ibuffer and dired Deniz Dogan
2010-07-01 14:34 ` joakim
2010-07-01 15:16   ` Deniz Dogan
2010-07-01 15:28     ` Lennart Borgman
2010-07-01 16:47       ` Drew Adams
2010-07-01 18:33         ` Wojciech Meyer
2010-07-01 21:34         ` Stephen Berman
2010-07-01 21:38           ` Deniz Dogan
2010-07-01 21:48             ` Drew Adams
2010-07-01 23:27               ` Lennart Borgman
2010-07-02  0:09                 ` Drew Adams
2010-07-02  0:13                   ` Lennart Borgman
2010-07-02  0:38                     ` Drew Adams
2010-07-02  1:02                       ` Lennart Borgman
2010-07-02 20:57                 ` Juri Linkov
2010-07-02 22:36                   ` Lennart Borgman
2010-07-01 21:41           ` Drew Adams
2010-07-02  4:56         ` joakim
2010-07-02  5:31           ` Drew Adams
2010-07-02  8:17             ` joakim
2010-07-02 14:26               ` Drew Adams [this message]
2010-07-02 20:57           ` Juri Linkov
2010-07-23 15:40 ` 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=562356F759744F228AAD6ED2EC0F26B7@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=deniz.a.m.dogan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=lennart.borgman@gmail.com \
    /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).