From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
tino.calancha@gmail.com, emacs-devel@gnu.org
Subject: RE: Ibuffer: w and B default to buffer at current line
Date: Sat, 17 Sep 2016 18:45:20 -0700 (PDT) [thread overview]
Message-ID: <c898f8c7-47e5-4870-adcb-f19ffe4b3855@default> (raw)
In-Reply-To: <m237kym6ea.fsf@newartisans.com>
> I'm not quite sure why you're even asking these questions, Drew, so I
> think I'll withdraw from this discussion, since nothing useful is being
> achieved.
Trying to find out what you are really saying, and how it might
apply to Emacs development. You have a strong belief that each
function should do one thing and one thing well. It would be
helpful, if that is to be a guideline or if we can learn from
it, to flesh out what you mean by it.
If it's clear to you and you don't care whether it's clear to
others, that's OK too. As I said, I think that such things
are usually clearer in the context of discussing concrete
features or code. No doubt there will be occasions to learn
what you mean for specific examples.
My guess is that what you prefer here is probably something
I would prefer too, but I'm not sure. The devil, as well as
interesting guidelines, are likely in the details.
next prev parent reply other threads:[~2016-09-18 1:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 5:35 Ibuffer: w and B default to buffer at current line Tino Calancha
2016-09-14 6:41 ` John Wiegley
2016-09-14 7:21 ` Tino Calancha
2016-09-14 14:08 ` Drew Adams
2016-09-15 22:05 ` John Wiegley
2016-09-16 6:40 ` Eli Zaretskii
[not found] ` <<83intw5our.fsf@gnu.org>
2016-09-16 14:53 ` Drew Adams
2016-09-17 16:30 ` John Wiegley
2016-09-17 17:21 ` Eli Zaretskii
2016-09-17 21:35 ` John Wiegley
2016-09-17 23:26 ` Drew Adams
2016-09-17 23:51 ` John Wiegley
2016-09-18 1:45 ` Drew Adams [this message]
2016-09-18 2:18 ` John Wiegley
2016-09-18 14:26 ` Eli Zaretskii
2016-09-18 19:35 ` John Wiegley
[not found] ` <<83zin630i9.fsf@gnu.org>
2016-09-17 18:47 ` Drew Adams
2016-09-17 19:25 ` Eli Zaretskii
[not found] ` <<83vaxuib1p.fsf@gnu.org>
2016-09-17 19:33 ` Drew Adams
2016-09-18 14:29 ` Eli Zaretskii
[not found] ` <<d33a60f5-b8b6-4637-b3e6-ea1b09d98f85@default>
[not found] ` <<83poo1i8nf.fsf@gnu.org>
2016-09-18 17:55 ` naming functions [was: Ibuffer: w and B default to buffer at current line] Drew Adams
2016-09-18 19:23 ` John Wiegley
2016-09-18 23:24 ` Drew Adams
2016-09-19 16:35 ` Eli Zaretskii
2016-09-17 18:22 ` Ibuffer: w and B default to buffer at current line Tino Calancha
2016-09-26 12:08 ` Tino Calancha
2016-10-03 12:28 ` Tino Calancha
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=c898f8c7-47e5-4870-adcb-f19ffe4b3855@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=tino.calancha@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).