[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50067: Context menus
From: |
Mattias Engdegård |
Subject: |
bug#50067: Context menus |
Date: |
Thu, 19 Aug 2021 16:22:39 +0200 |
18 aug. 2021 kl. 19.46 skrev Mattias Engdegård <mattiase@acm.org>:
> Yes it works for elisp, because its xref backend is simplistic enough to just
> accept the symbol given as argument. An example of a package where it doesn't
> work is merlin which is rather more sophisticated and wants to find the exact
> context so that it can find the right definition, so it ignores the argument.
Having actually read the doc strings I see that xref backends are supposed to
define `xref-backend-identifier-at-point` which can stuff any information it
needs in a property of the string it returns, as sort of a semi-covert channel
to `xref-backend-definitions` etc. Sorry about the unfounded complaint.
Would adding `xref-find-references-at-mouse` be handy for use in the context
menu?
- bug#50067: Context menus, (continued)
bug#50067: Context menus, Naoya Yamashita, 2021/08/28
bug#50067: Context menus, Juri Linkov, 2021/08/18
- bug#50067: Context menus, Mattias Engdegård, 2021/08/18
- bug#50067: Context menus, Tak Kunihiro, 2021/08/21
- bug#50067: Context menus, Tak Kunihiro, 2021/08/21
- bug#50067: Context menus, Juri Linkov, 2021/08/22
- bug#50067: Context menus, Tak Kunihiro, 2021/08/22
- bug#50067: Context menus, Juri Linkov, 2021/08/23
- bug#50067: Context menus, Tak Kunihiro, 2021/08/24
- bug#50067: Context menus, Juri Linkov, 2021/08/24