From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit--Claudel?= Newsgroups: gmane.emacs.devel Subject: Re: Improving describe-mode and discoverability Date: Thu, 23 Jun 2016 22:59:32 -0400 Message-ID: <576CA214.7000302@gmail.com> References: <576C2A6C.3090908@gmail.com> <576C59AF.7080902@gmail.com> <9c928ea6-6799-d096-de54-b2bf7ac140ec@yandex.ru> <576C6256.6060708@gmail.com> <576C7326.1020502@gmail.com> <531a7bec-28af-4c4c-aa85-1d13e84c98be@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o4uSxHHLVbkNt00nHLJv6xstB3OioCSaw" X-Trace: ger.gmane.org 1466737325 19817 80.91.229.3 (24 Jun 2016 03:02:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 24 Jun 2016 03:02:05 +0000 (UTC) To: Drew Adams , Dmitry Gutov , Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 24 05:01:56 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bGHNU-0008HV-AX for ged-emacs-devel@m.gmane.org; Fri, 24 Jun 2016 05:01:56 +0200 Original-Received: from localhost ([::1]:40472 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGHNT-0003wU-7z for ged-emacs-devel@m.gmane.org; Thu, 23 Jun 2016 23:01:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGHLL-00034p-Sy for emacs-devel@gnu.org; Thu, 23 Jun 2016 22:59:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bGHLJ-0007pX-7h for emacs-devel@gnu.org; Thu, 23 Jun 2016 22:59:43 -0400 Original-Received: from mout.kundenserver.de ([212.227.126.131]:55149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bGHLI-0007pO-TR for emacs-devel@gnu.org; Thu, 23 Jun 2016 22:59:41 -0400 Original-Received: from [18.189.1.110] ([18.189.1.110]) by mrelayeu.kundenserver.de (mreue002) with ESMTPSA (Nemesis) id 0MdTH9-1azZZN0wDr-00IV3D; Fri, 24 Jun 2016 04:59:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 In-Reply-To: <531a7bec-28af-4c4c-aa85-1d13e84c98be@default> X-Provags-ID: V03:K0:g8gzl7Hbn22+yJJb/Tg+cmyrsWgQhiIBzXoQS53ThFuHMecJMC8 Fmd4w1CGbdwiKxlvDYT7fP8nKBBNhJ9DfBCufXO5gCP1sycx5tqYhYgpgEHTwtexL5KqQH0 9SYUkAcvdNDUIrVaNhvRyu8iT8x+zcCaAmB8a3bSio4ZraFabx1joZDT3qz8vXTraZ5GBCv Ok1kjSAbv3w/1B86Xsc4g== X-UI-Out-Filterresults: notjunk:1;V01:K0:kjZkKw0UXt0=:vS/QZpGminVTZQlNWMhiKS 0u22QntLK+tZflK7VbON0fqurX0kUxFtCwFY8oOPmu5NUNjbZcuDeT29LLqtEycQ5ev2+TL5e MixRftGCtgl3LnI4Iz5hmKRNtqyPkhJMSiZT5fiCeMnXR2WUSuYsR+66IK37dywTkYj6lU6S+ ptyCIqL5OLX9dfPsTrM5JfWlorRUmdLPUEW1FuCqmBzKEXlT55suOBFOJG9P3TCx08HPsILWZ XlgZ+7jv9QE6PkKqi3s4SWpWb9fR9HieUgS+w2LtF1at4WrS8pRdMJ2NV3hbTNKihf97g9MKy YLPzMivHWOzVuMHv7+gOEIsZlTkZ91BxhF3E3/Tx7nfe+Pdh9mM6uh6EJO6D3DmqUF2+lA6C7 QgoWdN+0SdYB/zaTRxc1zdUNBp7GraqNvfHRpppMFabvhXdZoZevpYM4xFMdh5ce8u7JYVp7r Hwe5KsEuQflkVqLNgHj4j4CPCgHXWxnnr6OOzlm7hjHKMmGomNGyJE9DqZ0SSDDPkKveCzhNF AKsxUR9+jWSJUGrsgqHkLMOm9+QaAUKDLbliPAAUHDesuZBVnKrWcvPvTphK1fftBbJJB61o5 GbVvNWw+UTtHZ7lvnMPHlygndSgtsM+hup9v0C5i7KB4RNmApXcl+ZlIJ6oStqFzJ8mBAQLTV WLikclVflKFC6pmXBRa7maLo+K8klaP2UC8Audnqzzrqvcj0QAym3jsUGBSk8TgBv++Y= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.126.131 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:204717 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --o4uSxHHLVbkNt00nHLJv6xstB3OioCSaw Content-Type: multipart/mixed; boundary="SvoNf2qoAk48aaoC9ePe8hiNgd5BhRsAp" From: =?UTF-8?Q?Cl=c3=a9ment_Pit--Claudel?= To: Drew Adams , Dmitry Gutov , Emacs developers Message-ID: <576CA214.7000302@gmail.com> Subject: Re: Improving describe-mode and discoverability References: <576C2A6C.3090908@gmail.com> <576C59AF.7080902@gmail.com> <9c928ea6-6799-d096-de54-b2bf7ac140ec@yandex.ru> <576C6256.6060708@gmail.com> <576C7326.1020502@gmail.com> <531a7bec-28af-4c4c-aa85-1d13e84c98be@default> In-Reply-To: <531a7bec-28af-4c4c-aa85-1d13e84c98be@default> --SvoNf2qoAk48aaoC9ePe8hiNgd5BhRsAp Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-23 20:05, Drew Adams wrote: >> I propose to let user customize the result, using `format-keymap-funct= ion'. >=20 > `keymap-format-function'? Works for me :) > Much clearer; thanks. (And I appreciate the lack of automatic use.) >=20 > For my part: >=20 > 1. A user option for how to display \\{...} is not a bad idea. >=20 > 2. The defcustom type could include a `choice' among: two predefined fo= rmats > (the current one and yours) and an arbitrary user-defined function. Sounds great :) > (IMO, the default behavior should probably be what the behavior has bee= n, > but that's another discussion.) I'm never too sure about this. (I have the same problem, and I'm sure you= did too, with changing the defaults in my packages). In general my defau= lt has been to lean towards changing the default, with the expectation th= at those who knew about the old default could revert to it :) > 3. A problem I see with this is that there needs to be a way for code t= o > control the format in some cases - separately from users being able to > control the display in other cases. As you say below, I think let-binding around the code in question would b= e enough; there are other let-bindable settings already controlling some = aspects of printing, for example. =20 > 4. For that, code could I guess bind the option around a given use of t= he > string. (Would that handle all use cases?) >=20 > I'm writing this quickly without thinking much about it, so no doubt ot= hers > will see clearer. Thanks for your feedback and your help refining this proposal! Now hopefu= lly someone can lend me the hand with refining the patch, too :) Cl=C3=A9ment. --SvoNf2qoAk48aaoC9ePe8hiNgd5BhRsAp-- --o4uSxHHLVbkNt00nHLJv6xstB3OioCSaw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXbKIUAAoJEPqg+cTm90wjthoQAJLe2YF7kN0sFZQQORXOmPKr HX5b1myibRtlEcMNywDFlSfxEjn5z8ggxJA3//hyQ9tDJ3Eab3Q+gbZGxo4TfVlr NhUL2H1au5YkWl1DTezymVHx2mk0SqqdRn3wK1BE2y4pBhbgIYDKgGCg++F9xwm+ Ps1ktqCiaCF60vZeYQzuyzYposbxg/vYrOK4L8Y/R5DlOOhLEF0tigwzGG987g/D wZvo0fJWhF1UibzwSKU2jnUi7DLyr7mbhImnFU2EbN0HkMw9gpqHhw7ubc3/cycW hZjBoGEMI0IDbHdKzgAJff69YRcT+A136jKzOx5JwURBbHxVKHT5SvHfNKguLe0b u2c4Uj462tmNDWAl/FDRz+UuzKK88/8Wf4NT+Sn7RLk+SrKQivndPJ8Z7tjqWCL2 SgWRM4Ux7B0tn2W30G4rBV4Rl0TmobSWEqFxEXPTKvf28gyJdjWPOju2t9mR5dok CenYonVh/JzNIAMaQ+QDp/OBK6Fkouy75U5UwrOP0z/4pkMEejDR9VDcnnqoh0Vd MbTfbc5lve9mFsB/oc6bIc/T+0JZ9x/iOWlDcLxe08lOmysrCtWDeyTLIBJT5W/b EB+J6J3huKf132ZX94p4J1UMKVrT4SnyjphftADRNhisAtMLf/SBm8N//CC5/itU ouLKNjg/DQJv9NLchtuu =gKcW -----END PGP SIGNATURE----- --o4uSxHHLVbkNt00nHLJv6xstB3OioCSaw--