unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Request to add tomelr package to GNU ELPA
Date: Thu, 5 May 2022 17:05:56 -0400	[thread overview]
Message-ID: <CAFyQvY2Y9dXLVev4VBLZ2npUKO4DiKY3=30eeVgJQpCzq3ATDQ@mail.gmail.com> (raw)
In-Reply-To: <E1nmNme-0006py-Lc@fencepost.gnu.org>

On Wed, May 4, 2022 at 6:47 PM Richard Stallman <rms@gnu.org> wrote:
> I wonder: would it be useful to convert in the other direction,
> TOML config data to Lisp data?

I haven't found a use for parsing TOML (yet). Once I do, it will be a
challenging task to develop that library (I have zero experience
writing parsers).

The TOML generation on the other hand was easier as Emacs did all the
Lisp data processing for me :)

> Would it make sense to handle other somewhat similar formats
> of configuration data?  For instance, the data in .ssh/config?
> The data in /etc/network/interfaces?

It should be possible to generate that but the tomelr.el won't be the
place for that. I started with a strict definition for this package:
https://scripter.co/defining-tomelr/

This package only converts Lisp data to TOML and follows the TOML v1.0.0 spec.



  reply	other threads:[~2022-05-05 21:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 10:57 Request to add tomelr package to GNU ELPA Kaushal Modi
2022-05-03 13:09 ` Stefan Monnier
2022-05-03 14:29   ` Kaushal Modi
2022-05-03 14:38     ` Stefan Monnier
2022-05-04  7:10       ` Robert Pluim
2022-05-04 13:02         ` Stefan Monnier
2022-05-05 18:36           ` Richard Stallman
2022-05-05 21:16             ` Kaushal Modi
2022-05-03 14:31   ` tomas
2022-05-03 16:07 ` João Pedro
2022-05-03 16:45   ` Kaushal Modi
2022-05-03 17:41     ` Stefan Monnier
2022-05-03 17:51       ` Kaushal Modi
2022-05-03 18:01     ` João Pedro
2022-05-03 21:39       ` Kaushal Modi
2022-05-03 22:41         ` Stefan Monnier
2022-05-03 22:56           ` Kaushal Modi
2022-05-03 23:02             ` Stefan Monnier
2022-05-04  0:40               ` Kaushal Modi
2022-05-04  2:10                 ` Stefan Monnier
2022-05-04  2:37                   ` Kaushal Modi
2022-05-04 12:40                 ` Unable to get .elpaignore to work [Was: Request to add tomelr package to GNU ELPA] Kaushal Modi
2022-05-04 12:52                   ` Kaushal Modi
2022-05-04 13:06                     ` Kaushal Modi
2022-05-04 13:18                       ` Stefan Monnier
2022-05-04 15:03                       ` Stefan Monnier
2022-05-04 15:06                         ` Kaushal Modi
2022-05-04 15:11                           ` Stefan Monnier
2022-05-04 21:14                             ` Kaushal Modi
2022-05-04 22:47 ` Request to add tomelr package to GNU ELPA Richard Stallman
2022-05-05 21:05   ` Kaushal Modi [this message]
2022-05-06 23:19     ` Richard Stallman

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='CAFyQvY2Y9dXLVev4VBLZ2npUKO4DiKY3=30eeVgJQpCzq3ATDQ@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).