unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: summeremacs@summerstar.me,  emacs-devel@gnu.org
Subject: Re: Emacs Newbie Info Pages
Date: Fri, 13 Sep 2024 07:36:15 +0000	[thread overview]
Message-ID: <87ldzw3t00.fsf@posteo.net> (raw)
In-Reply-To: <86seu4jbto.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Sep 2024 09:40:35 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 12 Sep 2024 19:17:51 +0000
>> 
>> I guess we are thinking of different kinds of newbies here.  That being
>> said, an experiment I have been thinking about but haven't implemented
>> yet is a .ini-parser for Emacs that could load a Emacs configuration
>> from a file like 
>> 
>> --8<---------------cut here---------------start------------->8---
>> [package avy]
>> set all-windows all-frames
>> bind C-z avy-goto-word-1
>> 
>> [package auctex]
>> set TeX-master dwim
>> hook TeX-language-de-hook site/use-german
>> rebind RET newline 
>> 
>> [package bash-completion]
>> (bash-completion-setup)
>> --8<---------------cut here---------------end--------------->8---
>> 
>> where the common patterns are simplified and made safe (e.g. the "set"
>> directive wouldn't evaluate) but still remains powerful, as you can
>> intersperse lisp code.  If I ever get around to finishing this -- or
>> anyone else decides to steal the idea ;) -- then adding this to the core
>> and loading ~/.emacs.d/init.conf if it exists might be a useful thing to
>> mention in a newbie manual.
>
> This sounds like a new DSL to specify Emacs features to turn on and
> off?  Is adding yet another extension language to Emacs is a good
> idea?  If anything, why not start from Editorconfig way whose support
> was recently added to Emacs -- that at least is a DSL known to others
> out there?

Yeah, a DSL with a castrated syntax that many users might be familiar
with.  It might be possible to reuse the EditorConfig parser, but not
much more beyond that.  As I said, I haven't finished my prototype yet,
so there isn't much of a point in discussing concrete questions yet, I
just wanted to bring it up as an idea.

-- 
	Philip Kaludercic on siskin



  reply	other threads:[~2024-09-13  7:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 17:30 Emacs Newbie Info Pages Summer Emacs
2024-09-12 18:26 ` Philip Kaludercic
2024-09-12 18:45   ` Summer Emacs
2024-09-12 19:17     ` Philip Kaludercic
2024-09-13  6:40       ` Eli Zaretskii
2024-09-13  7:36         ` Philip Kaludercic [this message]
2024-09-13  7:39       ` Summer Emacs
2024-09-13 14:46         ` Juergen Fenn
2024-09-13 12:28       ` Thanos Apollo
2024-09-12 18:29 ` Corwin Brust
2024-09-12 19:00   ` Summer Emacs
2024-09-13  2:24   ` Suhail Singh
2024-09-17  3:47     ` Richard Stallman
2024-09-17 10:58       ` Summer Emacs
2024-09-17 13:31         ` Eli Zaretskii
2024-09-17 14:12           ` Summer Emacs
2024-09-17 14:48             ` Emanuel Berg
2024-09-17 16:45               ` Summer Emacs
2024-09-18  1:09                 ` Emanuel Berg
2024-09-17 15:44             ` Eli Zaretskii
2024-09-17 16:49               ` Summer Emacs
2024-09-17 17:53                 ` Eli Zaretskii
2024-09-19  3:51         ` Richard Stallman
2024-09-19  9:45           ` Summer Emacs
2024-09-13  6:38   ` Eli Zaretskii
2024-09-13  7:45     ` Summer Emacs
2024-09-13 10:46       ` Eli Zaretskii
2024-09-13 11:20         ` Summer Emacs
2024-09-13 11:57           ` Eli Zaretskii
2024-09-13 12:09             ` Summer Emacs
2024-09-13 13:31               ` Eli Zaretskii
2024-09-18  8:13       ` Emanuel Berg
2024-09-18 20:02         ` Juergen Fenn
2024-09-20  2:39           ` Emanuel Berg
2024-09-22 12:37   ` Peter Oliver
2024-09-22 14:31     ` Eli Zaretskii
2024-09-13  6:35 ` Eli Zaretskii

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=87ldzw3t00.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=summeremacs@summerstar.me \
    /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).