4 ms·
> Weird things would go wrong and I had no idea how to fix them. My experience with Emacs/Spacemacs without having significant knowledge of lisp/elisp/Emacs de
by pyre 11y ago
> Weird things would go wrong and I had no idea how to fix them.
My experience with Emacs/Spacemacs without having significant knowledge of lisp/elisp/Emacs debugging. I want to like Emacs, but my Vim environment feels so much more "solid".
- dkns 11y agoSame here. I have emacs init.el file that I'd like to tinker with from time to time but every time I try to make switch I feel like I'm using a system consisting of thousands of moving parts which constantly break. It's completely awesome that you can change anything in emacs however you want but time and time again I realize that I'd rather have a rock solid editor with small api that let's you customize few things.
- pklausler 11y agoWrite one, then. I did. It's not hard. Mine's about 7K lines of code and it's the perfect text editor for me.
- pyre 11y agoDo you have fun integrating every new mode that you might like to use when you decide to open a source file for a new programming language?
- pklausler 11y agoI think that what you're trying to express is that I might be wasting some time implementing support for some syntax highlighting and code formatting features that are already present in other editors. Thank you for your concern. It hasn't been much of a problem since (1) I don't really used much syntax highlighting other than for reserved words, string literals and comments, and paired bracketing characters, (2) I rarely need to view or edit files besides C/C++/Haskell/bash/LaTeX, which I have support for, and (3) the editor works just fine on other files without fancy-pants modes anyway.
- mbrock 11y agoIt's funny this idea that you can't edit source code without a special "mode". It's just plain text, come on!
- mbrock 11y agoSure, stuff can go wrong with Emacs! I don't know anything about Spacemacs... but what I mean is that Emacs invites people to learn about the system, study its source code, change it, and fix stuff—whereas Xcode is completely proprietary, so that when things don't work there is literally no way to do anything about it except ask Apple to please fix it.