From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: A plea for sanity from a frustrated hacker.
Date: Sun, 10 Jun 2007 17:28:48 +0300 [thread overview]
Message-ID: <874plfantf.fsf@jurta.org> (raw)
In-Reply-To: <jwvwsyc7akb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat\, 09 Jun 2007 23\:29\:29 -0400")
>> BTW, I have another frustration with this function. I like to view
>> the Help buffer and visit source code from it in the *same* window.
>> The former is achieved by
>
>> (add-hook 'same-window-regexps "\\*Help\\*\\(\\|<[0-9]+>\\)")
>
>> But the latter is impossible since as can be seen in code above
>> `help-function-def' calls the function `pop-to-buffer' which displays
>> the source code buffer in a different window.
>
> For what it's worth, I'd hate the behavior you like.
> So I don't think the code is wrong because the behavior should not be
> determined by the code but by user preferences. I.e. the problem is that
> the behavior of pop-to-buffer is not yet configurable enough.
That's exactly what I meant. pop-to-buffer doesn't allow configuring its
behavior to display the source buffer in the same Help window. I don't argue
for changing its default behavior.
How about adding a new user option, e.g `same-window-regexps-from'?
By analogy with `same-window-regexps' it will contain a list of regexps
saying that displaying a buffer from these buffers should appear in the
same window.
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2007-06-10 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 17:41 A plea for sanity from a frustrated hacker Alan Mackenzie
2007-06-09 16:29 ` Thien-Thi Nguyen
2007-06-09 17:59 ` Johan Bockgård
2007-06-09 20:20 ` Alan Mackenzie
2007-06-09 22:45 ` Juri Linkov
2007-06-10 3:29 ` Stefan Monnier
2007-06-10 14:28 ` Juri Linkov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874plfantf.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.