From: Arthur Miller <arthur.miller@live.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Patch proposal: display symbol source code in help buffers
Date: Tue, 21 Sep 2021 12:24:02 +0200 [thread overview]
Message-ID: <AM9PR09MB49779B6C3D7923E58373E7F296A19@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <3438b87f-b24a-3bc3-871f-84818868d445@gmx.at> (martin rudalics's message of "Tue, 21 Sep 2021 10:34:34 +0200")
martin rudalics <rudalics@gmx.at> writes:
>>> 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"?
User, of course, who else? We put some default size and a defcuctom for user to
change, as always?
>>> . 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.
I have tested yesterday, and it works well as it is in help buffer. It is like a
mini browser. I am sure there are possibly 1001 different ways to do things; but
somewhere we have to make a choice and do something. If the people wish
something different from how it works, we can always build on it later. As I
understand a lot of people use Helpful, and the buil-in help works even better
considering cross linking. I can click in built-in help and get new functions
and vars opened in the help buffer already; I can't do that in Helpful. Let's
have a face lift for built in help for 28. I am sure we could debate for years
and always someone will like it differently. Let's have something that works.
>> 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.
I haven't read the other thread, but I have used help and why I think it is
good, and some other have as well.
Can you try what I send in yesterday, with soucre view toggle? I think it works
quite nice (I did a misstake and went 1 row too far when deleting, but that's a
trivial to fix).
next prev parent reply other threads:[~2021-09-21 10:24 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 19:50 Patch proposal: display symbol source code in help buffers Arthur Miller
2021-09-20 5:46 ` Lars Ingebrigtsen
2021-09-20 6:09 ` Stefan Kangas
2021-09-20 6:14 ` Lars Ingebrigtsen
2021-09-20 7:17 ` Ihor Radchenko
2021-09-20 7:43 ` Stefan Kangas
2021-09-20 8:29 ` martin rudalics
2021-09-20 9:04 ` Ihor Radchenko
2021-09-20 23:45 ` Arthur Miller
2021-09-21 4:16 ` Lars Ingebrigtsen
2021-09-21 6:59 ` Ihor Radchenko
2021-09-21 7:41 ` Stefan Kangas
2021-09-21 8:38 ` Eli Zaretskii
2021-09-21 9:17 ` Ihor Radchenko
2021-09-21 16:49 ` Lars Ingebrigtsen
2021-10-01 7:05 ` Ihor Radchenko
2021-10-01 7:09 ` Lars Ingebrigtsen
2021-10-01 7:21 ` Ihor Radchenko
2021-10-01 7:21 ` Lars Ingebrigtsen
2021-10-01 9:04 ` Ihor Radchenko
2021-10-01 12:20 ` Lars Ingebrigtsen
2021-10-01 7:24 ` Eli Zaretskii
2021-10-01 9:08 ` Ihor Radchenko
2021-10-01 10:24 ` Eli Zaretskii
2021-10-01 14:14 ` Ihor Radchenko
2021-09-21 8:34 ` martin rudalics
2021-09-20 15:01 ` Arthur Miller
2021-09-21 7:41 ` Stefan Kangas
2021-09-20 15:27 ` Arthur Miller
2021-09-20 6:47 ` Eli Zaretskii
2021-09-20 15:27 ` Arthur Miller
2021-09-20 14:55 ` Arthur Miller
2021-09-21 4:18 ` Lars Ingebrigtsen
2021-09-21 10:26 ` Arthur Miller
2021-09-20 15:23 ` Arthur Miller
2021-09-20 5:59 ` Eli Zaretskii
2021-09-20 6:37 ` Gregor Zattler
2021-09-20 7:01 ` Eli Zaretskii
2021-09-20 15:21 ` Arthur Miller
2021-09-20 8:21 ` martin rudalics
2021-09-20 18:13 ` Arthur Miller
2021-09-21 8:34 ` martin rudalics
2021-09-21 10:24 ` Arthur Miller [this message]
2021-09-21 16:52 ` martin rudalics
2021-09-21 18:56 ` Arthur Miller
2021-09-21 17:30 ` Juri Linkov
2021-09-21 19:13 ` Arthur Miller
2021-09-22 7:49 ` martin rudalics
2021-09-22 16:04 ` Juri Linkov
2021-09-22 17:52 ` martin rudalics
2021-09-23 8:15 ` martin rudalics
2021-09-23 15:52 ` Juri Linkov
2021-09-26 9:10 ` martin rudalics
2021-09-22 22:38 ` Arthur Miller
2021-09-23 8:22 ` martin rudalics
2021-09-20 12:19 ` Dmitry Gutov
2021-09-20 15:13 ` Arthur Miller
2021-09-20 15:11 ` Arthur Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR09MB49779B6C3D7923E58373E7F296A19@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).