From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#16347: 24.3.50; Company pseudo-tooltip refresh problem when expanded down at eob Date: Thu, 09 Jan 2014 17:23:02 +0400 Message-ID: <52CEA2B6.1080007@yandex.ru> References: <87ob3ruki6.fsf@yandex.ru> <52CCF504.8050906@yandex.ru> <83a9f6fjem.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1389273859 20267 80.91.229.3 (9 Jan 2014 13:24:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Jan 2014 13:24:19 +0000 (UTC) Cc: 16347@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jan 09 14:24:24 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W1Fax-0005Wp-Q1 for geb-bug-gnu-emacs@m.gmane.org; Thu, 09 Jan 2014 14:24:24 +0100 Original-Received: from localhost ([::1]:51941 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Fav-0007mx-7Z for geb-bug-gnu-emacs@m.gmane.org; Thu, 09 Jan 2014 08:24:21 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57582) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Fak-0007mY-1H for bug-gnu-emacs@gnu.org; Thu, 09 Jan 2014 08:24:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W1Fac-0003Sf-OL for bug-gnu-emacs@gnu.org; Thu, 09 Jan 2014 08:24:09 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:57920) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Fac-0003Sb-Ks for bug-gnu-emacs@gnu.org; Thu, 09 Jan 2014 08:24:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1W1Fab-0003vV-V0 for bug-gnu-emacs@gnu.org; Thu, 09 Jan 2014 08:24:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 09 Jan 2014 13:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16347 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16347-submit@debbugs.gnu.org id=B16347.138927379615018 (code B ref 16347); Thu, 09 Jan 2014 13:24:01 +0000 Original-Received: (at 16347) by debbugs.gnu.org; 9 Jan 2014 13:23:16 +0000 Original-Received: from localhost ([127.0.0.1]:43705 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1W1FZr-0003u9-1r for submit@debbugs.gnu.org; Thu, 09 Jan 2014 08:23:15 -0500 Original-Received: from mail-lb0-f169.google.com ([209.85.217.169]:33479) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1W1FZk-0003tq-LY for 16347@debbugs.gnu.org; Thu, 09 Jan 2014 08:23:13 -0500 Original-Received: by mail-lb0-f169.google.com with SMTP id u14so2330432lbd.0 for <16347@debbugs.gnu.org>; Thu, 09 Jan 2014 05:23:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OErzUr0xSKQVs4fw+WhwHejpdq6ZwaWKy4/B8opP8mw=; b=WjhI5Uiezuf9Gs8y/yA/Z3CN4YwG6AMjXx01czUHfbwsxYPIKnvil/eOnW64lgffOJ nyD08pqkWrWSntF9HcVPrwRMM2x+Vu17iOQkd4vmPNoGjmK6RcuAkQCTgunYNCXiP9sb 3OdIVrtgsUkcFjaMjawC63HD3doZhH4IyWXav0OkXE+mHG8tyWh8ULkhUHWyZaixQX8T XU0Ih3NuCuyJse4OtGl1DndnEfaFg9o+QMDiG/VzhaLrlM2gGIM3cjL9iS6VVgSiRYF2 la+H0mBMBCge1OeW6eWMuOd9zI+CkOv0iPdTVjLNlMy/1ZeYQLw9EOnBQg4+//fdY56j QXXg== X-Received: by 10.152.21.3 with SMTP id r3mr1256283lae.15.1389273787143; Thu, 09 Jan 2014 05:23:07 -0800 (PST) Original-Received: from [192.168.1.3] ([178.252.98.87]) by mx.google.com with ESMTPSA id di11sm1625388lac.0.2014.01.09.05.23.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 05:23:06 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <83a9f6fjem.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:83190 Archived-At: Sorry, you both. Here's the missing piece: (setq bidi-display-reordering nil) This is pretty low-level var, so maybe it's not even supposed to be set by a user. On 08.01.2014 21:55, Eli Zaretskii wrote: > I'm not Stefan, but I have problems reproducing this. Is the recipe > complete enough to start with "emacs -Q"? Obviously, there should be > a step to add the company directory to load-path, but are there any > other customizations that are necessary? Sorry, see above. > Also, the description of the problem is not entirely clear to me. By > "current candidate" do you mean the completion candidate whose line in > the pseudo-tooltip is displayed with a distinct color? Yes. > You also talk about > "summary lines shown in the echo area", but if I follow your recipe, I > see nothing in the echo area, and the *Messages* buffer confirms that > nothing was displayed there. Indeed, this only happens when a suitable backend gets enabled, and company-elisp only works in IELM buffers in the upstream Company, not yet with code in ELPA. You can try (require 'company-capf) M-x company-capf but that really doesn't matter, since it's unrelated to the bug and just indicates that the current candidate has indeed changed after you pressed M-n or M-p, and it's just overlay display that wasn't updated. > Finally, did you try with the current trunk? Your original report is > about a revision after which a fix for a similar redisplay problems > was committed, so is there any chance you are still using an outdated > trunk code? I saw that fix, but no change.