From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#62029: 29.0.60; Allow users to customize eldoc buffer separator Date: Thu, 23 Mar 2023 21:33:41 +0000 Message-ID: <87355vdufe.fsf@gmail.com> References: <0C40D168-54D5-47E9-8BD8-77CFCD70B895@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36653"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 62029@debbugs.gnu.org To: Yuan Fu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 23 22:32:16 2023 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 1pfSXf-0009Kv-GJ for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 23 Mar 2023 22:32:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pfSXV-0001Rh-SO; Thu, 23 Mar 2023 17:32:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pfSXT-0001Pz-9e for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 17:32:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pfSXS-0003rS-Al for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 17:32:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pfSXS-0006Aw-13 for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 17:32:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 23 Mar 2023 21:32:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62029 X-GNU-PR-Package: emacs Original-Received: via spool by 62029-submit@debbugs.gnu.org id=B62029.167960710723711 (code B ref 62029); Thu, 23 Mar 2023 21:32:01 +0000 Original-Received: (at 62029) by debbugs.gnu.org; 23 Mar 2023 21:31:47 +0000 Original-Received: from localhost ([127.0.0.1]:39469 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pfSXD-0006AM-4R for submit@debbugs.gnu.org; Thu, 23 Mar 2023 17:31:47 -0400 Original-Received: from mail-ed1-f51.google.com ([209.85.208.51]:39921) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pfSXB-0006A3-Je for 62029@debbugs.gnu.org; Thu, 23 Mar 2023 17:31:46 -0400 Original-Received: by mail-ed1-f51.google.com with SMTP id ek18so567803edb.6 for <62029@debbugs.gnu.org>; Thu, 23 Mar 2023 14:31:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679607100; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=JIyVIsaBZdEcdkhSf/53+9D2B5dp2CD9SkdnIXgrte8=; b=X4NgAejy3Yp7XLeoYu36m/OFvnIo3oNObdyeukVeI1YkdvUNwMNadoefkYOCh2fxqH OppbosF/WK+KAQ4Ivj9acBvA9TYUDa0HDz5Cmz6yTKCy65UWBN27MDIYdF+KsZTCBDcJ Y0f88cScMkwwPhWVlXsNsmYWUMFAuIdaOFw3BGG84J2nxpVmwB1MWj7xnPtdAdxQLTOL sINtYIXFw0wbyY0tH2exBPKSJmFmef/6z5T6fUJmDeQgLgFEDf+80HZk8rnAeYDbr/xn 8UGV99Flo8dUOgDelaBMCxFL9EQt4tKp1TEQSFFhGmeM6S6oJSEX5k0/v+D/Oc2xp6+a GTvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679607100; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=JIyVIsaBZdEcdkhSf/53+9D2B5dp2CD9SkdnIXgrte8=; b=cwHy9BmXi+g7wl1QaZZevMvtB8e/rOXvD5XAOYLEfqIpjBnV54VHpjkH2eQSgWUrzD /jyB17hOyiYG+vfrFNtFWCzvyguEtaSXve8KkWEMsZEXDS1lKObmMyj2w/hlWp1pxR7S nUkB/wnSSk4estku55Dm3cgb2e5gL1xj4XtwqHgD1qy+eg8PBrhagcPPzCuBhqLnIv/o mGJzIZQPuO5n2D+O7YZ7wLauDxWUtZMykUwSwn0prXyk0b3WQMSlCL7zWCGE6icPWWwe 2aO4pnXRLAqh/rJmSz7Pci4GC61zSeNy2RISsQ0FeqXhhW0mEJL0P3FtyhjQEuJKVCYe EhJQ== X-Gm-Message-State: AAQBX9dgfyaQ8OFNm7oG/9GgvS5cTUV/92Q7QlhACdolLp6/GKd2I/Tc +uR8mnKwxPf71qcYSS7mRSbkJ95t5PU= X-Google-Smtp-Source: AKy350aDPjAenhqwtgLxwgILgIsoT80Rd5sbHdRFrmI5qDunES502ou+SooEdxp3MMwF70vGY04xvw== X-Received: by 2002:a17:907:c008:b0:8ad:51e9:cd57 with SMTP id ss8-20020a170907c00800b008ad51e9cd57mr500966ejc.49.1679607099438; Thu, 23 Mar 2023 14:31:39 -0700 (PDT) Original-Received: from krug (87-196-72-75.net.novis.pt. [87.196.72.75]) by smtp.gmail.com with ESMTPSA id a16-20020a170906245000b0093a6e9c2634sm3766063ejb.192.2023.03.23.14.31.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Mar 2023 14:31:39 -0700 (PDT) In-Reply-To: <0C40D168-54D5-47E9-8BD8-77CFCD70B895@gmail.com> (Yuan Fu's message of "Wed, 8 Mar 2023 13:28:39 -0800") 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:258483 Archived-At: Yuan Fu writes: > I agree. But in the same time, eldoc=E2=80=99s rendering should be > customizable too. If someone uses eldoc-doc-buffer and want to use > fancier separators, they should be able to. That=E2=80=99ll be easier than > writing another displayer that does everything the same as > eldoc-doc-buffer except for using a different separator. I've pushed two commits to master that address the design shortcoming I was referring to. Here they are summarized: commit e19994fe8c000b0ed2dbc667cdec26cf54356907 ElDoc: rework rendering of echo area (bug#62029) =20=20=20=20 Previously, the display function 'eldoc-display-in-echo-area' reused the same buffer as 'eldoc-display-in-doc-buffer', but that made it harder to render documentation items differently depending on the specific constraints of each display functions. commit 9b18407c7fd91313544acfb3457be5447987e20a ElDoc: remember origin backend in doc snippets (bug#62029) =20=20=20=20 This lays groundwork for discriminating between different documentation providers in ElDoc display outlets, i.e. members of eldoc-display-functions The first commit detaches eldoc-display-in-echo-area from eldoc-display-in-doc-buffer (It also allows the backend to control the display in the echo area specifically). For the purposes of this bug, it should allow eldoc-display-in-doc-buffer to more freely structure the *eldoc* buffer with separators, etc. The second commit adds a :origin cookie to each doc item passed to eldoc-display-functions. The origin is the name of the backend itself. It could allow for better separators in the *eldoc* buffer where each section is titled according to the backend that produced the documentation. So I guess what's missing for this bug is a customizable *eldoc* buffer separator with a good default value, like one of those resize-resisting horizontal separators. Also, for customization, maybe `format-spec' can be used? Jo=C3=A3o