From: Juri Linkov <juri@linkov.net>
To: Felician Nemeth <felician.nemeth@gmail.com>
Cc: 33992@debbugs.gnu.org, "João Távora" <joaotavora@gmail.com>,
"Dmitry Gutov" <dgutov@yandex.ru>
Subject: bug#33992: 27.0.50; xref-find-definitions wastes too much space
Date: Sun, 07 Apr 2019 00:08:38 +0300 [thread overview]
Message-ID: <874l7a962h.fsf@mail.linkov.net> (raw)
In-Reply-To: <87lg0ou6q7.fsf@ulti.tmit.bme.hu> (Felician Nemeth's message of "Fri, 05 Apr 2019 11:44:16 +0200")
> I thought that I didn't need to see the list of the xref results and the
> xrefs' window shrank the view of the code I wanted to study. So, I came
> up with the defun below. It presents the xref results without showing
> the xref window. I think this idea can be further developed.
> xref-show--xrefs-buffer could have an 'm' key binding that "minimizes"
> its window by switching to xref-show-xrefs-without-buffer (below) and
> that function can "maximize" back with the same 'm' key. A customizable
> variable could define the initial behavior.
This looks like good ol' find-tag and tags-loop-continue bound to M-,
with an optional pop-up to the xref buffer by a dedicated key.
next prev parent reply other threads:[~2019-04-06 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 23:43 bug#33992: 27.0.50; xref-find-definitions wastes too much space Juri Linkov
2019-01-06 11:03 ` João Távora
2019-03-20 21:37 ` Juri Linkov
2019-03-20 23:23 ` João Távora
2019-04-04 0:02 ` Dmitry Gutov
2019-04-04 20:49 ` Juri Linkov
2019-04-04 23:06 ` Dmitry Gutov
2019-04-05 9:44 ` Felician Nemeth
2019-04-05 23:20 ` Dmitry Gutov
2019-04-06 21:08 ` Juri Linkov [this message]
2019-04-06 21:03 ` Juri Linkov
2019-05-02 23:05 ` Dmitry Gutov
2019-05-15 20:57 ` Juri Linkov
2019-05-15 22:37 ` Dmitry Gutov
2019-05-28 20:35 ` Juri Linkov
2019-06-10 0:35 ` Dmitry Gutov
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=874l7a962h.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33992@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=felician.nemeth@gmail.com \
--cc=joaotavora@gmail.com \
/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.