Michał "phoe" Herda is a user on functional.cafe. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Tag urself on lisp indentation style:

;; I'm afraid of passing 80 characters
(proc1
arg1 arg2
(proc2
arg1 arg2
(cond
[(foo)
(bar 'baz 'quux)]
[else
(beep boop 'bop)])))

;; Everyone has wide monitors these days anyway right?????
(proc1 arg1 arg2
(proc2 arg1 arg2 (cond [(foo) (bar 'baz 'quux)]
[else (beep boop 'bop)])))

@cwebber 80 chars is best when you want to have 2 or 3 files open at once.

@phoe I agree, which is why I tend to be very "conservative" about width

@cwebber @phoe It seems odd that we still worry about line widths when we're editing structured data like code. Why should the formatting even make it into the file?

Michał "phoe" Herda @phoe

@freakazoid @cwebber Because source code is still text almost everywhere*, including Lisp lands. Lisp programs are Lisp data, but Lisp source code is text due to the possibility of syntax modification at read-time.**

*Unless you are programming in Smalltalk.

** So you can make the Lisp reader understand C syntax, for example. github.com/y2q-actionman/with-

· Web · 0 · 0

@phoe @cwebber I was really asking "why is source code still treated as text".