From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#43103: 28.0.50; Default ElDoc composition strategy in Elisp mode (eldoc-documentation-strategy) Date: Tue, 1 Sep 2020 13:52:00 +0300 Message-ID: References: <87h7sla2gc.fsf@gmail.com> <83wo1hxx4c.fsf@gnu.org> <87r1rpigff.fsf@gmail.com> <83tuwlxqow.fsf@gnu.org> <87k0xhi51w.fsf@gmail.com> <83blisxl9o.fsf@gnu.org> <878sdwi2ra.fsf@gmail.com> <87sgc3gqh0.fsf@gmail.com> <60560e93-40e8-b7bf-1339-fbd48c792588@yandex.ru> <873642k1fg.fsf@gmail.com> <59d878fc-98e0-26c3-e568-239638f54962@yandex.ru> <87wo1eikpi.fsf@gmail.com> <84b1d158-8f97-3b79-91cf-22ab2cb58e9c@yandex.ru> <87sgc2ig63.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3646"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 Cc: 43103@debbugs.gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca To: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Sep 01 12:53:11 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kD3uY-0000qW-Bw for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 01 Sep 2020 12:53:10 +0200 Original-Received: from localhost ([::1]:38912 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kD3uX-0003dW-EN for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 01 Sep 2020 06:53:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kD3uQ-0003cl-4g for bug-gnu-emacs@gnu.org; Tue, 01 Sep 2020 06:53:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43667) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kD3uP-0003Mn-SQ for bug-gnu-emacs@gnu.org; Tue, 01 Sep 2020 06:53:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kD3uP-0001em-O5 for bug-gnu-emacs@gnu.org; Tue, 01 Sep 2020 06:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 01 Sep 2020 10:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43103 X-GNU-PR-Package: emacs Original-Received: via spool by 43103-submit@debbugs.gnu.org id=B43103.15989575316308 (code B ref 43103); Tue, 01 Sep 2020 10:53:01 +0000 Original-Received: (at 43103) by debbugs.gnu.org; 1 Sep 2020 10:52:11 +0000 Original-Received: from localhost ([127.0.0.1]:55213 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kD3tb-0001df-7G for submit@debbugs.gnu.org; Tue, 01 Sep 2020 06:52:11 -0400 Original-Received: from mail-lf1-f52.google.com ([209.85.167.52]:37930) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kD3tY-0001dR-BE for 43103@debbugs.gnu.org; Tue, 01 Sep 2020 06:52:09 -0400 Original-Received: by mail-lf1-f52.google.com with SMTP id y11so503581lfl.5 for <43103@debbugs.gnu.org>; Tue, 01 Sep 2020 03:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=A31Kek3VhhE2V8xbLKQ6pmRSEQhf77wjkFRvW6ukSrk=; b=vJtakL31nwnN5PxD4f5xaeJODyWj70+7ZrZC+VUEJwX+2HdPOEhJ77J1dw8nzswIO1 ClEMVRHajhpZtiy58H5AMpO54koipVXjz08WT9PHDcQBH7y8NotWLcVqfl3FYCrYWubp zaZmu/yDjxiPlEDHdrxJn4bTsbGG0OcscHzMLPYc5+vKVMm5Eaqt+NfccTxoEWZc5kYa lbxvlhoU3eO9M0U+5c7IfYMcGvD9JywvEwdRN5ZIxhQ2e0CY/vQk7KcDXEyO2jN8Zv1H Wt0AmL9l2C010oErmX3liH6T5lDvHrSJ3gncnKtcmgUbaIHr0Pebj7axfjZW5T/+FmnJ /FSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=A31Kek3VhhE2V8xbLKQ6pmRSEQhf77wjkFRvW6ukSrk=; b=CtPWyP+6Kw5MzLChJUxknkCxtOXP7Wk8hcKZ9eQbaK9yrQX+Tp4BD8UOiWNaTgNedf v4dzIzrWrgwFDUcT+to6fNWvyQAJZhwTyYA9q6INljQ4nrgseT0yx/yfxdBl54SRs2c9 fTHGsr7rM0bUlQ7Dka6G9JbiilLGiDxbcd4UuybwvsUdhMORGje8clWWX3qhGMJs4LsO GrwNt7MBQ3qH1Arq+p86K6bmZy/v9Kq6NwqnTgs/ft28VRpDYD3FMqkGBN7GXIRiPEW3 je59bG+fh7FmSt8TYVWWiUxY1YUEnvVKLyLPKJVlY31aP1aBGsU9CvXUhiFt0nZm86ka w32A== X-Gm-Message-State: AOAM530ql0uKL+GPYvIx2hqP2P0xH/wxIgwUBo/iacgW/GmE/TWTQX8M TcHymrUuxluT+UrqU1064Tg= X-Google-Smtp-Source: ABdhPJyZx2ZAsrX/Icx1SH3nG6FtrUq63Zb6r9/dtZyuosyMWZJSzGBlfZfhbyT14gW/2TzH1smP+A== X-Received: by 2002:a05:6512:3143:: with SMTP id s3mr310512lfi.154.1598957522119; Tue, 01 Sep 2020 03:52:02 -0700 (PDT) Original-Received: from [192.168.0.104] ([94.229.108.16]) by smtp.googlemail.com with ESMTPSA id y5sm194867lfy.88.2020.09.01.03.52.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Sep 2020 03:52:01 -0700 (PDT) In-Reply-To: <87sgc2ig63.fsf@gmail.com> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:186823 Archived-At: On 01.09.2020 01:50, João Távora wrote: > The echo area > has been there from ElDoc's first design, it is not one of the new tools > that ElDoc offers now. My point is -- as is well-known -- the echo area has a long-standing problem. If the message is multiline, the windows will jump. Since the echo area is still the main means of conveying Eldoc notifications, changing Eldoc behavior to multiline messages is problematic. > For your benefit, and to wrap up this exchange, here's a summary of what > I propose: In Elisp mode, I've experimented with the > `eldoc-documentation-compose` strategy and I like the results: it's > useful to have Elisp function signatures, Elisp variable documentation > and Elisp diagnostics displayed somewhere, constantly updated. Indeed. > I think > other people would like these things, hence my proposal. I don't mind > the echo area jumping in height one or two lines once in a while, I mind. Unfortunately. > but if > others do, there are tools to control it, which we can leverage to good > effect. That's it. What tools? >>>> One particular way it's unfortunate, is I actually *would* like a >>>> generic "show documentation" feature with an existing key >>>> binding. Shame it doesn't really work for that purpose. >>> Try M-x eldoc and global-set-key and tell us what's missing. >> >> Already told you. I'm not sure how many different ways I can explain >> things, if you keep snipping those explanations out. > > You said you wished for a command to "show documentation" and I pointed > you to M-x eldoc, a new command which seems to do what you want, and > that you might not be aware of since it wasn't discussed. And I told you its semantics are broken. Showing the text intended to be displayed in the echo area (one line, usually; maybe a few) in a full-size window is ridiculous. > If you don't > wish to pursue this suggestion, fine. I am in no obligation to waste my > time replying to every new off-topic point you bring up, I do so only > where I think I can add value. Bickering with you is not one of those > things. If you try actually reading what I wrote, you might find some actionable suggestions there.