Describe-Slot -- Show current value

[lansingthomas]

Describe-Slot -- Show current value

[aadcg]

I second @jmercouris.

Maybe we could make the "current value" be the value of the slot in a brand new instance of a class. That's not always the same as the default value, since it can be changed with define-configuration, configure-slot or some other configuration methods.

I believe that this may be a slightly different topic. Let's think of an example, say slot nyxt/mode/hint:hints-alphabet. The default value is "ABCDEFGHIJKLMNOPQRSTUVWXYZ". Now say that the user starts Nyxt and sets the slot to "TOMATO". I believe that the default value of said slot (shown in describe-slot) should now be "TOMATO". Unfortunately, as of today, it will continue to show "ABCDEFGHIJKLMNOPQRSTUVWXYZ". I can image that, in practice, this may more difficult to reliably do than it may look like at first sight.

[jmercouris]

The current value, for which object? I mean there could be an infinite amount of objects. In some cases it is obvious, like the current buffer object, but what about the ambiguous cases?

[hgluka]

I have to agree.
I like the idea, but now that I think about it, I don't know how feasible it is.

For example, there are slots like current-zoom-ratio or modes that can be different for each buffer. How do we pick the current value for those slots?
Another issue would be slots for classes like prompt-buffer that aren't always instantiated.

Maybe we could make the "current value" be the value of the slot in a brand new instance of a class. That's not always the same as the default value, since it can be changed with define-configuration, configure-slot or some other configuration methods.

What do you think? @jmercouris

[lansingthomas]

cool cool. Thx all.