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#61072: How to change the length of the separation lines in eldoc, used by eglot? Date: Thu, 23 Mar 2023 21:59:21 +0000 Message-ID: <87wn37ceo6.fsf@gmail.com> References: <871qmyn51d.fsf@betli.tmit.bme.hu> <87pma3gcyw.fsf@betli.tmit.bme.hu> <87r0tq8bgp.fsf@betli.tmit.bme.hu> 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="29633"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 61072@debbugs.gnu.org, Wei-Ting Lin To: Felician Nemeth Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 24 00:04:26 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 1pfTys-0007KO-SZ for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 24 Mar 2023 00:04:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pfTyW-00062l-Mp; Thu, 23 Mar 2023 19:04:04 -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 1pfTyV-0005xr-14 for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 19:04: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 1pfTyU-0005l9-9l for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 19:04:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pfTyU-0008R6-4l for bug-gnu-emacs@gnu.org; Thu, 23 Mar 2023 19:04: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 23:04:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61072 X-GNU-PR-Package: emacs Original-Received: via spool by 61072-submit@debbugs.gnu.org id=B61072.167961260632386 (code B ref 61072); Thu, 23 Mar 2023 23:04:02 +0000 Original-Received: (at 61072) by debbugs.gnu.org; 23 Mar 2023 23:03:26 +0000 Original-Received: from localhost ([127.0.0.1]:39525 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pfTxt-0008QH-L9 for submit@debbugs.gnu.org; Thu, 23 Mar 2023 19:03:25 -0400 Original-Received: from mail-ed1-f49.google.com ([209.85.208.49]:46893) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pfTxr-0008Q1-Mg for 61072@debbugs.gnu.org; Thu, 23 Mar 2023 19:03:24 -0400 Original-Received: by mail-ed1-f49.google.com with SMTP id eg48so1108516edb.13 for <61072@debbugs.gnu.org>; Thu, 23 Mar 2023 16:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679612593; 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=jnbvJxKWop/NXhMwcML8fJjuAUOgD46m0BMc/2eYweU=; b=lUirAGT5cdSUv64AlXl2kYqOrBGA8McBidyx2wbH/jhzReKNXgPZOqwycx5k/W3joH aURBGVT6pArw9Kl0JXtg9f1HZNWj51XbNc0/IVb9Tvw71KmvEVFkWysRTYGMaw0x3fVt zyfD7Jk0y2RsH7LZZgTW96kQWUZ1ltS0zBv9nxMQM7i7t/Bq10ibmOSnfMBx++TmqeUj TBtnaR+GbWYa0/XFVuIjP5gfK7/vSL+w4D0Nb0LXWvqo37CCuaaoU/Rv5++iPapfanq9 YTiacxQ3prU9NFqO4ZwI3xyBPZuK1hcdsVPp491lOsCVRvDFlPbVjPs2YIB24/qQV8pJ Z/Cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679612593; 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=jnbvJxKWop/NXhMwcML8fJjuAUOgD46m0BMc/2eYweU=; b=vXTbW/LI7jJ4EJJQozHd70gyOWaEhPtJiE8mdVTpbb90R0qQHxi8y/JeihhWlFKIjH V0FSNYilMo0HeNpLG0FosTSz7/dSv7QroWStQrQaveTHAIcS95qrNK11mjI9gWsAy3d0 eQNTupoGLBDJZjo5zDvfGJZ5zaI6FaKS1Cyj4qNey0AA43cw7UpCKSSdKOqpWNLoRc+W 1ZRmZxxrOIKYA0F6dCe9Pkiddr8kIa1V5NlObT8H6bQiZxvJLuPLxX9d9skKclD6NJcH 9I+TlYz4bWYU4+d5PiJ61/YQvpno+ZrOJOMKXX1RLB04+TdVB+Bo7rlYyt0Vkk9Kv2Qu 3C/w== X-Gm-Message-State: AAQBX9f/2mWzWBlk7cNTiApRC1knsTqfPe0Hd3sghEHdaW+l+UdUnzA1 LD0jdExJqjP7msRAdr8wlaxka4Q4VGI= X-Google-Smtp-Source: AKy350adWhG1so4SE+axKPAiMqjEGzEQNnOBRsAIFVZ0TcpHTry5Y4sbJemM7RnBiDEtJw/lDgaRvg== X-Received: by 2002:a17:906:b0d4:b0:932:e141:29be with SMTP id bk20-20020a170906b0d400b00932e14129bemr427097ejb.75.1679608640069; Thu, 23 Mar 2023 14:57:20 -0700 (PDT) Original-Received: from krug (87-196-72-75.net.novis.pt. [87.196.72.75]) by smtp.gmail.com with ESMTPSA id ce20-20020a170906b25400b00929fc8d264dsm9291481ejb.17.2023.03.23.14.57.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Mar 2023 14:57:19 -0700 (PDT) In-Reply-To: <87r0tq8bgp.fsf@betli.tmit.bme.hu> (Felician Nemeth's message of "Wed, 15 Mar 2023 13:07:18 +0100") 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:258486 Archived-At: Felician Nemeth writes: > Jo=C3=A3o T=C3=A1vora writes: > >> Rather, Eglot should add a markdown-capable element to >> eldoc-display-functions and hint in the documentation item >> produced by Eglot's eldoc-documentation-functions that that item >> has a markdown version (it may also have a plaintext version >> alongside), taken directly from the LSP source. The new function >> would then render the item appropriately. > > Maybe I overthink this, but I wonder if it would make sense to specify > an optional content-type argument instead of a markdown-capable element. > That way, eldoc could potentially handle raw html texts as well. > Additionally, this would support different markdown variants. And I'm > sure gnus/eww already has some helper functions that eldoc could reuse. > > References for the text/markdown content-type: > https://www.rfc-editor.org/rfc/rfc7763 > https://www.rfc-editor.org/rfc/rfc7764#section-3 This could be reasonable. I've pushed some commits to master addressing Eldoc/Eglot problems. The protocol between eldoc-documentation-functions and eldoc-display-functions is enhanced, and eldoc-display-in-doc-buffer is now more independent, which could pave the way for this kind of thing. See docstring of eldoc-documentation-functions. I stopped short of adding :content-type there. There's not much point in moving rendering from Eglot to ElDoc if the rendering is going to suck just as bad. So I think this has to be analyzed carefully. Here are some ideas: 1. Use eww to render HTML, as you suggest. But how to get that HTML? Call an external process? 2. You seem to suggest that eww can render markdown directly. Sure? 3. Lobby for markdown.el to become more render-friendly, (remove hard newlines from paragraphs, remove invisible text, etc.) 4. Make a new Markdown mode based on a tree-sitter grammar Jo=C3=A3o