unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Just an uninformed question
Date: Sat, 21 Oct 2023 12:41:53 +0200	[thread overview]
Message-ID: <CAO48Bk9hK36WsiTh4pNfK9KW5twsU7_1vy49qC2tjpRV8KCf5Q@mail.gmail.com> (raw)

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

Hi,

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.

Just asking myself...
/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

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

             reply	other threads:[~2023-10-21 10:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 10:41 Pedro Andres Aranda Gutierrez [this message]
2023-10-21 11:59 ` Just an uninformed question 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
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=CAO48Bk9hK36WsiTh4pNfK9KW5twsU7_1vy49qC2tjpRV8KCf5Q@mail.gmail.com \
    --to=paaguti@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).