unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: parinfer-mode for Emacs might be neat for encouraging Lisp adoption
Date: Wed, 11 Nov 2015 17:30:28 -0600	[thread overview]
Message-ID: <877flow194.fsf@dustycloud.org> (raw)

Here's a project borrowing some neat ideas from Emacs and extensions
(especially paredit) on lisp editing and providing some of its own
ideas, too:

  http://shaunlebron.github.io/parinfer/index.html

I could imagine this could make GNU Emacs an even better lisp hacking
environment for some than it already is, or make jumping in easier, for
some people.  Maybe someone will be inspired and add a plugin for it?
There's a space listed for editor implementations here:

  http://shaunlebron.github.io/parinfer/index.html#editor-plugins

I don't have time to work on this, but I imagine someone on this list
might find it interesting enough to take for a spin, so I thought I'd
post it here.  At the very least, it's clearly critical for GNU Emacs to
be the most advanced lisp editing environment there is. ;)

 - Chris



             reply	other threads:[~2015-11-11 23:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 23:30 Christopher Allan Webber [this message]
2015-11-12 12:45 ` parinfer-mode for Emacs might be neat for encouraging Lisp adoption Marcin Borkowski
2015-11-13 11:32   ` Oleh Krehel
2015-11-13 14:49     ` Marcin Borkowski
2015-11-13 15:34     ` João Távora
2015-11-13 15:57       ` Marcin Borkowski
2015-11-13 15:58       ` Marcin Borkowski
2015-11-13 16:00         ` João Távora
2015-11-20  2:37           ` Stefan Monnier
     [not found]     ` <CALDnm53TD9N6ZYhALP4ynVANAUpKJTWATNmL_FA80JrOpdBErQ@mail.gmail.com>
     [not found]       ` <877fll7w18.fsf@gmail.com>
2015-11-13 15:55         ` João Távora
2015-11-13 16:15           ` Oleh Krehel
2016-02-15 20:05 ` Christopher Allan Webber

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=877flow194.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --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).