141–150 of 186 posts
Earlier quoted context omitted.
It's just a config for emacs. Sure it has some functions and life-cycle hooks for you to change a few things here and there, but in the end it's a glorified config. You delete .emacs.d and you're back to default emacs.
If you delete / /bin/ Ubuntu just becomes regular Linux.
Earlier quoted context omitted.
Just configuring all of the plugins with good key bindings takes a fair amount of time. Just one of the things that SpaceMacs provides. After a week or two with SpaceMacs I tried to start from a plain emacs and build up my own config, but I gave up. Just too much hassle for me. I probably would not have enjoyed SpaceMacs if I had used emacs at all before. But I switched directly from Vim with no prior emacs experienc…
Yup, you are right. When I deleted Vim and Installed Emacs, I wanted to learn Emacs and Lisp. That said I found configuring Emacs from scratch pretty good for what I want so I sticked to it. But I think that it is not that scary and hard as you might think! In 2 weeks I think you would be standing satisfied with your new humble and clean Emacs configuration. :)
I'd have to write my own editor for that. ;)
Earlier quoted context omitted.
Is there a clearer more understandable word? Your definition of 'distribution' sounds like something much more specific (changes to binaries?) than mine.
At risk of putting words in the another poster's mouth, I don't think the idea was that a distribution needs to have changes to binaries, just that it has to include the whole thing. I think the notion is that since you don't get your build of Emacs as part of Spacemacs, Spacemacs isn't a distribution of Emacs. I tend to agree. I think it could be a distribution of Emacs even if it were just upstream Emacs plus a sim…
Ok, but what it is? The page doesn't explain it. The top page explanation refers to spacemacs and most vim users don't know spacemacs. Is it a vim plus a bundle of plugins? EDIT: Cleaned up the spacemacs sentence.
Oh, yeah! Good old curl | sh via HTTP. Fucking awesome. I wonder how many people get unknowingly pwned while executing such curl | sh instructions. It's not hard at all to MitM HTTP, detect if shellcode is being transmitted, then add your own instructions to it. Or you can just compile a list of known sources that encourage to execute curl | sh and MitM only them if you want to make your exploits even more discreet.…
Earlier quoted context omitted.
For me the insecurity isn't even the worst thing about curl | sh. I like package managers, and I tolerate tarballs, because I know what they do and how to reverse it. I care about the organisation of my filesystem and suspect that the people who suggest I pipe their script into my shell do not care at all.
I have similar concerns. Also, these scripts pretty much never have an accompanying "uninstall" or "reset system state" scripts. For parent: check out http://github.com/awalGarg/curl-tap-sh (disclaimer: I am the author, and it was on HN's frontpage already a while ago)
Ok, but what it is? The page doesn't explain it. The top page explanation refers to spacemacs and most vim users don't know spacemacs. Is it a vim plus a bundle of plugins? EDIT: Cleaned up the spacemacs sentence.
It's a distribution, bundling vim with a whole bunch of plugins and configuration that's supposed to work out of the box. Spacemacs is the same for Emacs.
Emacs is a living, self-documenting environment and Spacemacs extends it quite a lot. This Lisp environment is very different from a set of plugins developed offline or mere configurations.
Calling Spacemacs a bunch of plugins and configuration is like calling any conventional program a plugin of its language and runtime. Plugins attach to an environment with a specific runtime API, instead of extending said API, blurring the line between runtime and extension in the process.
Earlier quoted context omitted.
I would probably spend more than 100 hours until I got to a point of equivalence with SpaceMacs, starting from a plain emacs. Especially since I use quite a few different languages. Ain't nobody got time for that...
The point is how much of Spacemacs you end up using?! And in which languages you work? Because, what consumes your time is not setup, with use-package setup becomes trivial really, what sucks you in is learning the plugins and how they work (cider, ensime, alchemist, magit, merlin, those are serious environments not just syntax/autocomplete plugins). Idk if they come with spacemacs, I doubt it, but what then makes th…
I wonder why?
Yay for the effort! But personally I don't think this is a good way to learn and use vim. The strength of vim is to customise it after your own needs and you'll do yourself a disservice if you end up with a config that you don't know and don't use more than x percent of.
I agree, the usefulness of a "distribution" like this is getting some fresh ideas about how to customise the editor. For example, this site listed some useful plugins that I didn't know about, such as https://github.com/bogado/file-line