unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 31772@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#31772: 26.1; (thing-at-point 'list) regression
Date: Mon, 11 Jun 2018 19:34:42 +0300	[thread overview]
Message-ID: <83a7s1qo2l.fsf@gnu.org> (raw)
In-Reply-To: <m1602p5mro.fsf@gmail.com> (message from Leo Liu on Tue, 12 Jun 2018 00:08:27 +0800)

> From: Leo Liu <sdl.web@gmail.com>
> Date: Tue, 12 Jun 2018 00:08:27 +0800
> Cc: 31772@debbugs.gnu.org
> 
> I am simply pointing out the irony it only takes one complaint to
> change something that's in Emacs for a long time but we often forget
> the majority that are happy with the feature never come and tell us
> from time to time what a great feature it is, they love it and don't
> change it.

No, we never forget that.  And one complaint is usually not enough to
make such changes.  on the contrary, sometimes the disputes about such
complaints are too long and exhaustive.  You can see many examples of
that in the archives and on the bug tracker.

But yes, the number of people here is relatively small, so each voice
counts.  Please be sure to voice yours, I'm certain it will have a
significant effect on the outcome.

> I already joined in but I am a little short of time lately.

We all are.  Thanks in advance for your contributions, both in
opinions and in code.





  parent reply	other threads:[~2018-06-11 16:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10  3:58 bug#31772: 26.1; (thing-at-point 'list) regression Leo Liu
2018-06-10 15:03 ` Eli Zaretskii
2018-06-10 15:21   ` Tino Calancha
2018-06-11  3:17     ` Leo Liu
2018-06-11 15:06       ` Tino Calancha
2018-06-11 16:08         ` Leo Liu
2018-06-11 16:25           ` Tino Calancha
2018-09-06 10:37             ` Leo Liu
2018-09-06 19:01               ` Andreas Röhler
2018-09-07  4:42                 ` Leo Liu
2018-09-07  8:17                   ` Andreas Röhler
2018-09-08  0:09                     ` Leo Liu
2018-09-11  8:31               ` Eli Zaretskii
2018-09-11 10:26                 ` Leo Liu
2018-09-11 11:16                   ` Eli Zaretskii
2018-09-11 11:52                     ` Andreas Röhler
2018-09-11 12:10                       ` Eli Zaretskii
2018-09-11 12:36                     ` Leo Liu
2018-09-11 12:39                       ` Eli Zaretskii
2018-09-14 14:55                         ` Leo Liu
2018-09-15  9:06                           ` Eli Zaretskii
2018-09-15 12:58                             ` Leo Liu
2018-09-15 13:28                               ` Eli Zaretskii
2018-06-11 16:34           ` Eli Zaretskii [this message]
2018-06-11 15:10       ` Eli Zaretskii
2018-06-11 16:36         ` Leo Liu
2018-06-11  2:32   ` Leo Liu
2018-06-11 14:58     ` Eli Zaretskii
2018-06-11 17:04       ` Leo Liu

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=83a7s1qo2l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31772@debbugs.gnu.org \
    --cc=sdl.web@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).