all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Felician Nemeth <felician.nemeth@gmail.com>, 61072-done@debbugs.gnu.org
Cc: Yuan Fu <casouri@gmail.com>, Wei-Ting Lin <linwaytin@gmail.com>
Subject: bug#61072: How to change the length of the separation lines in eldoc, used by eglot?
Date: Sat, 8 Apr 2023 10:10:54 +0100	[thread overview]
Message-ID: <CALDnm53KkkpyB6fp84SXeEc3xiECO0D3yzVa7JeptSrDZZT-7w@mail.gmail.com> (raw)
In-Reply-To: <87wn2mzrg5.fsf@betli.tmit.bme.hu>

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Yes, I think so. Doing that now.

On Sat, Apr 8, 2023, 09:52 Felician Nemeth <felician.nemeth@gmail.com>
wrote:

> >> https://github.com/jrblevin/markdown-mode/issues/753
>
> As the underlying problem has been fixed in mardown-mode, can we close
> this bug?
>

[-- Attachment #2: Type: text/html, Size: 655 bytes --]

  reply	other threads:[~2023-04-08  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  1:42 bug#61072: How to change the length of the separation lines in eldoc, used by eglot? Wei-Ting Lin
2023-01-26 11:12 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-27  1:08   ` Wei-Ting Lin
2023-02-09 17:05 ` Felician Nemeth
2023-02-18 15:08   ` Wei-Ting Lin
2023-02-21 17:11     ` Felician Nemeth
2023-02-21 17:19       ` João Távora
2023-03-15 12:07         ` Felician Nemeth
2023-03-23 21:59           ` João Távora
2023-03-28 15:16             ` Felician Nemeth
2023-03-28 22:27               ` João Távora
2023-03-29 17:48                 ` Felician Nemeth
2023-03-29 23:59                   ` Yuan Fu
2023-04-08  8:52                     ` Felician Nemeth
2023-04-08  9:10                       ` João Távora [this message]
2023-03-23 21:53 ` João Távora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALDnm53KkkpyB6fp84SXeEc3xiECO0D3yzVa7JeptSrDZZT-7w@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=61072-done@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=felician.nemeth@gmail.com \
    --cc=linwaytin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.