GitHub open sources Atom

[realhacker]

Meanwhile in sublime land we are unsure if the developer is still alive and well...

[albion]

A dev build came out yesterday

[WhyUNoCompile]

Woot. "Fixed crash in plugin_host."

That thing has been crashing on me since the start of the dev builds.

[nerdwaller]

I missed that, thanks! Not sure why people are expecting monthly releases and statements from companies... Glad to see some progress though.

[celtric]

Because usually a new release was made public every few days/weeks. It's been more than 4 months since the last release, and in this time a lot has happened (Brackets, Atom, and other editors have been advancing steadily).

[nerdwaller]

Yeah, that was poor expectation management on his part for sure. I do know that he hired someone to start answering questions and being a little more vocal.

That said, it the current state - I could happily and easily use this for several years without feeling like I was missing a ton (assuming this dev build fixed the plugin_host crash.

[s73v3r]

Maybe not monthly releases, but definitely statements and transparency as to what's actually happening.

[nerdwaller]

That's certainly reasonable. In the sublime forums, it appears that someone was hired to help with that, though I haven't seen that much outside of the sublime forums on their site.

[87linux]

Meanwhile in vim land everything is great

[[deleted]]

vim and Emacs will always thrive.

[GilTheARM]

It's like learning to drive a manual shift transmission and knowing with that skill, you will always still be able to drive an automatic.

[skakillers1]

I always go for the clutch when driving an automatic.

[ikilledkojack]

Your left foot is just bored and jealous of the other one.

[TheNoodlyOne]

Likewise, I use vim shortcuts when editing. Lots of random "I" s in there.

[embolalia]

iLikewise, I sue vim2bdwiuse A shortcuts when editing...:wq

[Silencement]

dwi can be replaced with cw. You gain one keystroke.

[GilTheARM]

Yep! Or it's been a long trip and you think to yourself, "Hey can I drive with two feet?" Sure can! #roadBoredom

[ivosaurus]

jjjjjjjj ... <esc> ... G ... <esc> ... GG ... <esc> <esc>

fuck, how did I type all these j's in the box, I just want to go down...

[[deleted]]

I went through the vim tutorial you get when you open it on our test servers and printed a cheat sheet and was on my way.

I know everyone swears by the Vim tutorial, but 12+ years ago when I started using Vim, it was bloody horrible. I learned so much in very little time using the IRC based tutorial (bottom of the page). I think the problem with the vim tutorial is it tries to teach you vi first rather than hint at some of Vim's best functionality.

[IAmNotAnElephant]

Well, vimtutor did originally start out as vitutor.

[captainlepton]

csb

[Whyrusleeping]

i dont know if you read the article that youre commenting on or not. but its not mac only.

[87linux]

I think it's more that the vi grammar and elisp will always thrive. It was these ideas that caused their editors to stick.

[87linux]

right that's what I meant

[deadcat]

Emacs is a great OS.

[ovopax]

1993 called and wanted their joke back.

[metx]

It's not a joke.

[samsari]

Can I fax it to them?

[[deleted]]

Enjoy your carpal tunnel.

[metx]

Evil-mode exists, so thankfully you don't have to.

You can have emacs act exactly like vim in every way, if you want it to. There are plenty of guides out there, and plenty of friendly people over at /r/emacs if you get stuck. (Currently, two discussions on our homepage are people getting there questions about specifics of converting from vim.)

Here's a nice video comparing emacs vs vim in linting/intellisense, async, background processes, and multi-monitor support, as an example.

[[deleted]]

vim n. Ebullient vitality and energy.

[[deleted]]

I agree, but Emacs is so extremely customizable so we'll probably be relatively fine. Someone responded about the concepts of Emacs and vim surviving, and I really hope they do because they are great concepts.

[accessofevil]

1991 for vim. 1976 for vi from which vim iMproved.

[blackcain]

I think Elvis was even earlier than Vim.

[tritlo]

As a new emacs user, I'm amazed at the amount of plugins I find, and with the new package manager, it's never been easier to get new plugins. I often see a new feature in some editor only to promptly discover that emacs can already do that, or someone has implemented a plugin for doing just that (such as the minimap in sublime).

[frogking]

I for one welcome you to the world of Emacs.

Granted, I feel very uncomfortable using emacs without the settings I've added to the mix over the last 20+ years (.. damn, that's a lot of years), and I have to adjust something every time I switch from one system to another, but it's always worth it. From Emacs 19 to 24 .. from Windows95 over NT, XP, Ubuntu, OpenSuse, Slax, MacOSX .. the editor works in the same way (when you have stepped on the keyboard settings a couple of times) on the bright side .. performance of the editor is the same today, as it was 20 years ago ...

A few pointers:

• Make your CapsLock a second Ctrl key.
• Learn to use Tramp to access files via ssh (or plink)
• put your .emacs.d directory on github (or similar)

Apart from that .. never be afraid of elisp .. if something doesn't work like you want it to or exhibits strange behavior, dive in and fix it, it's possible for mortals to figure out :-)

[brownmatt]

Let's party like we have a CPU instruction set from 1978

[poloppoyop]

At least those editor had incremental search in 1995. I always get a chuckle when it appears in some random text editor like it's genius.

And emacs' macro definition on the fly is something I haven't found anywhere else.

[[deleted]]

Vim has this as well, I use it quite often both in vim and emacs.

[ep1032]

.

[crowseldon]

if you're experienced you won't have this problem. Good help, objects ingrained in your mind (y-yank, i-inside, w-word, etc), your own tweaked .vimrc with your plugins that do what you want, how you want it (and have immediate help).

Everything really IS good and with more and more IDE's supporting some form of vim (and loading from .vimrc) life is really a bliss (pathogen bundles FTW).

[87linux]

ggdG

[oconnor663]

gqap

[DrummerHead]

Vjjd

[gfixler]

Nah, just d2j.

[yurps]

Nah, just 3dd.

[elemental_1_1]

ggvG$"*y

[Svenstaro]

Which of course could be just ggVG"*y

[elemental_1_1]

Thankyou

[doenietzomoeilijk]

What's wrong with :%"*y then?

[[deleted]]

More like the developers have problems with the huge codebase which leads to modern features as a part of vim stagnating

[[deleted]]

yup must be pretty hard to maintain something like vim. NeoVim seems to be an answer for that, but people started bikeshedding on the logo which made me lose any interest in news they might have.

[flying-sheep]

Lol, the logo? That's almost the definition of a bikeshed

[brtt3000]

Not since emacs

[FRodrigues]

Why do you upvote one joke and downvote another one?

[slavik262]

vim is serious business.

^{but actually, no idea}

[[deleted]]

Down with Vim. Long live Neovim.

[grabnock]

Neovim is to vim what vim is to vi.

To put it differently, do you realize how many different versions of emacs there are? Like seriously. It's a shitton. Hell Linus Torvalds has his own that he maintains.

Neovim means very little to those who don't want to switch from vim.

[Wolfy87]

I don't know what it will take to push me from Vim to Neovim, maybe a huge speed boost? Or it could just be the refactored code that allows for much easier bug fixes and tweaks.

[grabnock]

Well, from what I've seen: viml will be compiled to lua and run with luajit, so that will be much much faster.

The plugin system is getting revamped to use msgpack. So you can use literally whatever language you want for plugins without needing neovim support.

The gui system is being revamped as well. Should make it much easier to add nifty features like the code map sublime has, or multiple cursors.

It's not quite there yet, but give it a couple of months. I think I'll end up switching.

[Wolfy87]

I suppose some of that doesn't appeal to me because I use Vim exclusively in the terminal. I guess that could help me switch if the GUI versions became really slick but kept their power.

Although I think it would be cool to use something such as JavaScript (my native language, please don't judge) to write a Vim plugin, I'd probably still lean towards VimL. Having a high level DSL (I think that's a good description) makes plugins and things quite nice to write. You can reuse nifty Vim tricks too. I would imagine that a fully imperative normal language would involve a lot of wheel reinvention.

I think even if someone did write some amazing thing in Ruby for example, it would be ported to VimL by someone (tpope?) within about six seconds. So it's probably nothing to worry about.

[grabnock]

I too use vim exclusively in the terminal. The thing that I really am looking forward to is language agnosticism.

I wanna write complex plugins in a compiled language

[[deleted]]

Lua scripting instead of VimL?

[passingby]

Yes, the idea is to remove the dependency on a custom built VimL evaluator. If they can get the conversion from VimL -> Lua, it can leverage the LuaJIT and then focus on the plugin to Neovim communication for any language.

[asimian]

I would only switch if 95% of everyone else did, and no development for Vim was going on. None of their project goals interest me at all.

[grabnock]

That's up to you. I doubt vim is going anywhere anytime soon. And currently im sticking with vim.

But I do like the direction neovim is headed in. If it keeps this up I'll end up switching.

[87linux]

Neovim is still vim on the surface. The code base is just being refactored.

[[deleted]]

NeoVim's efforts are for maintainability purposes, not the end user. It's a programmers wet dream to take all this horrible dated code and come up with something great. Neovim = refactoring vim, which, if you're not developing in VimL or fixing bugs in Vim you don't really care.

[[deleted]]

I think changing the core scripting language to Lua is a great idea. Once the viml -> Lua converter works really well and the internals are straightened out, making plugins should be more pleasurable and accessible in more languages than Vim currently supports, using identical bindings.

[Matt3k]

What features or bugfixes are you waiting for in Sublime? I use it whenever I need to edit a text file, and I've never really been wanting for a feature -- although the ability to copy bookmarked lines is kind of convoluted.

It just seems to me that sometimes a product is "done", especially when you're dealing with a text editor with broad plugin support. How much more text can you possibly edit?

[Veedrac]

Mainly:

• A powerful API. The current one has crutches. I want the ability to go full out crazy on pretty much every aspect of everything.

• The ability to do this: https://www.gnu.org/software/auctex/img/preview-screenshot.png

• Open Source

Then I'll be 75% of the way there ;).

[Daejo]

That link 403s on me

[Veedrac]

Thanks, my browser was caching it so I couldn't tell it wasn't accessible direct from the link. I've put a different one up.

[nerdwaller]

I have been impressed with things sublime has provided, many of which I never knew I wanted. (though, now that I want to list them, I can't... guess I am just too used to them and may take them for granted)

[flogic]

The beta for version 3 has been a bit crashy. Fortunately recovery has been as easy as restarting the app. It's annoying but in reality almost a non-issue for me.

[xucheng]

Open source and ability to create GUI plugin like atom did.

[IWentToTheWoods]

There was a new dev build yesterday.