Earlier quoted context omitted.
I mean, I use autocomplete for work in python, ruby, golang, C/C++, JavaScript, coffeescript, CSS and probably more in enacts. The trick is the setup, but I've only had problems with minor edge cases (like coffeescript 2). Either way I'll spend an hour and use Elisp to fix it. Really nothing I've found is even close to as robust
I've been using spacemacs for nearly 2 years now and autocomplete has mostly always worked right out of the box after installing the corresponding layer. I rarely even need to reboot Emacs.
A CEO's Guide to Emacs (2015)
151–160 of 180 posts
Re: A CEO's Guide to Emacs (2015)
#152Earlier quoted context omitted.
I love Emacs. But there were no good multimodes 3 years ago. And autocompletion and hints are often a bitch to get working on things which are not C or C++. The moment you start editing files containing more than one language you're pushed to use a dedicated IDE. And then you discover the joy of "good enough". No need to tinker with config files to get the perfect setup: it works good enough to give you a productivit…
I came to the same realization about Vim about a year ago. I've used Sublime and Vim/Nvim extensively, and I've spent at least a few hours in Textmate, Emacs, Spacemacs, Notepad++, VS Code, and Atom as well. All of those text editors above have some excellent and unique redeeming qualities. But at the end of the day their actual language support tends to be weak. Now I do Python work in Pycharm, R work in Rstudio, an…
I use vim for everything, but Intellij (because we have the licenses; I mainly use it for Python at the moment) has my attention. Wish I had more time to learn it; it has been a couple of months and I still don't feel really comfortable. But the capabilities actually make a difference.
Vim is never going away for me; muscle memory, if nothing else, ensures it will always be the most efficient way for me to type text and I spend most of my time in the terminal anyway. And as nice as it was when it was my go-to for everything, there are times when a special purpose editor has a place.
Re: A CEO's Guide to Emacs (2015)
#153Earlier quoted context omitted.
I've been using spacemacs for nearly 2 years now and autocomplete has mostly always worked right out of the box after installing the corresponding layer. I rarely even need to reboot Emacs.
Just curious... Does spacemacs only offer Vim keybindings, or does it support Vim macros as well?
Spacemacs by extension integrates evil mode entirely, so keyboard macros are available.
Re: A CEO's Guide to Emacs (2015)
#154Re: A CEO's Guide to Emacs (2015)
#155I've never been able to get into graphical emacs, but emacs-nox has been my terminal editor of choice since college. Coming from a Windows background, vi(m) was too weird to get used to.
Re: A CEO's Guide to Emacs (2015)
#156Emacs and the Atreus keyboard and xmonad etc. are white elephants.
Re: A CEO's Guide to Emacs (2015)
#157Earlier quoted context omitted.
Author here. I didn't, but I might now. Dig this.
Hi there. Thanks for the article. I'm a newbie when it comes to emacs config files. You said, that we will put (add-to-list 'load-path "~/.emacs.d/lisp/") in the .emacs file, but that was before we had created it. Then a few paragraphs later, when we finally do create it, you tell us to just put in ;; set up ido mode (require `ido) (setq ido-enable-flex-matching t) (setq ido-everywhere t) (ido-mode 1) Where do we put…
I've got the `(add-to-list 'load-path "~/.emacs.d/lisp/")` pretty early in the file. You can put the `(require `ido) (setq ido-enable-flex-matching t) (setq ido-everywhere t) (ido-mode 1)` where you like. Basically, you just need the lines in your .emacs file - if you add the reference prior to creating the directory and populating it, you'll get an error, but nothing will break. Add the directory and do a `M-x eval-buffer` and it'll pick it up without restarting emacs. Or just restart emacs. Hope this helps. Someone will tell you a better way.
Re: A CEO's Guide to Emacs (2015)
#158Re: A CEO's Guide to Emacs (2015)
#159Earlier quoted context omitted.
I came to the same realization about Vim about a year ago. I've used Sublime and Vim/Nvim extensively, and I've spent at least a few hours in Textmate, Emacs, Spacemacs, Notepad++, VS Code, and Atom as well. All of those text editors above have some excellent and unique redeeming qualities. But at the end of the day their actual language support tends to be weak. Now I do Python work in Pycharm, R work in Rstudio, an…
I'm hopeful that https://github.com/Microsoft/language-server-protocol will decouple some of these concerns. We've built support for it for our DSL, and it's pretty great so far (esp in VSCode). Emacs LSP support is still pretty slow, so I don't use it when in emacs at present, but it feels like the right direction for getting good language support into editors.
It's still fairly new so most solutions I've seen that use it still have some sharp edges.
Re: A CEO's Guide to Emacs (2015)
#160Earlier quoted context omitted.
Back in the day our teaching assistance got pissed off that most people were using Emacs as if it was Notepad, and spent the rest of the programming lecture teaching how to use Emacs instead (about 1h). Which then became my to go editor in UNIX systems, until IDEs finally became a thing on UNIX.
I'm especially saddened when I see a lisp/clojure talk where the user navigate through emacs using arrows and the likes. A lisper not leveraging sexp ala paredit/parinfer is odd.
Mind, I do use Evil so I'm getting some 'structured editing'-lite from that already.