Ideas for a good lisp editor?

[sydy]

Dear all,

I'm quite often confused when I have to deal with larger strings of lisp. Probably my mind isn't as powerful as others to follow the structure in all these parentheses. Sometimes, I just get sick by doing all these strings in a max-message. So I open a proper coding editor and write it there. But still, I have the problem with the confusing babushka of all these parentheses...

Actually, the III-slot would be a nice editor because it represents the structure of a III. Unfortunately, you lose your code if you forget a parenthesis... So it's not practical as an editor neither.

Has anyone an idea which coding-editor would give a structured representation of lisp code – as III-slot does – and maybe other features? (For java I use for instance komodo which is very helpful to code...)

I did a bit of research but couldn't find something convincing on the editor level...

Many thanks
m

[pedrnun]

Here's one!

Code: Select all

<pre><code>
----------begin_max5_patcher----------
1091.3ocuXsrjiZCEcs8WgBqrqggf.DfypjEoprHKx93obICZbqIXIJgneLS
MeP42HeYQO.Z5twf6wX6tLx5ZYc04Tm6C0ea4Bm87GIUNfeA72fEK91xEKLl
zFVzLegyQ7iYE3Jyxbx3GORXRGW62IIOJM1+u+ED3C2.9KRtfC9Sd8WITAuc
YUxmJHl00ZgUejxJHRytBaLVhkY2QYG1IHYR6oJH0y2EDgRzCaB0OgHOevmZ
9IelyjUzuZ1b8RsVo4Fmw2+kOF2yi7ZYqK80F+9xk5GtWH1877.bAPMb43MJ
HRiwDuzDjB2FzG32Cv8fVvlqO198bpDPYfLdNAPTS3hKGjH+9fD5mLJJSt9n
7dZUMtfVQlAA6FnQjFDqGPiCMz7AMF4A0V9FjIA6AEsVstP9TIwdVc1iYGbb
Ufr6zcoQpv.C7C8M3N3D3NbXbG7Cf6ijpJ7Axa.9ePJJ3a25BVY9KR8FodGm
.1jBxwLJof.7AqAPPf5IlkKHX0GNbGshpMbfWIoL8GefKJx+oSRhmM4ELYZN
aveTxlwXOX5vrGb9TM6wY24UxERbA3WUt.HOM5cajQylDJL0pj7GmENQh8VR
tBeOIemZkpceGVJEz80RastEcjwBm6IhJJmo1i8DgoHhuuuQGZox4RNlWer7
ppfPMoZ1zT4.NJ4Ec0kPlOLonQMRU4imAsCR2VfKHF5EZv+nIffvgwe3LVSI
iW9D3CfRbkj.VYF9nfTVfyHq2xdtmgsLdoTIA+YbgTs9bA9vVFQl0qchBJij
wqYlMFMWTU3ll3LiTIIZXp5F1iggat7JvP+TOTW2EIwiUAN4pW.Vn1VBPOET
QFOh3cUINbpzn1lkSGMN.MegAZDp6O7jEhWsZUzJzpWU.dMLXss16ZSk20s0
cWOUU2lTGuWdaxxOsYPCiM0ePPu.T2l+OjmNp5Dt+F0iNOQV0nNWJvGIRhXG
gg2aOj+HJMS0YofzEqLXQL3jRM2gpdOHYouk0m0Am5S7js.FYItTi.LHz+DW
WCFLz805xLqWJSwWlu42DTb+1XsQbpWCy3s4He3NdAYmlp1kik3c9cuZ3Bi3
zUyBqdwinlQTyXbhJfJUMoQ3pLovlyZ0HTgwlO5XUxNsSMJ5tYsJ6NCMJ7Nx
40m1tT9pbZfOMiMinNi4W2lQrUX5BkPiVLNX9ZF4THNqffEWUHC886e+mjQu
+yz.17yLE9e0+dFiq01eIKTwqEYs3oI0N3YmmSzROrtOidqQeOL8hFjneONB
dKbTzYfHzL3m1C6nNBNWNBdKbzMBP56jMsiReApORyK4pB4MxbUfi41KwlgM
OO6ROZmi5ANKjPvMySvyOhXX1FEDoI3zDuXah5jdSuzS24PCwugFrI9vkkMM
0X7h1GpD8ega5tIw0LkxrSMcBqpocOsc8lx+NXgJGsTkftVXSo+XrsAMGcKb
BVMsIoqxyee4+CPpTKgA
-----------end_max5_patcher-----------
</code></pre>

Cheers,
Pedro

[sydy]

Hey Pedro,

thanks, I did things like this too but your's is quite proper.
The problem comes with bigger strings. The bach.tree objects can't represent them without having all the connections scrambling the visualization... Try this one for instance (and it's still really a very small one...) :
( slotinfo (1 ( name amplitude ) ( type function ) (key a ) ( range -90. 10. ) ( slope -0.4 ) (representation dB) ( grid ) ( ysnap 0.) ( domain 0. 1.) ( domainslope 0. ) (temporalmode relative ) ( with duration ) ( height auto ) ) ( 2 ( name partial ) ( type text ) ( key p ) ) )

(And yes, you could use the attribute @textdecayfactor to shrink the text, but then the text of substrings gets really tiny... I'm not happy with it.)

So I'm still looking for something like ( slotinfo (1 ( name edit-tree ) ( type llll) )) but without the inconvenience of losing the code if there's an error.
Compare the representation as shown in the attachment (slot type llll) with your patch – I think you'll agree...
@Daniele and Andrea: This is a real issue for Santa Claus. I'll send him a lot of messages. :–)

Thanks again and have a nice evening.
M

[pedrnun]

Hi,

I'm sorry for not having replied sooner – I totally missed your reply.

You are absolutely right regarding the representation! I actually hadn't fully understand your issue until now. At the time, I was not aware of the "Editor for slot llll", which is very handy indeed!

It's probably a bit too late now, but here's another take: you can copy/paste from the slot editor to the [textedit]* and edit the llll there so you won't lose your code, in case of a mistake. If the code is good, it is accepted and formatted by [bach.slot]; otherwise, you'll get bach.join: Bad input llll (there's a [bach.join] before [bach.slot] in my patch).
I know it's not ideal but it might save you some code deletions!

* - it does support indentation although in a funny way...

Code: Select all

<pre><code>
----------begin_max5_patcher----------
1909.3oc6a0raaiCD9rySAgOk.jFPRIqe1S6VfdaOrXQussvfVhIVckIEjnh
iaQef1Wi8Ia4ORJVVT1xNtcSsZCpjMIEmY9zGmYj0vub0joK3OQKlB9EveAl
L4KWMYhtIUCSp99joqHOEkRJzCa5JZQA4A5zaM8InOIzsWPE0swJWkvRoB8E
fqZLiHhVlvdXdNMRXDnK18N3sxSH0Ib3cyjGw2AAer5ZRh0SMewmdCNbqYmW
JpmdTUqEhMoT8nqGmYPhMYTizlNE7QUOe8pqTGtcf1KitVJ+Nl6BRzx6Xhk.
r5ui1x8zlriqzl8vRyNvWCA8Y79mCiudvjGowykSqTalSDh7jEkBCGXRCFLY
5iz7hDNSJvEzbUmAPHDo6TifGKNtCu4HQpJNhK1Yu3zr+mHI8snHtbUF.AOV
i1SYf2BP95Sy1O2v4U3BiLdtfjB9Uon.1cKfN7hCescifg607g1Me7QX92pz
Z1Cu1Vhz.orxzzS025rC6ZE4+5hAI.Kj20AomHuAIsSjxmp6dW2zyxFmgazZ
Nij6jvDpSeCVEkSynrX.INtHkKNQWmnfPCdfvd6CPPvWgNR9DOgocirNmH8j
dpPfmSMDrWNAB+iebVMr0Kco1RtmyD2ShzZM7f3G1w0feXHz3SFtE.plqhjO
qmKjJh0U6wvr.5tS2ZhXjUFD92xSHo6eMphpDwS44FkUqZsNznhjHQxiTMpn
TxZUbw5H9JoYmrHIMQrYWkTJRCAks2XGcierdIOkNuLQIv4wDAYNr4eUWn4N
DX50pCpujvtmW2.ptCMZHOSVkIUvxX8Wto45zJh778kLoAxYs68uoazWa6Vy
kZp9hl+T0eJFy76S4DgmaSixQnhAiwdAgtNNdC7BPPeODDgvvVBUZfYCSn3Y
9dgAPG+.kzQA9vfffv1V.U5XrfxDjZaN9ssswGxk7qVsrofQxFpU2V2i4qHI
ri4ZGHPg8BcvtAVD1vgqNZqftRl7EIcE2PVXb1NjF4hFYPko6dgqShEK0pPY
NoKYZIM4gkZFKoTva2WDOay5kTVghj1YhIQQx7ZL23HwDV757Dwy5Ty.w6R5
yH4BsO.aTdcXBaz8roWH3gyt3gxKAPlrQZRgvNnXsSCt.Ocm.CmRKcdhj9K7
Nw09cHycWou0JE58jxTwzgudKHLv0G59pidfNI5gqU5g136mfzS2eGoHV858
5fh.uPXFy5ywQuNM9oCiQfCCu9cXrGmE+zQwkqiBeqLhtYVcnbttTx.Mv9Jj
jT5dhnZs2Wq3xowSBshKEY843naOeO8a7xd9yixuwOtTcDz58zzzzdddqt8b
Ys1GgrBHHjc3nqgcYsjGgsCG3QJbX+gwQNiT3v9Cep9kbGkvg8m3BMajBG1e
RCj2HENrmls5stNJgC6YYiBFovg8jqQgiS3.2Iuz3MxOkDUXGOr2a0qBH9RI
acbmjSS2j2Klz6qFI8hAO5jcp5UEEUlp0ldfk8LD6uozefWE0IcUFWPWJul9
7pXq2JTY4ECpXOqU7HMqUr8rVwizrVw1yZEORyZEaOqU7HMqUr8rVwizrVw1
yZEORyZ0w9ulpCb7AGs9M2EU4YsmBiKhWxpJ1PzIU8nQ7UqnLQ2xGkKVBDjE
J3Cb86IK.uiIn4Ef2KGwM.o1C9.Sh6l9+SpnLm0dHEK4kowfETPAU.DbPSAx
llvnMJN9HKSYmfsJLaO8Wbb5odT6oHkgcqG0SoRQKEBN6XqxZyFw.o2GFNv5
iV0dzKtZZqJqxyHs3e+G4yXhBA+AMNmC9cd4moI47iEDBc0kRsmKzTWrgZ3.
MqmphMnonX2Bd79VdusOy+cwIpRAAjkpJ92izpQAP09Hvbu22TL48bu2+aow
0SAimKEDs50WeRkIdflNWUxy8Th3yNKa2jSiSqLMZbR26pWCpqfXoOsOHtFo
OI+.PEOBzT8vfaZ5PoPf55Fdq1kdDAjs9t9szBdSH7N.R9+m6P+JUAuAdm6y
M19ckBhe6yCWURtac055wE.u64VLU9JPImNsZj01he6fifbp5o5ebayachz6
ec7usZ2D7Cnh7U0p430.baLqp3S2EwTP9NnU1NSjSq4Y0l45bAto0zHef64x
dzetomcPu2UlyKL8JObi8XO9mj2aCQ2Ivwr8xlobhYir2TY9RzPZLxXiyoLx
hzVaaf1KDbq4llHu8rneeqMp2NM2dt2LdRNjhIIVKoYmvdxy.ZMaEhv85lv4
buYZzBQeyemcqqVUUs2FQJ3k4Q0SUkiKvypZLsP5uvjc3yiwwLFqX9Pki6.j
SacYURbFWdWuxvbzAY777La3SiO4VeyWm6jqudf95ftuHUVmm9gzYj6Y.bbF
ffvNmIAgNjEgOSBBODAgdgBR+rkGD6lcFLI8uwwAkD7bHImuWDOLbnn2K89D
xe3NZpc8kGa1gXvu8RdGZTinQuLQODud07pWljvCgxbNHm5Re5PR5bvMQmn6
WSHQRVV0NMTKFkPjoC7IylBTmdjL.Cy7U8FGbZN8wj5wOS2BIWFsWHC0WlaB
J+jmI0mopbXxYkIUTDoj+5U+GzcJj1A
-----------end_max5_patcher-----------
</code></pre>

Cheers!
Pedro

[pedrnun]

I've just learned that [bach.reg] has the same kind of llll editor that pops up when you double-click it!!!
Here: http://forum.bachproject.net/forum/view ... =774#p2561
(Thanks, Daniele!)