unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Pedro A. Aranda" <paaguti@gmail.com>,
	"João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Restore emacs-29.1 eglot behaviour on master
Date: Thu, 22 Feb 2024 15:39:40 +0200	[thread overview]
Message-ID: <86ttm01uub.fsf@gnu.org> (raw)
In-Reply-To: <ccede0b6-6afd-40d4-9eba-142c2823027b@gmail.com> (paaguti@gmail.com)

> Date: Sun, 18 Feb 2024 07:36:46 +0100
> From: "Pedro A. Aranda" <paaguti@gmail.com>
> 
> Hi
> 
> I've been having massive problems with eglot on master. I understand 
> evolution, being on master, etc. but this is taking too much time now 
> <sigh> and some LSP implementers understand but others don't even react...
> 
> I'm mainly working with Python and LaTeX and this is my eglot config:
> 
>    (setq-default eglot-workspace-configuration
>                  '(:pylsp
>                    (:configurationSources ["pycodestyle"]
>                     :plugins (:autopep8 (:enabled t)
>                               :jedi_completion (:include_params t
>                                                 :eager t
>                                                 :fuzzy :json-false)
>                               :flake8      (:enabled :json-false)
>                               :pylint      (:enabled :json-false)
>                               :pycodestyle (:enabled :json-false)
>                               :pyflakes    (:enabled t)
>                               :mccabe      (:enabled t ;; boolean: true 
> (default) or false
>                                             :threshold 45)))
>                    :texlab
>                    (:completion (:matcher "prefix"))))
> 
> What I have learnt:
> 
> On emacs-29, the section relating to the LSP that is used when on a 
> specific buffer (and only that) is sent tp the LSP. And everything woks 
> as expected
> 
> On emacs-30. the full configuration is sent. That confuses the LSP 
> servers and they start working with the default configuration, which is 
> sometimes of little help.
> 
> Could the original behaviour be (re)implemented in master, please
> 
> Thanks a ton in advance,

João, any comments or suggestions?

Thanks.



  parent reply	other threads:[~2024-02-22 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  6:36 Restore emacs-29.1 eglot behaviour on master Pedro A. Aranda
2024-02-18 12:20 ` Dmitry Gutov
2024-02-22 13:39 ` Eli Zaretskii [this message]
2024-02-22 14:02   ` 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=86ttm01uub.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=paaguti@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 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).