From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Stefan Kangas <stefankangas@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Just an uninformed question
Date: Sun, 22 Oct 2023 17:25:30 +0200 [thread overview]
Message-ID: <CAO48Bk8GtSt1uzcEW=ZSb1krg_qP9Hfj4d+Xr5JQDBkjkO-Nfw@mail.gmail.com> (raw)
In-Reply-To: <f3eb237c-6951-a656-4979-c5cb2bcaf001@gutov.dev>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
Dmitry wrote:
>It might help if the said format is similar enough to some configuration
>snippets floating around for VS Code, for example.
That may be the point I was looking for ;-) Some of my students went for
VSCode just for that reason
/PA
On Sun, 22 Oct 2023 at 16:14, Dmitry Gutov <dmitry@gutov.dev> wrote:
> On 22/10/2023 14:26, Stefan Kangas wrote:
> > 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.
>
> It might help if the said format is similar enough to some configuration
> snippets floating around for VS Code, for example.
>
--
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: 1593 bytes --]
prev parent reply other threads:[~2023-10-22 15:25 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
2023-10-22 14:14 ` Dmitry Gutov
2023-10-22 15:25 ` Pedro Andres Aranda Gutierrez [this message]
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='CAO48Bk8GtSt1uzcEW=ZSb1krg_qP9Hfj4d+Xr5JQDBkjkO-Nfw@mail.gmail.com' \
--to=paaguti@gmail.com \
--cc=dmitry@gutov.dev \
--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).