unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: "João Távora" <joaotavora@gmail.com>
Cc: Christopher Allan Webber <cwebber@dustycloud.org>,
	Oleh Krehel <ohwoeowho@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: parinfer-mode for Emacs might be neat for encouraging Lisp adoption
Date: Fri, 13 Nov 2015 16:57:17 +0100	[thread overview]
Message-ID: <87vb95opsy.fsf@mbork.pl> (raw)
In-Reply-To: <CALDnm52pcXfUD42pEaL0kyP2LL__p9A9BAg8wf10XWfaPMhRqQ@mail.gmail.com>


On 2015-11-13, at 16:34, João Távora <joaotavora@gmail.com> wrote:

> Hi Oleh, Christopher, Marcin
>
> What do you think of this prototype?
>
>     (defun joaot/setup-some-parinfer-fanciness ()
>       (add-hook 'post-self-insert-hook 'joaot/reindent-up 'append 'local))
>
>     (add-hook 'lisp-mode-hook 'joaot/setup-some-parinfer-fanciness)
>
>     (defun joaot/reindent-up ()
>       (ignore-errors
>         (save-excursion
>           (backward-up-list) (indent-sexp))))
>
> Now in some lisp-mode, type
>
>    (defun parinfer ()
>      (let ((foo bar)
>            (baz quux))))
>
> Change the `let' to `let*' and watch the auto-reindentation
> magic. Probably very slow, but a cool trick nonetheless right?

I'll try it later!

> This is useful is other languages, right? Couldn't JSON benefit from
> something like this too?
>
>> - It doesn't solve the problem of pasting unbalanced code.
>
> IMO the problem of pasting unbalanced code is best solved by leaving it
> alone, and using `electric-pair-mode's paren-balancing heuristic (on by
> default), which is like paredit, but without the restraining order. And
> no need to learn new commands.

BTW, lispy's M command also (kind of) solves that.

> Have you tried it, Oleh? Any feelings on how it could be improved?
>
> Works for every language defining one or multiple parenthesis
> syntaxes. Just like the hack above.
>
> Personally I haven't tried lispy, basically because I want uniform
> interfaces for all languages, even non-programming ones. I don't want to
> re-learn shortcuts when I switch from lisp to JSON.
>
> For that, I stick to, and am reasonably happy with, traditional sexp
> navigation, the C-M-* family of movement/edition commands. Whoever came
> up with those deserves some love.

That is also a good point.  (But I use lispy nevertheless.)

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2015-11-13 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 23:30 parinfer-mode for Emacs might be neat for encouraging Lisp adoption Christopher Allan Webber
2015-11-12 12:45 ` 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 [this message]
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=87vb95opsy.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=cwebber@dustycloud.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=ohwoeowho@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).