Emacs Bedrock 2.0(lambdaland.org) |
Emacs Bedrock 2.0(lambdaland.org) |
Is it time to give emacs another try
From the README of the linked repo:
"When I started learning Emacs, my dad gave me his .emacs file. (That's what we used back in ye olden days instead of .emacs.d/init.el and stuff.) I used it without modification for many years. Eventually I learned how to write my own functions and customizations. This package aims to give other users a similar experience. When someone comes to me and expresses their desire to learn Emacs, I can point them at this to help them get over the initial hump, but not coddle them so much that they're afraid or unable to change things to their liking."
https://xkcd.com/297/ (Lisp Cycles)
I kept Elpaca out of Bedrock because I wanted a strictly built-ins-first experience, but if anyone asks what I use when they outgrow package.el, Elpaca is my first and only recommendation.
I hope Bedrock is useful to some people. :)
Kidding kidding... Cool project, thanks for sharing and kind of validating the stuff I ended up doing [0]. Hooray, use-package! That meandering (floundering?) culminated in my Emacs, which is a single `init.el file` (hooray, use-package): https://github.com/adityaathalye/dotemacs
[0] The blow-by-blow of which is documented in this excessively long blog post series I ended up writing as I was..., well, the title says it all;
Emerging from dotemacs bankruptcy the hard way
https://www.evalapply.org/posts/emerging-from-dotemacs-bankr...
The linked post is the first in the series, and it enumerates what features / capabilities I was going for, and the key references I used while figuring out the configuration, from scratch.
So many blogs (and newsletters for that sake) assume the reader knows and remembers what they are about
TIL! I might be able to remove my wgrep too. I love those highly crafted starter kits, they are full of gems.
Thank you!
No shade on wgrep, mind you—I used that for a long time and it's been one of my favorite tools. But now I just… don't need it. It's so nice being able to do consult-ripgrep -> export results to a buffer -> change to edit mode -> search-and-replace project-wide.
I agree that it’s counterintuitive and even sounds somewhat dangerous.
I see you're with PLT. :-)
Since Racket is built on Chez, you might like this. It's an Emacs-like editor built in Chez Scheme:
This is the right thing to do if you wrote your .el files recently and assumed lexical-binding was true and you understand the implications thereof.
OTOH if your .el files are older and written before lexical binding was possible, it's best to set the cookies of those files to nil. Or go over them with a fine-toothed comb and rewrite them (if necessary) for lexical binding.
Isn’t lexical binding the default in more or less all other programming languages?
So for people who don’t understand the implications, and wrote their .el files recently, lexical binding is likely less surprising behavior than the alternative?
In the past I wrote my .el files assuming dynamic binding because lexical binding was not available. Until I have the time and inclination to rewrite that code I mark them with
lexical-binding: nil
lexical-binding: t
https://www.gnu.org/software/emacs/manual/html_node/elisp/Le...
EMACS started as Eugene Ciccareli’ init file for the TECO editor (which was also a programming language) around 1976. Hence the name (Eugene‘s Macros). It was later rewritten in Lisp for Multics, the MIT Lisp Machine (I worked on one for the Xerox lisp machine as well), and later Unix (in those cases using lisp only as an extension language)
Interesting, do you have a source for this? I’ve always read that it stood for Editor MACros, are you saying this is a backronym?
For a start it's either spelled "Emacs" or "EMACS", and definitely not "eMacs".
Then it's closer to an OS than an editor.
Everyone knows that, but iOS autocorrects Emacs -> eMacs because Apple used to sell a product called "eMac".
I dislike the default package management system, but until a better one is merged into core, I'll keep updating my packages manually once a year when I remember.
Since Wikipedia didn’t even exist until emacs was more than 25 years old and little was written down in a way acceptable to Wikipedia, consider pages on topics of that vintage to be vague
Do you have corroborating sources? I (and others) would be keenly interested in them!
"The new version of TECO quickly became popular at the AI Lab and soon accumulated a large collection of custom macros whose names often ended in MAC or MACS, which stood for macro. Two years later, Guy Steele took on the project of unifying the diverse macros into a single set.[21] Steele and Stallman's finished implementation included facilities for extending and documenting the new macro set.[3] The resulting system was called EMACS, which stood for Editing MACroS or, alternatively, Emacs with MACroS."
I use the LazyVim distribution but I remember something in the docs about per-repo plugin settings