unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: henri-biard@francemel.fr
To: "Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 49037@debbugs.gnu.org
Subject: bug#49037: flyspell word correction frustrating
Date: Tue, 15 Jun 2021 18:34:00 +0200 (CEST)	[thread overview]
Message-ID: <ea-mime-60c8d678-7da2-4dfd75cf@www-7.mailo.com> (raw)
In-Reply-To: <87o8c7ruwp.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]



> We have no mechanisms to ban anybody. 



Let's hope so.  But you brought it up, I believed you.



I was pointing out that if your "experiment" was to see how much you can abuse the

bug reporting facilities (with trivial user questions that are already answered in the
manual) before you get banned -- it's not going to happen, so you can just stop the

experiment right away.



It's has only been your conclusion about what you call "experiment".



It is you who is inventing all these things.  At least Eli responds well, with no accusations

of sorts.



Can you tell me exactly where the information is in the manual because I could only

find a reference to aspell in "16.4 Checking and Correcting Spelling"



If it was good information I would not complain.



Instead of delving into accusations, it is always better to educate and assume other

are not as bad as you might believe.







From: Lars Ingebrigtsen <larsi@gnus.org>
To: henri-biard@francemel.fr
Subject: bug#49037: flyspell word correction frustrating
Date: 15/06/2021 17:48:22 Europe/Paris
Cc: 49037@debbugs.gnu.org

henri-biard@francemel.fr writes:

> You might as well ban people considering you are getting in the habit
> to close request anyway.

We have no mechanisms to ban anybody. I was pointing out that if your
"experiment" was to see how much you can abuse the bug reporting
facilities (with trivial user questions that are already answered in the
manual) before you get banned -- it's not going to happen, so you can
just stop the experiment right away.

-- 
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no





[-- Attachment #2: Type: text/html, Size: 2286 bytes --]

  reply	other threads:[~2021-06-15 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  5:47 bug#49037: flyspell word correction frustrating henri-biard
2021-06-15 15:10 ` Lars Ingebrigtsen
2021-06-15 15:23   ` henri-biard
2021-06-15 15:48     ` Lars Ingebrigtsen
2021-06-15 16:34       ` henri-biard [this message]
2021-06-15 16:54         ` Eli Zaretskii
2021-06-15 17:08           ` henri-biard
2021-06-15 17:33             ` Eli Zaretskii
2021-06-15 18:24               ` henri-biard
2021-06-15 18:29                 ` Eli Zaretskii
2021-06-15 19:35                   ` henri-biard
2021-06-15 20:00                   ` henri-biard
2021-06-15 17:59       ` Glenn Morris
2021-06-15 15:55     ` Robert Pluim
2021-06-15 16:48       ` henri-biard

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=ea-mime-60c8d678-7da2-4dfd75cf@www-7.mailo.com \
    --to=henri-biard@francemel.fr \
    --cc=49037@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).