3 ms·
Yes, that is what i wanted to be able to make sense of those one liners to avoid frustration of not having any idea why it's not working. Thanks.
by rooam-dev 7y ago
Yes, that is what i wanted to be able to make sense of those one liners to avoid frustration of not having any idea why it's not working.
Thanks.
- brudgers 7y agoAbout all the Lisp you need to know for that is Python/Javascript/C code that looks like: myFunc(3, "odd", myOtherFunc(7, 4, 8)); In a Lisp might look like: (myFunc 3 'odd (myOtherFunc 7 4 8)) Essentially the parentheses move, the commas go away, and strings that are used for dispatch are passed as symbols ('odd in Lisp instead of "odd"). On the one hand, that's really about it. On the other hand...there's a lot more to learning Lisp than that. It's just like any other programming language...it takes a non-trivial number of months. But you can use Emacs without knowing any Lisp at all. And the basic syntax of (func arg1 arg2 ... argN) gets you a long way. If you get the basic idea of quoting, you can probably parse all the code in just about any .emacs file. The hard part of Lisp is understanding all the implications and possibilities of quoting and applying them to abstract away complexity in a problem domain...your .emacs file won't need to do that because the relevant complexities are already abstracted away by the Emacs system as shipped.