I recently tried to switch from vim to Emacs with spacemacs. I enjoyed it until I discovered Emacs has no support for tabs (ui tabs, not the character ;). I went back to vim mainly due to that, but still miss magit....
Buying into the Emacs Platform (2018)
11–20 of 136 posts
Re: Buying into the Emacs Platform (2018)
#12The way I see it, there are two major approaches to IDEs - Extendable text editors (of which Emacs is the best example) and Visual Studio knock offs. There is no right or wrong answer, but I like the Emacs way.
I'd put it slightly differently, but I guess it is the same idea. There are two major approaches to software development: 1) powerful text editors (vi, Emacs) or 2) IDE. Powerful text editors are universal, but up to now their language support was often subpar compared to IDEs. They tend to do well for niche languages with no dedicated IDE, as then they're the reference editors. But for mainstream languages on can us…
It’s really interesting how LSP shifts what I’ll call “Visual Studio only features” into all editors, while at the same time you had Microsoft being the ones who initially pushed for LSP-adoption.
I wonder how many internal discussions they had on this subject before saying “Go”.
It’s a fantastic initiative and I’m glad it’s there for me, in my Emacs today.
Re: Buying into the Emacs Platform (2018)
#13I’ve tried using Spacemacs as a main editor for a while, but it’s too much of a mess, and if anything goes wrong (and it often does) you’re stuck with obscure lisp tracebacks, thanks but no thanks, I’ll use vim or kak as the actual text editor. I also noticed I spent an enormous amount of time constantly tweaking my spacemacs config as opposed to doing actual work.
Re: Buying into the Emacs Platform (2018)
#14I recently tried to switch from vim to Emacs with spacemacs. I enjoyed it until I discovered Emacs has no support for tabs (ui tabs, not the character ;). I went back to vim mainly due to that, but still miss magit....
C-x C-b
shows you the list of tabs ("buffers") and lets you select from them easily. As a bonus, the title portion isn't compressed to incomprehensibility when they get numerous.
Re: Buying into the Emacs Platform (2018)
#15Earlier quoted context omitted.
I'd put it slightly differently, but I guess it is the same idea. There are two major approaches to software development: 1) powerful text editors (vi, Emacs) or 2) IDE. Powerful text editors are universal, but up to now their language support was often subpar compared to IDEs. They tend to do well for niche languages with no dedicated IDE, as then they're the reference editors. But for mainstream languages on can us…
> That's the situation so far, but I see this changing thanks to the language server protocol It’s really interesting how LSP shifts what I’ll call “Visual Studio only features” into all editors, while at the same time you had Microsoft being the ones who initially pushed for LSP-adoption. I wonder how many internal discussions they had on this subject before saying “Go”. It’s a fantastic initiative and I’m glad it’s…
How many of us would be using a Microsoft IDE/text editor if it were not for VS Code?
Re: Buying into the Emacs Platform (2018)
#16Earlier quoted context omitted.
> That's the situation so far, but I see this changing thanks to the language server protocol It’s really interesting how LSP shifts what I’ll call “Visual Studio only features” into all editors, while at the same time you had Microsoft being the ones who initially pushed for LSP-adoption. I wonder how many internal discussions they had on this subject before saying “Go”. It’s a fantastic initiative and I’m glad it’s…
Visual Studio-like IDEs are a dead end. There is little revenue opportunity in them and a huge downside in losing relevance in the overall developer mindshare. How many of us would be using a Microsoft IDE/text editor if it were not for VS Code?
Re: Buying into the Emacs Platform (2018)
#17Earlier quoted context omitted.
I'd put it slightly differently, but I guess it is the same idea. There are two major approaches to software development: 1) powerful text editors (vi, Emacs) or 2) IDE. Powerful text editors are universal, but up to now their language support was often subpar compared to IDEs. They tend to do well for niche languages with no dedicated IDE, as then they're the reference editors. But for mainstream languages on can us…
> That's the situation so far, but I see this changing thanks to the language server protocol It’s really interesting how LSP shifts what I’ll call “Visual Studio only features” into all editors, while at the same time you had Microsoft being the ones who initially pushed for LSP-adoption. I wonder how many internal discussions they had on this subject before saying “Go”. It’s a fantastic initiative and I’m glad it’s…
Re: Buying into the Emacs Platform (2018)
#18I want to believe the friction comes if you try to "fix" Emacs too early.
You kinda have to conform to the Emacs way when learning it and leave all of your assumptions at the door. I see a lot of people who come to Emacs from Vim expecting Evil Mode to be the panacea for Emacs. It's not. At the end of the day, it's still Emacs and people run into friction because they expect it to be Vim-ish all over or they want to force Emacs to be Vim.
Personally, I came from Vim to Emacs via Spacemacs. I was a bit of a zealot about Vim until I tried Emacs. I left all of my expectations behind and I was pleasantly surprised by many things inside. Were there things I disliked? Of course. But, I wasn't looking for an excuse to hate it.
Re: Buying into the Emacs Platform (2018)
#19No thanks. I've had several bouts of trying to learn emacs throughout my life. It isn't necessary to list all the benefits, sure, there's a lot. Yes, I get it's "extensible" and you can write little elisp programs to do just what you want. Here's the obstacle: Motor skills. It just takes way to long to first memorize reams of commands and then to train your fingers to issue those commands effortlessly. In the meantim…
I just feel it's "my" editor more than any other editor I've ever used.
edit: typos
Re: Buying into the Emacs Platform (2018)
#20Is there a way to transition my claws-mail folders to Emacs, or ideally use both programs at the same time for a while?
The article recommends notmuch-emacs. But I'm afraid of 2 things, (i) loosing existing mails in the transition (due to e.g. faulty conversion tools), and (ii) that after a complicated transition I'm not happy with the new setup. Any recommendations? Is it possible to use the claws-mail email inboxes directly in Emacs?
Another thing is org-mode. I never really managed to get deep enough into it to really see the benefits. I've even bought the printed org-mode manual, but the setup seems so complicated. Can someone recommend a good "light" tutorial for it? What are you using it for?