paredit.vim

Paredit Mode: Structured Editing of Lisp S-expressions

Developer Tools Languages & Compilers

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

178GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Paredit Mode: Structured Editing of Lisp S-expressions

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2013-06-25 23:01:22 UTC to 2015-09-23 18:03:03 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jun 2013	2013-06-01 00:00:00 UTC	2013-07-01 00:00:00 UTC	1	1
Jul 2013	2013-07-01 00:00:00 UTC	2013-08-01 00:00:00 UTC	0	0
Aug 2013	2013-08-01 00:00:00 UTC	2013-09-01 00:00:00 UTC	0	0
Sep 2013	2013-09-01 00:00:00 UTC	2013-10-01 00:00:00 UTC	0	0
Oct 2013	2013-10-01 00:00:00 UTC	2013-11-01 00:00:00 UTC	0	0
Nov 2013	2013-11-01 00:00:00 UTC	2013-12-01 00:00:00 UTC	0	0
Dec 2013	2013-12-01 00:00:00 UTC	2014-01-01 00:00:00 UTC	1	1
Jan 2014	2014-01-01 00:00:00 UTC	2014-02-01 00:00:00 UTC	0	0
Feb 2014	2014-02-01 00:00:00 UTC	2014-03-01 00:00:00 UTC	0	0
Mar 2014	2014-03-01 00:00:00 UTC	2014-04-01 00:00:00 UTC	0	0
Apr 2014	2014-04-01 00:00:00 UTC	2014-05-01 00:00:00 UTC	0	0
May 2014	2014-05-01 00:00:00 UTC	2014-06-01 00:00:00 UTC	0	0
Jun 2014	2014-06-01 00:00:00 UTC	2014-07-01 00:00:00 UTC	0	0
Jul 2014	2014-07-01 00:00:00 UTC	2014-08-01 00:00:00 UTC	0	0
Aug 2014	2014-08-01 00:00:00 UTC	2014-09-01 00:00:00 UTC	0	0
Sep 2014	2014-09-01 00:00:00 UTC	2014-10-01 00:00:00 UTC	0	0
Oct 2014	2014-10-01 00:00:00 UTC	2014-11-01 00:00:00 UTC	0	0
Nov 2014	2014-11-01 00:00:00 UTC	2014-12-01 00:00:00 UTC	0	0
Dec 2014	2014-12-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	0	0
Jan 2015	2015-01-01 00:00:00 UTC	2015-02-01 00:00:00 UTC	0	0
Feb 2015	2015-02-01 00:00:00 UTC	2015-03-01 00:00:00 UTC	0	0
Mar 2015	2015-03-01 00:00:00 UTC	2015-04-01 00:00:00 UTC	0	0
Apr 2015	2015-04-01 00:00:00 UTC	2015-05-01 00:00:00 UTC	0	0
May 2015	2015-05-01 00:00:00 UTC	2015-06-01 00:00:00 UTC	0	0
Jun 2015	2015-06-01 00:00:00 UTC	2015-07-01 00:00:00 UTC	0	0
Jul 2015	2015-07-01 00:00:00 UTC	2015-08-01 00:00:00 UTC	0	0
Aug 2015	2015-08-01 00:00:00 UTC	2015-09-01 00:00:00 UTC	0	0
Sep 2015	2015-09-01 00:00:00 UTC	2015-10-01 00:00:00 UTC	1	1

What Hacker News says

3 sources

an_ko·Sep 23, 2015

I'm a vim user actually! gasp Seeing ParEdit in action makes me extremely jealous though. http://danmidwood.com/content/2014/11/21/animated-paredit.ht... I wonder if the vim plugin https://github.com/vim-scripts/paredit.vim is any good.

In Show HN: Eslisp – Minimal JavaScript S-expression syntax and macro system

emidln·Dec 15, 2013

Brief overview of the landscape: For clojure/clojure-py/clojurescript, I start out with vim-sexp[0] (for vim motions over sexpressions; some people prefer the more common paredit.vim[1]), rainbow-parenthesis.vim[2], and vim-clojure-static[3] (for indention rules, syntax highlighting, etc). You'll want those regardless of which way you use to interact with Clojure. On top of that, you probably want some way to access a REPL. The top contenders seem to be: fireplace[4] (NREPL-based quasi-repl) slimv[5] (SLIME for CL, Clojure, Schemes, etc) vimux[6]/tslime[7] (copies from vim registers to a tmux/screen window where you presumably run lein repl or something) fireplace works pretty well. In theory, it can pick up the rest of the clojure world's nrepl middleware for advanced features. In practice, nobody seems to be doing this. I haven't looke

Read the rest

d into the codebase to figure out how to add support for various nrepl middleware, but it should be possible. slimv doesn't seem to be as popular in Clojure land. Most new development is based around nrepl, but you get some (not all) of its functionality thanks to ritz[8] being abstracted. I use vimux and normal vim shortcuts/macros to abstract my workflow. I like being able to handle cljs and clj in the same manner that I handle Python, Hy, Perl, and JavaScript. This is probably the route that requires the most vim knowledge and comfort with programming your lisp environment to make work. [0] - https://github.com/guns/vim-sexp [1] - https://github.com/vim-scripts/paredit.vim [2] - https://github.com/kien/rainbow_parentheses.vim [3] - https://github.com/guns/vim-clojure-static [4] - https://github.com/tpope/vim-fireplace [5] - https://github.com/kovisoft/slimv [6] - https://github.com/benmills/vimux [7] - https://github.com/kikijump/tslime.vim [8] - https://github.com/pallet/ritz

In Ask HN: How to get started with a modern Lisp

dktbs·Jun 25, 2013

I would argue that s-expressions are powerful for reasons other than macros, but I agree that the prefix notation and boatloads of parentheses can initially require a lot of extra effort for no apparent payoff. When I began writing clojure code (in vim) this was a constant source of frustration for me. The paredit.vim plugin [https://github.com/vim-scripts/paredit.vim] made things much easier and led me to give emacs a serious try. Writing lisp in an editor with paredit is a magical feeling. It turns the onion of parentheses into a structure that you can navigate and modify without having to worry about keeping things balanced. For me, this has made the parens effectively disappear from my focus.

In Why I am so excited about Clojure