From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, emacs-tangents@gnu.org, abrochard@gmx.com,
Samuel Wales <samologist@gmail.com>
Subject: Re: Emacs User Survey 2020 Results
Date: Fri, 11 Dec 2020 11:57:38 +0300 [thread overview]
Message-ID: <X9M0gueKG48o7r9Z@protected.rcdrun.com> (raw)
In-Reply-To: <83h7os3h6y.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2020-12-11 11:01]:
> > From: Samuel Wales <samologist@gmail.com>
> > Date: Thu, 10 Dec 2020 14:30:01 -0700
> > Cc: emacs-tangents@gnu.org, Adrien Brochard <abrochard@gmx.com>
> >
> > (as an analogy, if you go to a doctor who does not treat you, you will
> > not go back to that doctor. but the doctor might think that you were
> > cured because you did not go back. this is a serious problem in
> > medicine.)
>
> But since we are not talking about one person, but many different
> persons, it is still surprising that we don't get such bug reports,
> because surely some of these persons may not know or assume up front
> that these problems are unlikely to be fixed. It isn't like there's a
> secret cabal of people who spread the idea that these problems are
> unlikely to be fixed and therefore shouldn't be reported. The law or
> large numbers should have won here. It is surprising that it didn't.
When I was using Emacs on Redhat Linux back in 1999, if I remember
well it was crashing in each session. And I have never reported those
many many bugs neither to Redhat neiter to Emacs development. There
were various versions of Emacs and I coped with it. Often I used other
editors.
Then when I started using Debian GNU/Linux I have not been reporting
bugs probably for few years. I have just assumed it is not working
well, but that I could do something about it was not clear. There will
be whole series of users not being aware of it.
Then later I have been reporting all Debian GNU/Linux related bugs
only to Debian, straight there, and nowhere else. I have not even know
that there is some central way to report bug. I remember that under
Help there was menu item to report Emacs bug, but I have not used that
interface, rather Debian interface. Maybe maintainers reported to
upstream.
Long time passed until I started reporting to Emacs and this is
probably because I switched to Hyperbola GNU/Linux-libre and somebody
directed me. Otherwise I was reporting to https://www.hyperbola.info
anything related to Hyperbola packages as I was used from Debian this
way.
Look:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=emacs
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs-common
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs-el
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs-gtk
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs-lucid
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs-nox
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=emacs25
https://issues.hyperbola.info/index.php?string=emacs&project=0&do=index&type%5B%5D=&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=open&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
https://bugs.archlinux.org/index.php?string=emacs&project=1&search_in_comments=1&search_in_details=1&search_for_all=1&type%5B%5D=&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=open&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index
https://bugs.launchpad.net/ubuntu?field.searchtext=emacs&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
prev parent reply other threads:[~2020-12-11 8:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:40 Emacs User Survey 2020 Results Adrien Brochard
2020-12-09 17:22 ` Jean Louis
2020-12-09 18:24 ` Jack Kamm
2020-12-09 18:30 ` Jean Louis
2020-12-09 18:29 ` Yuri Khan
2020-12-09 18:51 ` Jean Louis
2020-12-09 21:32 ` Adrien Brochard
2020-12-09 19:30 ` Göktuğ Kayaalp
2020-12-09 20:45 ` Jean Louis
2020-12-09 21:39 ` Adrien Brochard
2020-12-09 22:20 ` Jean Louis
2020-12-10 23:09 ` chad
2020-12-10 5:39 ` Göktuğ Kayaalp
2020-12-10 5:59 ` Sacha Chua
2020-12-10 13:04 ` Adrien Brochard
2020-12-09 21:31 ` Adrien Brochard
2020-12-09 23:25 ` Jean Louis
2020-12-09 17:44 ` Qiantan Hong
2020-12-09 20:58 ` Lars Ingebrigtsen
2020-12-09 21:08 ` Jean Louis
2020-12-09 23:08 ` Gregory Heytings via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2020-12-10 21:28 ` Samuel Wales
2020-12-10 21:30 ` Samuel Wales
2020-12-11 8:00 ` Eli Zaretskii
2020-12-11 8:57 ` Jean Louis [this message]
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=X9M0gueKG48o7r9Z@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=abrochard@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-tangents@gnu.org \
--cc=larsi@gnus.org \
--cc=samologist@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.
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).