unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Re: Explain a bit more on how to configure language server in Eglot's manual
Date: Sun, 12 Mar 2023 13:09:24 +0100	[thread overview]
Message-ID: <CAO48Bk8Kyp7mjT29wkygaMqqt47PdV6hkaD8Lv=z205G1bcPBw@mail.gmail.com> (raw)

Hi Joao,

I've been looking at the write-eglot-manual-for-advanced-server-config
branch in savannah and it looks great.
 My .2 cents to it is that would be great if you included something in
the line of

----- cut here -------
You can create a basic eglot configuration to use (by default) in most
of your projects in your Emacs initialisation like below:

  (setq-default eglot-workspace-configuration
                '(:pylsp
                  (:configurationSources ["pycodestyle"]
                   :plugins
                   (:mccabe (:threshold 30)))
                  :gopls
                  (:usePlaceholders t)))

and then use .dir-locals.el for a project or directory that needs
specific settings.
----- cut here -------

That would cover sone newbie questions.

In addition to this, it would also be nice to document a 'canonical'
way to disable/customise the mouse code actions. If I use something,
it's just the import organiser in Python... Disabling it, moving it to
another binding would be great.

TIA, /PA

-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should
run a leader-deposed hook here, but we can't yet



             reply	other threads:[~2023-03-12 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 12:09 Pedro Andres Aranda Gutierrez [this message]
2023-03-12 19:52 ` Explain a bit more on how to configure language server in Eglot's manual 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='CAO48Bk8Kyp7mjT29wkygaMqqt47PdV6hkaD8Lv=z205G1bcPBw@mail.gmail.com' \
    --to=paaguti@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@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).