5 ms·
I think this book would be perfect for me - I have been using Emacs for quite a while, but never mastered elisp: I could never figure out how to structure thing
by mrspeaker 5y ago
I think this book would be perfect for me - I have been using Emacs for quite a while, but never mastered elisp: I could never figure out how to structure things properly.
Looking at the book landing page, I think I would have passed on it because the Table of Contents make it look a bit like the book is just covering specific tasks (about rearranging sentences) rather than general tasks, like using best practices for creating packages.
It would be good to include the paragraph from your blog in the book landing page:
In the first chapter, it tells you basically how to find Elisp functions doing things you need.
In the second, longest chapter, it walks you through writing a complete, useful package, showcasing lots of Elisp features and good practices.
In the third, last chapter, it hints at a few more advanced techniques – functional programming, lexical scoping and regular expressions.
This made me a lot more excited about the contents!
- bjarneh 5y ago> I have been using Emacs for quite a while, but never mastered elisp You are not alone in that boat :-)
- rvdginste 5y agoAs a developer, I find it a bit embarassing that I started using Emacs in 2000, that at some point I even read my email with it, and that I never took the time to really learn emacs-lisp. Still, some day I will. This book might help me. :)
- bjarneh 5y ago> Still, some day I will I said I'd lean Spanish some_day® as well, according to duolingo that was 9 years ago :-)
- rvdginste 5y agoUh... well, it would be even more embarassing to admit how long I've been telling myself that I'd start learning emacs-lisp in earnest... so I won't. :)
- bloopernova 5y agoI'm just a devops person, not a coder by any stretch of the imagination, but I found that maintaining my .init.el in git helped me to learn enough elisp to be useful/dangerous. I really dig that it's a full on language used for the configuration files. It just makes so much sense to do it that way. (I also like VSCode's json prefs) Also I love sharing snippets of my .init.el: 40 │ ;; Taken from https://karl-voit.at/2017/02/11/my-system-is-foobar/ 41 │ ;; Check if system is Darwin/macOS 42 │ (defun my-system-type-is-darwin () 43 │ "Return non-nil if system is darwin-based (Mac OS X)." 44 │ (string-equal system-type "darwin") 45 │ ) ... 65 │ 66 │ (when (my-system-type-is-darwin) 67 │ ;; EXAMPLE: (global-set-key (kbd "C-z") 'shell) 68 │ ;; https://www.gnu.org/software/emacs/manual/html_node/emacs/Init-Rebinding.html#Init-Rebinding 69 │ (global-set-key (kbd "s-/") 'comment-or-uncomment-region-or-line) 70 │ (global-set-key (kbd "s-<backspace>") '(lambda () (interactive) (kill-line 0))) 71 │ )
- jolux 5y agosystem-type is actually a symbol, so you can do (eq system-type 'darwin) for the same effect. here's my macOS section: https://github.com/bklebe/.emacs.d/blob/b0ca255032d1240942ff885b98be51c9b5a37106/README.org#macos-configuration https://github.com/bklebe/.emacs.d/blob/b0ca255032d1240942ff...
- bloopernova 5y agoNice! I'll definitely take a close look at that.
- deleted 5y ago[deleted]
- TacticalCoder 5y ago> I found that maintaining my .init.el in git helped me to learn enough elisp to be useful/dangerous. The snippets you gave of your init.el are really basic but I do agree with you: working on init.el (and using Git to revert SNAFUs) helped me learn enough elisp to be dangerous too. The elisp I write is certainly not idiomatic but it gets the job done. I have some functions I wrote more than a decade ago and they still "Just Work [TM]"!
- ljm 5y agoI would love a dead tree version too. I've never managed to get on well with ebooks and PDFs.