From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#46240: Sorting order of read-char-by-name Date: Wed, 03 Feb 2021 21:44:47 +0200 Organization: LINKOV.NET Message-ID: <87o8h1q6kw.fsf@mail.linkov.net> References: <87v9bb4tm2.fsf@mail.linkov.net> <83wnvr65zg.fsf@gnu.org> <87o8h266x2.fsf@mail.linkov.net> <838s865mxs.fsf@gnu.org> <87bld1t6z9.fsf@mail.linkov.net> <83ft2d3um3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25008"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: 46240@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 03 21:05:55 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l7OPT-0006Op-7K for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 03 Feb 2021 21:05:55 +0100 Original-Received: from localhost ([::1]:48942 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l7OPS-0006YU-3J for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 03 Feb 2021 15:05:54 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50126) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l7O6E-0006Mj-Mm for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 14:46:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55597) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l7O6E-00038C-FB for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 14:46:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1l7O6E-0002Wc-6a for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2021 14:46:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 03 Feb 2021 19:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46240 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 46240-submit@debbugs.gnu.org id=B46240.16123815419671 (code B ref 46240); Wed, 03 Feb 2021 19:46:02 +0000 Original-Received: (at 46240) by debbugs.gnu.org; 3 Feb 2021 19:45:41 +0000 Original-Received: from localhost ([127.0.0.1]:38909 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7O5t-0002Vv-GT for submit@debbugs.gnu.org; Wed, 03 Feb 2021 14:45:41 -0500 Original-Received: from relay2-d.mail.gandi.net ([217.70.183.194]:51223) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1l7O5s-0002VW-DN for 46240@debbugs.gnu.org; Wed, 03 Feb 2021 14:45:40 -0500 X-Originating-IP: 91.129.108.204 Original-Received: from mail.gandi.net (m91-129-108-204.cust.tele2.ee [91.129.108.204]) (Authenticated sender: juri@linkov.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 9765540006; Wed, 3 Feb 2021 19:45:32 +0000 (UTC) In-Reply-To: <83ft2d3um3.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 03 Feb 2021 19:54:12 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:199237 Archived-At: >> Here is an option for this: > > Thanks, but why does the value of the defcustom _have_ to be a > function? Such defcustoms make it harder for users to customize them, > because not everyone can write a sorting function. > > How about allowing simple values there, and if you really think we > should allow a function, make that one of the possible values, but not > require that the value be a function? I agree. If there is a need to add more values later, such as grouping by Unicode blocks, then it would be easier to add new values, not functions.