lisp code formatting

On Jul 2, 8:41 am, Marc Tfardy wrote:
> Xah Lee schrieb:
> > you might try the latest version of ergoemacs
> WTF is ergoemacs??? :-o
> >http://code.google.com/p/ergoemacs/

Hi Marc,

There were numerous huge flame wars in the past couple of years regarding this. Perhaps you are a new comer. :D

> http://ergoemacs.googlecode.com/files/ergonomic_keybinding_qwerty_4.3...
> Who really need this? And what is better in you own key bindings
> compared to standard emacs? (except for your private preferences of
> course.)
> BTW:
> - bad parens
> - poor indent
> - too long comments lines

Here's some answer to your skeptism.

The Reason for ergoemacs is:

• Why Emacs's Keyboard Shortcuts Are Painful

> - bad parens
> - poor indent
> - too long comments lines

The reason that my elisp source code's formatting not always being have 100% lisp convention is because partly lazy and partly consider this formatting issue is a major myth that causes major harm to the industry. Here's some essays about it:

• Fundamental Problems of Lisp
(see the section “Automatic, Uniform, Universal, Source Code Display”)

• The Harm of Hard-wrapping Lines

• Tabs versus Spaces in Source Code

The following essays are on some feature that could've been:

• A Simple Lisp Code Formatter

• A Text Editor Feature: Extend Selection By Semantic Unit

∑ http://xahlee.org/

No comments:

Post a Comment