unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: Just an uninformed question
Date: Sun, 22 Oct 2023 11:13:32 +0200	[thread overview]
Message-ID: <CAO48Bk9XbOjqh2XqbCGgs4LgxSxxgYZw5wkH0n5i3PU4OQW+sw@mail.gmail.com> (raw)
In-Reply-To: <83ttqjp419.fsf@gnu.org>

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

Hi Eli,

Just an example, by no means the only thing I tinker on to get something
that is comfortable (for me -TM-):

```
 "texlab" : {
  "completion" : {
    "matcher" : "prefix"
  }
},
```
I have also experienced hick-ups with pylsp and had to temporarily change
the default behaviour to be able to work.

Best, /PA


On Sun, 22 Oct 2023 at 08:25, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> > Date: Sun, 22 Oct 2023 08:09:54 +0200
> > Cc: emacs-devel <emacs-devel@gnu.org>
> >
> > +/- correct. I want to explore how difficult it would be to _add_ the
> possibility
> > of customising eglot with a JSON file in the user-emacs directory. A
> newbie
> > learning Emacs Lisp might not find it easy to configure eglot with it
> and, thus,
> > may be "tempted away" from it. The idea should be to make it easier for
> people
> > to access cool features, not to shy them away because they need a level
> of
> > ELisp knowledge they don't have (yet).
>
> What are we talking about, in practical terms?  What kind of
> customizations are needed for Eglot before the user can start using it
> with some LSP server?
>


-- 
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

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

  reply	other threads:[~2023-10-22  9:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 10:41 Just an uninformed question Pedro Andres Aranda Gutierrez
2023-10-21 11:59 ` Stefan Kangas
2023-10-22  6:09   ` Pedro Andres Aranda Gutierrez
2023-10-22  6:25     ` Eli Zaretskii
2023-10-22  9:13       ` Pedro Andres Aranda Gutierrez [this message]
2023-10-22  9:31         ` Eli Zaretskii
2023-10-22 11:26     ` Stefan Kangas
2023-10-22 14:14       ` Dmitry Gutov
2023-10-22 15:25         ` Pedro Andres Aranda Gutierrez

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=CAO48Bk9XbOjqh2XqbCGgs4LgxSxxgYZw5wkH0n5i3PU4OQW+sw@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@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).