A possible translation of Martin Fowler's Syntactic Noise:
(state-machine idle(events
(door-closed D1CL)
(draw-opened D2OP)
(light-on L1ON))
(commands
(lock-panel PNLK)
(unlock-door D1UL))
(state idle
(=> door-closed active)
(actions unlock-door
lock-panel))
(state active
(=> draw-opened waiting-for-light)
(=> light-on waiting-for-draw)))
Put in a blender together with about 3 dl macrology, mix well.

Most of the ‘noisy’ parentheses are not strictly necessary, indentation alone can work too - see http://www.lispin.org/
Three things:
1. You already do look at the indentation level, and not the parens;
2. … moreover, most people change the paren color so they are close to the background color, making them actually disappear (mine are dark gray against a black background);
3. the output of the parens inserter is awful:
Nobody would indent their code nor place their parens like that. Instead, they would write:
Frankly, I don’t see the point of the Lispin project. But, to each his own!
Yes there are two kinds of programmers those who are happy with () and those that ain’t.
Personally I was happy with most of the (), but it puts off most developers, including
many THWers! Hence I decided to build a parser which removed most of the parens so the majority of coders would not turn up their noses.
The latest incarnation is in Genyris (http://sourceforge.net/projects/genyris/). This time the language is modified to suit indentation’s constraints, it looks like Ruby without ends. The rule is: If the indentation looks right the code will be too.
e.g.
So MF’s example in Genyris:
Which is more readable to a non-Lisper?
Looks alright, but the question is how user-extensible it is. Can you do macros?
Yes. Macros and templates.