GNU bug report logs - #17091
24.3.50; Info-index doesn't call its completing-read in current-buffer.

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 17091 <at> debbugs.gnu.org, Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Subject: bug#17091: 24.3.50; Info-index doesn't call its completing-read in current-buffer.
Date: Wed, 24 Feb 2016 13:47:13 +1100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
>> Date: Tue, 25 Mar 2014 07:03:12 +0100
>> 
>> when in a info buffer and calling `Info-index' ("i") the buffer
>> `Info-complete-menu-buffer' is made current just to call
>> `Info-goto-index', then the `completing-read' is called from this buffer
>> instead of beeing called from `current-buffer'.
>> This is not needed because the collection function of the
>> `completing-read' (`Info-complete-menu-item') is making the
>> `Info-complete-menu-buffer' current to compute its data.
>> 
>> In emacs, there is no problem, it is working like this, however in
>> external application like helm, it cause problems.
>> 
>> See https://github.com/emacs-helm/helm/issues/456
>
> Why is helm so sensitive to such intimate details of the
> implementation of Emacs functions?

More information was requested, but no response was given within a few
months, so I'm closing this bug report.  If the problem still exists,
please reopen this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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