From: Eli Zaretskii <eliz@gnu.org>
To: "R. Diez" <rdiezmail-emacs@yahoo.de>
Cc: 32142@debbugs.gnu.org
Subject: bug#32142: WG: 26.1; Problems with flyspell-region
Date: Sat, 14 Jul 2018 18:44:00 +0300 [thread overview]
Message-ID: <834lh1bz5r.fsf@gnu.org> (raw)
In-Reply-To: <912664a1-96e1-1a91-7b86-97184cf62aaf@yahoo.de> (rdiezmail-emacs@yahoo.de)
> From: "R. Diez" <rdiezmail-emacs@yahoo.de>
> Cc: 32142@debbugs.gnu.org
> Date: Sat, 14 Jul 2018 17:15:12 +0200
>
> > I object to the "unable or unwilling" part of your complaint.
> > I was just stating the fact that the feature you expected was > missing from Emacs, because no one designed and coded it.
>
> My "complaining" and your "stating of the fact" are both subjective
> perceptions.
No, a fact is not a subjective thing.
> My point of view is as follows: I took several e-mails to fix (if only
> in the documentation) an obvious issue I had reported correctly and I
> had to insist. Your answers were selective, side-stepping the problem.
> Your tend to answer in an authoritative way, kind of supporting or
> defending the current implementation, or negating the existence of a
> problem. It is a frustrating exercise. This is not the first time that
> this kind of "resistance" happens to me with open source projects, or
> with the Emacs developers. It is in fact a recurring pattern.
What you perceive is "selective", "side-stepping", "authoritative",
and "defensive" responses were just my attempts at understanding the
issues in full, that's all.
> I guess we could start a new bug about ispell, couldn't we?
You could, yes.
next prev parent reply other threads:[~2018-07-14 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <745366070.6138533.1531494673065.ref@mail.yahoo.com>
2018-07-13 15:11 ` bug#32142: WG: 26.1; Problems with flyspell-region R. Diez
2018-07-13 19:43 ` Eli Zaretskii
2018-07-13 20:22 ` R. Diez
2018-07-14 7:45 ` Eli Zaretskii
2018-07-14 15:15 ` R. Diez
2018-07-14 15:44 ` Eli Zaretskii [this message]
2018-07-14 15:56 ` Eli Zaretskii
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=834lh1bz5r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32142@debbugs.gnu.org \
--cc=rdiezmail-emacs@yahoo.de \
/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.