Re: Improving describe-mode and discoverability

["Clément Pit--Claudel" <clement.pit@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1670 bytes --]

On 2016-06-23 20:05, Drew Adams wrote:
>> I propose to let user customize the result, using `format-keymap-function'.
> 
> `keymap-format-function'?

Works for me :)

> Much clearer; thanks.  (And I appreciate the lack of automatic use.)
> 
> For my part:
> 
> 1. A user option for how to display \\{...} is not a bad idea.
> 
> 2. The defcustom type could include a `choice' among: two predefined formats
> (the current one and yours) and an arbitrary user-defined function.

Sounds great :)

> (IMO, the default behavior should probably be what the behavior has been,
> 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 default has been to lean towards changing the default, with the expectation that 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 to
> 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 be enough; there are other let-bindable settings already controlling some aspects of printing, for example.  

> 4. For that, code could I guess bind the option around a given use of the
> string.  (Would that handle all use cases?)
> 
> I'm writing this quickly without thinking much about it, so no doubt others
> will see clearer.

Thanks for your feedback and your help refining this proposal! Now hopefully someone can lend me the hand with refining the patch, too :)

Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]