unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Just an uninformed question
Date: Sat, 21 Oct 2023 04:59:23 -0700	[thread overview]
Message-ID: <CADwFkmmwK_3p_4WepPVRuj7avShDPn3qsWXUXWmTEZuBWSHRYA@mail.gmail.com> (raw)
In-Reply-To: <CAO48Bk9hK36WsiTh4pNfK9KW5twsU7_1vy49qC2tjpRV8KCf5Q@mail.gmail.com>

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> I've been using eglot for some time now and that has implied playing around
> with different LSPs and their configurations. Before going for the "complex
> things", like project specific settings, I'm working on a one-fits-all my
> needs config and, yes, I've been writing this in elisp, which was somehow
> convoluted (and maybe not optimal for newbies).
>
> How difficult/acceptable would it be to have a e.g.
> `(locate-user-emacs-file "eglot.json")` file holding the basic one-fits-all
> configuration in JSON? This files will always be overwritten with a
> .dir-locals.el file for specific projects, of course.

Sorry, I don't understand what are you proposing.  Do you want to
customize Emacs/eglot in JSON instead of in Emacs Lisp?

Could you please clarify?



  reply	other threads:[~2023-10-21 11:59 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 [this message]
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
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=CADwFkmmwK_3p_4WepPVRuj7avShDPn3qsWXUXWmTEZuBWSHRYA@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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).