From: martin rudalics <rudalics@gmx.at>
To: "Philip K." <philipk@posteo.net>
Cc: Dmitry Gutov <dgutov@yandex.ru>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Poll: Change xref-show-definitions-function's default?
Date: Sat, 2 Jan 2021 16:43:10 +0100 [thread overview]
Message-ID: <d4579669-13a0-e11f-882f-90e240d798af@gmx.at> (raw)
In-Reply-To: <87im8ftz15.fsf@posteo.net>
> Do you mean something like this:
> https://github.com/fmdkdd/dotfiles/blob/master/emacs/.emacs.d/elisp/xref-posframe.el?
I don't know. After evaluating with emacs -Q
(progn
(load "~/temp/posframe.el")
(load "~/temp/xref-posframe.el")
(global-set-key (kbd "M-.") #'xref-posframe-dwim)
(find-file "~/emacs-git/quick/src/xdisp.c")
(re-search-forward "get_next_display_element"))
I typed M-. and after confirming the TAGS table prompt I got an *xref*
window below the xdisp.c window displaying
/home/martin/emacs-git/quick/src/xdisp.c
7244: #define GET_NEXT_DISPLAY_ELEMENT(
7396: get_next_display_element
What I expected was to show these two lines in a menu (or posframe)
right above or below the "get_next_display_element" string in xdisp.c,
allow navigation there via <up> and <down> and having <right> or <RET>
get me to the corresponding tag, simultaneously popping down the menu
(or posframe). Have I done something wrong?
In cases where there is only one definition like `set_iterator_to_next'
below, M-. first gets me a four lines frame with a short description
and then gets me to the definition as expected.
Thanks, martin
next prev parent reply other threads:[~2021-01-02 15:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 18:28 Poll: Change xref-show-definitions-function's default? Dmitry Gutov
2020-12-30 3:17 ` Lars Ingebrigtsen
2020-12-31 13:06 ` Daniel Martín
2021-01-01 12:25 ` Zhiwei Chen
2021-01-01 12:46 ` Dmitry Gutov
2021-01-01 13:33 ` Dmitry Gutov
2021-01-02 21:09 ` João Távora
2021-01-03 23:54 ` Daniel Martín via "Emacs development discussions.
2021-01-03 23:58 ` João Távora
2021-01-04 0:07 ` Dmitry Gutov
2021-01-04 8:48 ` João Távora
2021-01-04 11:16 ` Dmitry Gutov
2021-01-04 11:24 ` João Távora
2021-01-04 11:42 ` Dmitry Gutov
2021-01-01 7:59 ` martin rudalics
2021-01-01 12:17 ` Dmitry Gutov
2021-01-02 10:26 ` Philip K.
2021-01-02 15:43 ` martin rudalics [this message]
2021-01-02 17:25 ` Dmitry Gutov
2021-01-03 8:39 ` martin rudalics
2021-01-03 17:43 ` Dmitry Gutov
2021-01-02 10:24 ` Philip K.
2021-01-02 11:08 ` Dmitry Gutov
2021-01-04 12:12 ` Philip K.
2021-01-04 12:22 ` Dmitry Gutov
2021-01-04 14:21 ` Philip K.
2021-01-04 16:14 ` Dmitry Gutov
2021-01-04 17:42 ` Juri Linkov
2021-01-04 18:41 ` Dmitry Gutov
2021-01-06 18:30 ` Juri Linkov
2021-01-06 20:55 ` Dmitry Gutov
2021-01-07 17:47 ` Juri Linkov
2021-01-09 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=d4579669-13a0-e11f-882f-90e240d798af@gmx.at \
--to=rudalics@gmx.at \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.