all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Juri Linkov' <juri@jurta.org>,
	'Stephen Berman' <stephen.berman@gmx.net>,
	emacs-devel@gnu.org, 'Deniz Dogan' <deniz.a.m.dogan@gmail.com>
Subject: RE: Differences between ibuffer and dired
Date: Thu, 1 Jul 2010 17:38:52 -0700	[thread overview]
Message-ID: <E4D6EB4BACC3406B84DEC65A173B909F@us.oracle.com> (raw)
In-Reply-To: <AANLkTiku3l8YLsuXWxy0ApwZI5jUKrr6nMin0M8-JGx-@mail.gmail.com>

> >> While we are looking at this:
> >
> > You mean making some keys more consistent between ibuffer 
> > and dired?  See Subject line.
> >
> >> Wasn't there a discussion before about putting ibuffer on C-x C-b?
> >
> > ? No connection with the current subject.
> >
> >> I don't remember, someone had something to
> >> say about this. Was it Juri?
> >
> > 1. Why?
> > 2. Why would you bring that up here, in this discussion?
> 
> I think you want to say that for you it is easier to keep those
> subjects separate. I can try to remember to respect that, but for me
> it is easier to do it the way I did it here.
> 
> There are simply different thinking styles.

_I_ think I want to say that you introduced a different subject.  And that
subject would be better discussed in a different thread.  This thread is about
"Differences between ibuffer and dired".  It is easier for _the list_ as a whole
"to keep those subjects separate".  It's not about me, what's easier for me, or
my thinking style.

That point I made is not about thinking styles.
It's about mailing-list organization and etiquette.

Use any thinking style you like.  FWIW, I appreciate your thinking style.  But
please try harder not to hijack threads (yes, we are all occasionally guilty of
that).

FYI - Today alone, you also injected a proposal to add a new menu-bar menu to
consolidate all minor-mode menus into a thread about possibly including
anything.el in Emacs.  No connection.  Except perhaps that something you read in
one of that thread's mails reminded you that you had proposed that menu before,
so you proposed it again.  It's OK to bring that up again, but please just use a
new thread.

This is a pattern, and IMHO it's not helpful.  Should we be reduced to having
just one thread for everything, entitled "poubelle", "catch-all", "X" or
"Lennart"?

Think about it, please.  Even in your thinking style you might realize that your
new topics will be better treated and easier to find later if you keep them
separate.  It's easy to do.  Copy as much of the original context that made you
think of the new topic as you want.  Just change the Subject line so we know
what the topic is.  Thx.




  reply	other threads:[~2010-07-02  0:38 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=E4D6EB4BACC3406B84DEC65A173B909F@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=deniz.a.m.dogan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=lennart.borgman@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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.