Parinfer is a text editing mode that can infer Lisp code structure from indentation (and vice versa). A detailed explanation of Parinfer can be found here.
Put simply: the goal of Parinfer is to make it so you never have to think about "balancing your parens" when writing or editing Lisp code. Just indent your code as normal and Parinfer will infer the intended paren structure.
Once the package has been installed, it will automatically load in the background when you open Atom and watch for file extensions of popular Lisp languages. The file extensions are listed here and can be changed in the Settings.
When a file with a recognized extension is first opened, Parinfer runs Paren Mode on the entire file and one of three things will happen (in order of likelihood):
Running Paren Mode is a necessary first step before Indent Mode can be safely turned on. See Fixing existing files for more information.
If you do not want to be prompted when opening a new file, the prompts can be disabled in the Settings.
Please be aware that - depending on the indentation and formatting in your Lisp files - this initial processing may result in a large diff the first time it happens. Once you start using Indent Mode regularly, this initial processing is unlikely to result in a large diff (or any diff at all). You may even discover that applying Paren Mode to a file can result in catching very hard-to-find bugs in your existing code! As usual, developers are responsible for reviewing their diffs before a code commit :)
If you want to convert a project over to Parinfer-compatible indentation, please check out the Parlinter project.
|Turn on / Toggle Mode||Ctrl+Shift+(||Cmd+Shift+(|
The status bar will indicate which mode you are in or show nothing if Parinfer is turned off.
If you are in Paren Mode and Parinfer detects unbalanced parens (ie: code that will not compile), the status bar text will be red. Note that this will never happen in Indent Mode because Parinfer ensures that parens are always balanced. Also note that there is a known bug with this feature due to the "parent expression" hack explained below.
This extension uses a hack for performance reasons that may act oddly in certain
circumstances. It assumes that an open paren followed by an alpha character -
^\([a-zA-Z] - at the start of a line is the beginning of a new
"parent expression" and tells the Parinfer algorithm to start analyzing from
there until the next line that matches the same regex. Most of the time this is
probably a correct assumption, but might break inside multi-line strings or
other non-standard circumstances. This is tracked at Issue #9; please add to
that if you experience problems.
# clone this repo to your homedircd ~git clone https://github.com/oakmac/atom-parinfer.git# symlink the repo to the Atom packages folderln -s ~/atom-parinfer ~/.atom/packages/parinfer# compile CLJS fileslein cljsbuild auto
Then run Atom on a Lisp file. Some development notes:
View > Developer > Reload Window(to reload plugin changes)
View > Developer > Toggle Developer Tools(to see console)
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.