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: Mon, 31 Aug 2020 23:03:37 +0300 Message-ID: <60560e93-40e8-b7bf-1339-fbd48c792588@yandex.ru> 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> 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="28054"; 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 Mon Aug 31 22:04: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 1kCq2F-0007BS-61 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 31 Aug 2020 22:04:11 +0200 Original-Received: from localhost ([::1]:49074 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kCq2E-0007Y8-87 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 31 Aug 2020 16:04:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59078) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kCq26-0007Xj-Jk for bug-gnu-emacs@gnu.org; Mon, 31 Aug 2020 16:04:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42228) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kCq26-0000PQ-9d for bug-gnu-emacs@gnu.org; Mon, 31 Aug 2020 16:04:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kCq26-0001xX-4u for bug-gnu-emacs@gnu.org; Mon, 31 Aug 2020 16:04:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 31 Aug 2020 20:04:02 +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.15989042297507 (code B ref 43103); Mon, 31 Aug 2020 20:04:02 +0000 Original-Received: (at 43103) by debbugs.gnu.org; 31 Aug 2020 20:03:49 +0000 Original-Received: from localhost ([127.0.0.1]:53774 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kCq1t-0001x0-6R for submit@debbugs.gnu.org; Mon, 31 Aug 2020 16:03:49 -0400 Original-Received: from mail-lj1-f180.google.com ([209.85.208.180]:46233) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kCq1p-0001wi-Af for 43103@debbugs.gnu.org; Mon, 31 Aug 2020 16:03:47 -0400 Original-Received: by mail-lj1-f180.google.com with SMTP id h19so8118210ljg.13 for <43103@debbugs.gnu.org>; Mon, 31 Aug 2020 13:03:45 -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=gSyaLg0nY/pP8JVqK4Vd7JI+RWS2rvtmB/E9ytCxNvY=; b=W8xOf1DtPhCf9uZqfW6oEJ33H8hjSCYP+5qbK+6w8pVGMxZLwsKQjQosT/03mqIMeK Y6/kp7gU2cBBoUQyjr3tvLH0NjvVmQsoHeUu0Npzn/XtSx6I0aQ8y/AOck+x5K0vxA70 ZmDecwCyGETKaP9dE2xp9WHiW5i7BKrUTHafoFCtTnCXuIFgwKurGpi8avRK600w/Jcg Xp5CMfLFMJtZl0fcSRNIznP6rYR508RQjOq0ftdQAgSzJEg0X6ER8JvlCNstowcoxSVE r3xiEH+4GjdouXBk0zroD/RolC6IloRrYKde4aYdGwo5m//fQgnN2OKsG+u9BlqPwvLG Cj+A== 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=gSyaLg0nY/pP8JVqK4Vd7JI+RWS2rvtmB/E9ytCxNvY=; b=AHHvpHzn06Y4CW2dD92kv9Aztoewx99UxbUTFeFatibdgNIbS2A4rnXrwVTz2T3Zkx fmDH3dQzdprHYB5zCEZsBI1vfpoE0eRdi9od47w+Qhv3umNjihgoJfLmjprIW0uv53iV voHm15qcEVNU3cX4ii1Z9c/UnjICCqvaffLj2+OhOnOWbp02weIen2xVxMK7vklJ2yLi cytUChiF+bNyuJjbyI5XjOMECYymDixdJUMPVCgVVHXnpybnmGWjwCmeD7Ve5NT+sagI WiSmN0YWisGVwDz2ive6HE+Qjz46YVK/FJ/J3805ixG+v7gDrJRr/YCI3NcGKeb0VUm7 sBdA== X-Gm-Message-State: AOAM532IFgFAkHGNbmr6nt7ueecFEeOn4lcyJC+1Ccwjt5t2BYUDUSg+ Ob4TbwSqtuueTZKGVdLzT60= X-Google-Smtp-Source: ABdhPJx59IuAVckjZ4AVG9ON547kG+7OqWGiyy0l4v7o32Ry+v+PfTptsdn4BT+8/KNnLUmEMUsuHg== X-Received: by 2002:a2e:9a93:: with SMTP id p19mr1316349lji.67.1598904219010; Mon, 31 Aug 2020 13:03:39 -0700 (PDT) Original-Received: from [192.168.0.104] ([94.229.108.16]) by smtp.googlemail.com with ESMTPSA id d2sm1799496ljo.126.2020.08.31.13.03.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 31 Aug 2020 13:03:38 -0700 (PDT) In-Reply-To: <87sgc3gqh0.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:186795 Archived-At: On 31.08.2020 11:38, João Távora wrote: >> It's true, but the curious reality is that AFAIK the built-in eldoc >> functions (foremost, the Elisp one) have always used the one-line >> display, even when they could show more. >> >> These is definite wisdom in that. > > I see only signs of rudimentary intial design which predates > eldoc-...-multiline-p, composition, Flymake... That doesn't mean the initial design didn't get something right. If it didn't, this aspect would have likely changed by now. >> Change the default in eldoc.el. Why emacs-lisp-mode? > > See subject line. Having a major mode exhibit a different behavior WRT eldoc strategy is bound to be confusing. E.g., why Elisp and not Python? Why not the rest? >> One would probably prefer to see the description of the compilation >> error rather than the function signature, if they had to choose. > > Maybe you would, you can adjust it. I'd rather not change more defaults > than the one suggested in the subject line. If it's for emacs-lisp-mode only, it's already not "changing the default". >>> - even if eldoc-echo-area-use-multiline-p is set to nil, users can still >>> get to all the info collecte by ElDoc with the new >>> `eldoc-documentation-compose` strategy by pressing M-x eldoc-doc-buffer >> >> Is that the only benefit? > > No. Any others? >> This command is pretty odd in its design. But if its main purpose was >> to show multiple eldoc results together > > It's similar to `help-buffer`, but also switches to the buffer when > called interactively. I don't see anything odd in that, in Emacs terms. It's odd to use basically the same presentation for the buffer as the one for the echo area. The echo area is smaller in size, and has undesirable side-effects when its contents change height. A buffer doesn't have these kind of constraints. And if we were to differentiate the buffer's presentation (for instance, by binding eldoc-echo-area-use-multiline-p to t inside eldoc-print-current-symbol-info's interactive clause), we might as well use a different strategy for it, too. > The command pops a window to *eldoc ...*, a less restricted view into > the continuously composed results of ElDoc collection, the echo area > being a much more restricted outlet. In the future, there could/should > be an arbitrary number of such outlets: windows, frames, tooltips, some > more restrictive, some less, some more interactive, some less. Some of these have different constraints, too. > This is beyond the scope of this bug, though. You brought it up.