From: "João Távora" <joaotavora@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 44629@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#44629: 28.0.50; Eglot noisy with gfm-view-mode and view-read-only
Date: Sun, 15 Nov 2020 23:14:19 +0000 [thread overview]
Message-ID: <CALDnm526_zNhkwFOUKVY+A7_J6wE3==XLChuRDU8xCRudwCy0Q@mail.gmail.com> (raw)
In-Reply-To: <87tutqi8yv.fsf@tcd.ie>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
On Sun, Nov 15, 2020 at 9:52 PM Basil L. Contovounesios <contovob@tcd.ie>
wrote:
> The selectivity is that I want the "View mode: ..." message to appear
> most of the time, except not when Eglot is doing background processing.
Exactly. Or any type of background processing, for that matter.
So, if this is a principle, the check for `this-command`, as I proposed
it in a patch,should suffice
This doesn't change the fact that jsonrpc.el's use of `read-only-mode`
should probably be replaced by a simple setting of buffer-read-only,
but it could avoid the change to eglot when it calls `gfm-view-mode`.
Though maybe that change could be there, too.
João
[-- Attachment #2: Type: text/html, Size: 911 bytes --]
next prev parent reply other threads:[~2020-11-15 23:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 10:58 bug#44629: 28.0.50; Eglot noisy with gfm-view-mode and view-read-only Basil L. Contovounesios
2020-11-14 11:15 ` Basil L. Contovounesios
2020-11-14 12:02 ` Eli Zaretskii
2020-11-14 12:26 ` Basil L. Contovounesios
2020-11-14 14:46 ` Eli Zaretskii
2020-11-14 15:13 ` João Távora
2020-11-15 20:27 ` Juri Linkov
2020-11-15 21:52 ` Basil L. Contovounesios
2020-11-15 23:14 ` João Távora [this message]
2020-11-17 20:15 ` Basil L. Contovounesios
2020-11-17 20:21 ` Basil L. Contovounesios
2020-11-17 22:55 ` João Távora
2020-11-28 21:27 ` Basil L. Contovounesios
2020-11-29 10:36 ` Lars Ingebrigtsen
2020-12-03 15:26 ` Basil L. Contovounesios
2020-11-16 9:14 ` Juri Linkov
2020-11-14 13:47 ` João Távora
2020-11-14 17:13 ` Basil L. Contovounesios
2020-11-15 9:55 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALDnm526_zNhkwFOUKVY+A7_J6wE3==XLChuRDU8xCRudwCy0Q@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=44629@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=juri@linkov.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).