From: Arthur Miller <arthur.miller@live.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Florian Beck <abstraktion@t-online.de>,
9054@debbugs.gnu.org
Subject: bug#9054: 24.0.50; show source in other window
Date: Sun, 26 Sep 2021 16:04:49 +0200 [thread overview]
Message-ID: <AM9PR09MB497719E0E42117567C027B0196A69@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <134f4301-d4c8-a73b-72f9-fba1577e8607@gmx.at> (martin rudalics's message of "Sun, 26 Sep 2021 11:10:13 +0200")
martin rudalics <rudalics@gmx.at> writes:
>>> I just did C-h f whitespace-display-window, from there went to that
>>> function's source and added a doc-string for it. Displaying the source
>>> in the help window would have been merely distracting in this scenario.
>>>
>> Ok, but that is diferrent usage scenario :). You are completely changing
>> requirement there. What you describe is indeed more handy when you wish to hack
>> a function. But when you do not wish to hack it, but would like to see what it
>> does, but stay in the same buffer you were edited, than what you describe would
>> be nuissance and distraction.
>
> The point I wanted to make was that there may be tenths of different
> usage scenarios for perusing the *Help* window and its buffer.
Ah, sorry then, in that case we are in agreement. Yes there are different usage
scenarios. I think what you have considered in this thread, does not even
require help buffer. If someone would just like to pop a source for a symbol,
you could just code an interactive funtion to open the source file for the
symbol, all the code is already there. There is no need to even touch the
help-buffer for that.
>> Also, consider again, people new to Emacs. Having source auto shown to them,
>> makes them probably more akin to see what is going on, how things work and give
>> more incitament to explore. I think.
>
> There are two major sources of disappointments here - many users are not
> proficient in C and often the function they will look up first is only a
> stub for the function doing the actual work.
Yes indeed, I agree with that one. Also many new users would be new to Lisp
too. My proposal was to make it optional to show/hide source, mostly because of
the cpu overhead, but we can also add option to show only lisp sources.
I don't what is the best; I don't think there is a one-solution-fits-all in this
case. Users have different workflows, different backgroudns etc, so maybe it is
best to just be flexible as much as it is possible.
next prev parent reply other threads:[~2021-09-26 14:04 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 18:31 bug#9054: 24.0.50; show source in other window Florian Beck
2011-07-12 8:21 ` martin rudalics
2011-08-31 16:52 ` Juri Linkov
2011-09-01 0:26 ` martin rudalics
2021-09-07 18:12 ` Lars Ingebrigtsen
2021-09-07 19:11 ` martin rudalics
2021-09-07 19:17 ` Lars Ingebrigtsen
2021-09-08 8:29 ` martin rudalics
2021-09-08 10:30 ` Lars Ingebrigtsen
2021-09-09 8:34 ` martin rudalics
2021-09-09 13:13 ` Lars Ingebrigtsen
2021-09-10 8:34 ` martin rudalics
2021-09-22 21:20 ` Arthur Miller
2021-09-23 8:16 ` martin rudalics
2021-09-23 12:52 ` Arthur Miller
2021-09-26 9:10 ` martin rudalics
2021-09-26 14:04 ` Arthur Miller [this message]
2021-09-09 17:20 ` Juri Linkov
2021-09-10 10:21 ` Lars Ingebrigtsen
2021-09-10 16:15 ` Juri Linkov
2021-09-11 8:38 ` martin rudalics
2021-09-11 18:51 ` Juri Linkov
2021-09-13 8:02 ` martin rudalics
2021-09-13 17:57 ` Juri Linkov
2021-09-13 18:43 ` Juri Linkov
2021-09-15 9:28 ` martin rudalics
2021-09-15 16:07 ` Juri Linkov
2021-09-15 18:48 ` martin rudalics
2021-09-17 7:21 ` Juri Linkov
2021-09-17 7:39 ` martin rudalics
2021-09-17 16:04 ` Juri Linkov
2021-09-18 7:36 ` martin rudalics
2021-09-18 16:30 ` bug#9054: [External] : " Drew Adams
2021-09-19 16:20 ` Juri Linkov
2021-09-19 17:27 ` Eli Zaretskii
2021-09-19 17:35 ` bug#9054: [External] : " Drew Adams
2021-09-19 17:43 ` Eli Zaretskii
2021-09-20 8:21 ` martin rudalics
2021-09-20 14:11 ` bug#9054: [External] : " Drew Adams
2021-09-21 8:32 ` martin rudalics
2021-09-21 17:52 ` Drew Adams
2021-09-22 7:49 ` martin rudalics
2021-09-22 15:17 ` Drew Adams
2021-09-22 15:43 ` martin rudalics
2021-09-22 16:09 ` Drew Adams
2021-09-22 16:18 ` Eli Zaretskii
2021-09-22 16:49 ` Drew Adams
2021-09-22 17:30 ` Eli Zaretskii
2021-09-22 18:22 ` Drew Adams
2021-09-22 18:42 ` Eli Zaretskii
2021-09-20 8:21 ` martin rudalics
2021-09-20 15:20 ` Juri Linkov
2021-09-21 8:34 ` martin rudalics
2021-09-21 18:05 ` Juri Linkov
2021-09-22 7:48 ` martin rudalics
2021-09-22 17:10 ` Juri Linkov
2021-09-23 8:15 ` martin rudalics
2021-09-23 15:46 ` Juri Linkov
2021-09-26 9:10 ` martin rudalics
2021-09-23 8:51 ` martin rudalics
2021-09-23 16:33 ` Juri Linkov
2021-09-26 9:11 ` martin rudalics
2021-09-29 17:47 ` Juri Linkov
2021-09-30 16:18 ` martin rudalics
2021-10-03 17:36 ` Juri Linkov
2021-10-04 8:28 ` martin rudalics
2021-10-04 17:28 ` Juri Linkov
2021-10-05 8:09 ` martin rudalics
2021-09-14 11:07 ` Lars Ingebrigtsen
2021-09-15 9:28 ` martin rudalics
2021-09-15 9:30 ` Lars Ingebrigtsen
2021-09-15 9:42 ` martin rudalics
2021-10-23 0:46 ` Stefan Kangas
2021-09-15 9:27 ` martin rudalics
2021-09-15 16:05 ` Juri Linkov
2021-09-15 18:47 ` martin rudalics
2021-09-16 18:53 ` Juri Linkov
2021-09-16 19:11 ` Juri Linkov
2021-09-17 7:39 ` martin rudalics
2021-09-17 16:05 ` Juri Linkov
2021-09-18 7:35 ` martin rudalics
2021-09-11 8:35 ` martin rudalics
2021-09-11 12:43 ` Lars Ingebrigtsen
2021-09-11 16:42 ` martin rudalics
2021-09-13 7:50 ` Lars Ingebrigtsen
2021-09-13 8:10 ` martin rudalics
2021-09-22 20:43 ` Arthur Miller
2021-09-23 8:16 ` martin rudalics
2021-09-23 12:49 ` Arthur Miller
2021-09-26 9:09 ` martin rudalics
2021-09-26 13:56 ` Arthur Miller
2022-05-02 9:31 ` Lars Ingebrigtsen
2022-05-02 16:05 ` Juri Linkov
2022-05-03 10:29 ` Lars Ingebrigtsen
2022-05-03 17:25 ` Juri Linkov
2022-05-03 18:03 ` Lars Ingebrigtsen
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=AM9PR09MB497719E0E42117567C027B0196A69@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=9054@debbugs.gnu.org \
--cc=abstraktion@t-online.de \
--cc=larsi@gnus.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).