all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17091@debbugs.gnu.org, Thierry Volpiatto <thierry.volpiatto@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	[thread overview]
Message-ID: <87fuwiomdq.fsf@gnus.org> (raw)
In-Reply-To: <8338i61e5a.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Mar 2014 17:39:13 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Thierry Volpiatto <thierry.volpiatto@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





      reply	other threads:[~2016-02-24  2:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  6:03 bug#17091: 24.3.50; Info-index doesn't call its completing-read in current-buffer Thierry Volpiatto
2014-03-25 15:39 ` Eli Zaretskii
2016-02-24  2:47   ` Lars Ingebrigtsen [this message]

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=87fuwiomdq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=17091@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=thierry.volpiatto@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.