GNU bug report logs - #53956
27.1; Make xref--current-item public

Previous Next

Package: emacs;

Reported by: Felician Nemeth <felician.nemeth <at> gmail.com>

Date: Sat, 12 Feb 2022 12:46:02 UTC

Severity: wishlist

Found in version 27.1

To reply to this bug, email your comments to 53956 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to dgutov <at> yandex.ru, bug-gnu-emacs <at> gnu.org:
bug#53956; Package emacs. (Sat, 12 Feb 2022 12:46:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Felician Nemeth <felician.nemeth <at> gmail.com>:
New bug report received and forwarded. Copy sent to dgutov <at> yandex.ru, bug-gnu-emacs <at> gnu.org. (Sat, 12 Feb 2022 12:46:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Felician Nemeth <felician.nemeth <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.1; Make xref--current-item public
Date: Sat, 12 Feb 2022 13:45:27 +0100

Severity: wishlist
thanks

Dmitry answered (to my question) in
https://github.com/joaotavora/eglot/pull/832#issuecomment-1031019256 :

> > An xref-after-jump-hook processes the last selected item
> > (xref--current-item) and gives an option to the user to execute the
> > selected command. However, xref--current-item is private. @dgutov,
> > is there another way (an api call) to get the selected xref-item?
> 
> Nope, never considered that the value would be interesting for
> extensions. You can refer to this name, but it's probably a good idea
> to rename it (with a compatibility alias, I guess). We can move this
> to the bug tracker.
Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#53956; Package emacs. (Mon, 21 Feb 2022 01:01:02 GMT) Full text and rfc822 format available.

Message #8 received at 53956 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Felician Nemeth <felician.nemeth <at> gmail.com>, 53956 <at> debbugs.gnu.org
Subject: Re: bug#53956: 27.1; Make xref--current-item public
Date: Mon, 21 Feb 2022 03:00:34 +0200

On 12.02.2022 14:45, Felician Nemeth wrote:
> Severity: wishlist
> thanks
> 
> Dmitry answered (to my question) in
> https://github.com/joaotavora/eglot/pull/832#issuecomment-1031019256 :
> 
>>> An xref-after-jump-hook processes the last selected item
>>> (xref--current-item) and gives an option to the user to execute the
>>> selected command. However, xref--current-item is private. @dgutov,
>>> is there another way (an api call) to get the selected xref-item?
>>
>> Nope, never considered that the value would be interesting for
>> extensions. You can refer to this name, but it's probably a good idea
>> to rename it (with a compatibility alias, I guess). We can move this
>> to the bug tracker.

Thanks for the report, now done on master (3d2c213ce9).

Should be in the next update, 1.4.0.
This bug report was last modified 3 years and 117 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.