Re: Patch proposal: display symbol source code in help buffers

[martin rudalics]

>> If you fit the window showing *Help* to its buffer, there is no room
>> left.
>
> It would be nice to make it fit to N lines in height, and C columns in width,
> i.e. to make it fit to certain size.

Who would specify that "certain size"?

>>      .  Where to pop up the location of the source and how to get rid of
>> it is a question we currently discuss in Bug#9054 and Bug#36767.
>
> There are so many discussions here so I wasn't following those. I really don't
> know what you have discussed there. I come to this from my own needs.

Similar issues like how to navigate to the source of a function or
variable from the current point of the user's interest.

> This shouldn't be by any mean in collision what you are saying here. What you
> describe, as I understand it, is to display source on-demand, in help buffer,
> which would be very nice too. What I have done is to display by global
> switch. It would be still useful to have on-demand display when global switch 
is
> off, and it would be trivial to re-build the patch to include that. I can
> rebuild and send new one. I have found a bug and I need to rebuild-it anyway. 
I
> can also refactor it and add an interactive function that can be boudn to a 
key
> to display only sources in help buffer. And if global switch is on, and 
sources
> are requested, it can function as a "narrow" button, i.e. fit only symbol 
source
> to the help buffer. Would that be interesting?

What we should establish first is what users want.  Eli and Lars have
explained their workflow in the threads I cited including how and why
they want to go to the source in the first place, where to go from there
and how to return to the initial state.  Few others have so far.

martin