From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: function arguments downcased in help buffers
Date: Tue, 15 Apr 2008 18:01:43 +0200 [thread overview]
Message-ID: <f7ccd24b0804150901n2cce0e43i3e0edb023e724533@mail.gmail.com> (raw)
In-Reply-To: <200804151537.m3FFb71U018970@sallyv1.ics.uci.edu>
On Tue, Apr 15, 2008 at 5:37 PM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> That might have been your intention, but that is not what you actually
> said, and what I was replying to.
We can discuss forever the meaning of "they are", but I stand for what
I actually said.
> This is unrelated to what I wrote and the context I wrote it in. DejaVu
> Sans Mono is also not useful to X11 emacs for emacs 22,
Why not?
> AFAICT it is not available as a core X font.
That is unrelated to what you wrote, unless your definition of popular
is "available as a core X font".
> This type of attitude is one of the reasons emacs-devel is such an
> unpleasant environment lately.
I'd say that the attitude of using "brain-dead", "bug", "stupid" etc
to people's decissions (and, yes, sometimes mistakes) is one reason
why emacs-devel is often unpleasant. That, and the habit of pushing to
change back defaults people don't like, instead of just customizing
them in their .emacs and be done with it.
> The discussion was about a feature that recently changed behavior
That's one way to see it. Another is to think that the feature has not
changed behavior, but a recent bug is triggering an unindented
misbehavior.
> and
> the statement you replied to was clearly labeled as _a personal opinion_
> and clearly stated that it didn't require a change if that is what most
> people want.
I fail to see why your statement is "clearly [...] _a personal
opinion_", and my comment, which explicitly said "but I find it
a bit insulting [...]", is not.
> Stating that criticism of a feature is an insult is a
> clear way to drive people way from any type of discussion.
Nice strawman, but I wasn't objecting to your disliking of the
feature, or your criticism, just to the election of the word "bug" to
denote an intended feature.
Juanma
next prev parent reply other threads:[~2008-04-15 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 0:20 function arguments downcased in help buffers Dan Nicolaescu
2008-04-15 1:52 ` Juanma Barranquero
2008-04-15 2:04 ` Glenn Morris
2008-04-15 2:33 ` Juanma Barranquero
2008-04-15 5:03 ` Dan Nicolaescu
2008-04-15 8:51 ` Juanma Barranquero
2008-04-15 14:16 ` Drew Adams
2008-04-15 14:48 ` Juanma Barranquero
2008-04-15 15:04 ` Drew Adams
2008-04-15 14:25 ` Dan Nicolaescu
2008-04-15 15:00 ` Juanma Barranquero
2008-04-15 15:37 ` Dan Nicolaescu
2008-04-15 16:01 ` Juanma Barranquero [this message]
2008-04-15 17:15 ` Stefan Monnier
2008-04-15 17:50 ` Dan Nicolaescu
2008-04-15 16:00 ` Jason Rumney
2008-04-15 23:09 ` Kenichi Handa
2008-04-16 3:44 ` Dan Nicolaescu
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=f7ccd24b0804150901n2cce0e43i3e0edb023e724533@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.