From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#30399: 27.0.50; tooltips are broken Date: Mon, 12 Feb 2018 10:26:40 +0100 Message-ID: <5A815DD0.9090205@gmx.at> References: <87wozn9kyy.fsf@gmx.net> <5A7D6F9A.1010504@gmx.at> <5A7EBFC2.1040104@gmx.at> <0f060af6-d348-4d38-806e-a0d6d9f194ff@default> <5A800E8F.60706@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1518427549 26272 195.159.176.226 (12 Feb 2018 09:25:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Feb 2018 09:25:49 +0000 (UTC) To: Drew Adams , Stephen Berman , 30399@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 12 10:25:45 2018 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 1elAMM-0004jc-Hv for geb-bug-gnu-emacs@m.gmane.org; Mon, 12 Feb 2018 10:25:14 +0100 Original-Received: from localhost ([::1]:60395 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elAOO-0006w3-Bu for geb-bug-gnu-emacs@m.gmane.org; Mon, 12 Feb 2018 04:27:20 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55761) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elAO9-0006rL-6x for bug-gnu-emacs@gnu.org; Mon, 12 Feb 2018 04:27:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1elAO6-0001l8-AZ for bug-gnu-emacs@gnu.org; Mon, 12 Feb 2018 04:27:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59267) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1elAO6-0001ki-7T for bug-gnu-emacs@gnu.org; Mon, 12 Feb 2018 04:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1elAO5-0003zg-WF for bug-gnu-emacs@gnu.org; Mon, 12 Feb 2018 04:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 12 Feb 2018 09:27:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30399 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30399-submit@debbugs.gnu.org id=B30399.151842761615341 (code B ref 30399); Mon, 12 Feb 2018 09:27:01 +0000 Original-Received: (at 30399) by debbugs.gnu.org; 12 Feb 2018 09:26:56 +0000 Original-Received: from localhost ([127.0.0.1]:38931 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elAO0-0003zN-IN for submit@debbugs.gnu.org; Mon, 12 Feb 2018 04:26:56 -0500 Original-Received: from mout.gmx.net ([212.227.15.18]:49125) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elANy-0003zA-T0 for 30399@debbugs.gnu.org; Mon, 12 Feb 2018 04:26:55 -0500 Original-Received: from [192.168.1.101] ([46.125.250.92]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MNYxW-1esIBi2PW6-007FOJ; Mon, 12 Feb 2018 10:26:44 +0100 In-Reply-To: X-Provags-ID: V03:K0:593RPeZH2fOfOlj9CJwoUHTpxJj4RhctNDh8nrD1B6/dRM+ew7K 34Jpg4Va3JghjGZMyELq7qmSqRht6PMnPutQ48gYrjcBxkEml1J0rQCPr/LQYAvuYxhW4IS sYNWxvLgHAoo73Vp6wMqgFwxaFcMQbucy8xD+nmuO+MkLWpCEkl/yf7s0RL/Qadgu9n7Gx4 zythnF54FSnTZb/uGY2cg== X-UI-Out-Filterresults: notjunk:1;V01:K0:G2F85f2teUk=:XvqVcFw1Vm815N/zIoBSwh JR74ALirdiWYVZHbt2qmgBWigMfeGrGeJuosrdBHJpijW3Ig5RRyyQTA8SR0iDqj02sbqj26N Q5j1PSBjWeMDLF7HYGCRiZLOUXUWz27T7rSpheSddkhAjPE2MNxBklBXHhCqVuqGlAk3Lumx/ mNWR/KBQ61z7clbPmMQyuk8hLWUpjsPO2GwagIcdd189iylh82ZIDiCTi4rMV+GisTN+bzwUO 5p6/902BvsOtTIuQ1HHTOci4FpELoAc3dQNG9EcUrTJfVmomzgANlN3FxGwnnRu0lENfbFFsW NcNI3OIjOPEhCGsJR/x9oPI2OE9NaoDqwR/YBw59ehzJJCRZD82BhVh4bpLqpKZ33KSBfhs2C qi5gnjgvyqZCTeo4UiysSY9Q3/yxxX0doGfUDrAIDWr0ET7WBbGq5vAUSyF4mNyLoGdwYGQgR Y1xyccL8erGOjeuuj2JPsZjqoizStDtcWkL8pBG2lLu9rHNfLcb7wP/tl6YRovI2Cs0MRTUFX CaW9WrD6EdLowGn5kh5hiZiX3wezIwGEBA4K510JFfw9+Slu5+KKfQCnx1hECMPZw/64LfTps YnBBMYzuSTiSGm4/t1bQspecbOYLdoJ1kfOJOtKWvvSgf5wO8aqGKvVwlrStM8stuhhBnaQwp PmCrY2D6kee8FBfHOLEBJF5b4QaOHMSQfbEyhhyPvxdPj0/ui1bJKjAr8A8ndM+bvM7dsmuN9 +gTelk4ZY/0lxb2/28/WaCzcPqo5a8iz6s3HfPUoCmYDokGatbRzErIazyDa8Yu/hyoZFrxt 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:143196 Archived-At: >> That when the behavior of 'x-show-tip' changes, >> applications will have to adapt. > > That's even more vague - not a clarification at all. > What is the behavior change? What kind of adaptation > are you hinting at? That if for some reason the behavior of that function must be changed, its callers may have to change too. >> Currently there are no plans to replace 'x-show-tip' AFAICT. > > Let's not quibble over the word "replace", please. > > You imply that "the behavior of 'x-show-tip'" will > change. That's what I'm asking about, in talking > about "replacement". 'x-show-tip' had a bug that has been hopefully fixed. I did not imply anything else. > You also said that we should not use 'x-show-tip' > but should use only `tooltip-show', which is much > more limited - not a substitute for 'x-show-tip' > at all. I'm using 'x-show-tip' in my private code, so why should I say such a thing. > The question is, if `x-tool-tip' is not expected > to be replaced, but it is expected to change, just > _how_ is it expected to change? > > Will we be able to do with the "new" `x-show-tip', > what we can do with it now, even if we must "adapt" > in some way to be able to do that? Hopefully so. > You are being quite vague, it seems. You make a > pronouncement that we should not use the function, > but also that it will change - somehow. I did neither the former nor the latter. > The real question is not the words to name the > impending change or replacement that you warn us > about. > > The question is how, after the change/replacement, > to get done everything we can do now with that > function. Let's see to that when we're there. martin