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>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Just an uninformed question
Date: Sun, 22 Oct 2023 04:26:12 -0700	[thread overview]
Message-ID: <CADwFkmkreEvYecHBd31Y-Bedz3zW33HJTWYiGNhuSugN7vJKbQ@mail.gmail.com> (raw)
In-Reply-To: <CAO48Bk-oUwa7=VOEkXxDs9Eo_069fA4xgR0fy1emDH_aeeKvOQ@mail.gmail.com>

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

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

I don't think adding another customization file format helps, because
that would just mean you'd have to learn that in addition to learning
som basic Lisp.  That makes it harder to use Emacs, not easier.

If we want to make it easier to customize Emacs without knowing Lisp, I
think the best place to start is `M-x customize' and related commands.
There is definitely a lot of room for improvement there.

See (info "(emacs) Customization").



  parent reply	other threads:[~2023-10-22 11:26 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
2023-10-22  9:31         ` Eli Zaretskii
2023-10-22 11:26     ` Stefan Kangas [this message]
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=CADwFkmkreEvYecHBd31Y-Bedz3zW33HJTWYiGNhuSugN7vJKbQ@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).