From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#27427: 26.0.50; Native line numbers lead to display error in company-mode popup Date: Sat, 01 Jul 2017 14:59:55 +0300 Message-ID: <83podkpdtw.fsf@gnu.org> References: <611468a0-3115-813a-7347-d0c06e155831@web.de> <83h8zawvih.fsf@gnu.org> <00f59a24-2d80-ca47-b6f3-3d219aa5aa3f@yandex.ru> <8360fqvz9x.fsf@gnu.org> <6aa4616d-79f7-db1b-c048-076a9a48596f@yandex.ru> <83tw39urzq.fsf@gnu.org> <4c4b873b-2bec-1c12-82f5-325b558bea93@yandex.ru> <83o9tgul6h.fsf@gnu.org> <49b431fd-aaa4-e7ca-06fc-7146a0a5692c@yandex.ru> <83a84zul0d.fsf@gnu.org> <513eca6f-998a-a937-76c4-7cf2fb0ff787@yandex.ru> <83wp81u8rz.fsf@gnu.org> <8ec1b301-79dc-7d11-b3f9-85ae2e925785@yandex.ru> <594FDDC5.6040009@gmx.at> <83zicwrkmu.fsf@gnu.org> <5950C342.7010908@gmx.at> <83mv8ussb6.fsf@gnu.org> <595203DE.1040608@gmx.at> <837ezxsd02.fsf@gnu.org> <59527971.5000205@gmx.at> <83y3sdqtto.fsf@gnu.org> <59536CA6.10608@gmx.at> <83r2y4qcs1.fsf@gnu.org> <5953F706.7080405@gmx.at> <83o9t8q6u1.fsf@gnu.org> <5954A995.9@gmx.at> <83d19mrc3d.fsf@gnu.org> <59560B86.4030600@gmx.at> <8337ahrf9w.fsf@gnu.org> <59577A15.6010209@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1498910473 32369 195.159.176.226 (1 Jul 2017 12:01:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 1 Jul 2017 12:01:13 +0000 (UTC) Cc: alexanderm@web.de, 27427@debbugs.gnu.org, dgutov@yandex.ru To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jul 01 14:01:08 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dRH5H-000852-HY for geb-bug-gnu-emacs@m.gmane.org; Sat, 01 Jul 2017 14:01:07 +0200 Original-Received: from localhost ([::1]:54119 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRH5M-00059Y-MG for geb-bug-gnu-emacs@m.gmane.org; Sat, 01 Jul 2017 08:01:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35963) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRH5G-00059E-PZ for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2017 08:01:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dRH5C-0001XU-BR for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2017 08:01:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:44288) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dRH5C-0001X9-4C for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2017 08:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dRH5B-00070O-P9 for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2017 08:01:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 01 Jul 2017 12:01:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27427 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 27427-submit@debbugs.gnu.org id=B27427.149891042126876 (code B ref 27427); Sat, 01 Jul 2017 12:01:01 +0000 Original-Received: (at 27427) by debbugs.gnu.org; 1 Jul 2017 12:00:21 +0000 Original-Received: from localhost ([127.0.0.1]:46965 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dRH4W-0006zP-Po for submit@debbugs.gnu.org; Sat, 01 Jul 2017 08:00:21 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:44285) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dRH4U-0006zD-Vr for 27427@debbugs.gnu.org; Sat, 01 Jul 2017 08:00:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dRH4L-0000PL-GI for 27427@debbugs.gnu.org; Sat, 01 Jul 2017 08:00:13 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55857) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRH4L-0000P8-Dq; Sat, 01 Jul 2017 08:00:09 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2483 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dRH4I-0006py-Ko; Sat, 01 Jul 2017 08:00:07 -0400 In-reply-to: <59577A15.6010209@gmx.at> (message from martin rudalics on Sat, 01 Jul 2017 12:31:49 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.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" Xref: news.gmane.org gmane.emacs.bugs:134070 Archived-At: > Date: Sat, 01 Jul 2017 12:31:49 +0200 > From: martin rudalics > CC: dgutov@yandex.ru, alexanderm@web.de, 27427@debbugs.gnu.org > > > My idea was that these windows would be "special", in that they could > > only display some special buffer or maybe only a string. > > Then we are back at my earlier ‘tty-popup-frames’ proposal with > "windows" substituting "frames". Please lets call these objects > "popups" for now. OK. > > About the > > only function we'd need is to set the coordinates where such a window > > will be displayed. Everything else, including the dimensions, will be > > determined by the text to be displayed there. > > We'd have to decide when to call the function that sets the coordinates. I hoped the application would do that, via some new API. > For that purpose each popup would probably have to store the window it > originated from to handle scrolling of that window and any changes to > its buffer. That could be one way, but maybe we could use something more direct.