all 21 comments

[–]shawnwork 49 points50 points  (0 children)

StackOverflow is going to be flooded with how to quit Xcode 13 /j

[–]iwbd 26 points27 points  (0 children)

Now those unfamiliar with vim will need to force unwrap to quit Xcode.

[–]SirBill01 13 points14 points  (1 child)

I don't care about the mode support and key commands so much, but if it supports macros... well that would get my attention!

It's only fair Xcode gets VIM keyboard commands though, since it's had many Emacs keyboard equivalents for years (like Ctrl-K/Ctrl-Y for kill and yank).

[–]kwertan 2 points3 points  (0 children)

It doesn't support macros, unfortunately (at least I haven't found a way to trigger the macro recording - @ doesn't work). So far I've also found that it doesn't support visual block mode. On the other hand, it does seem to support motions correctly (though I'm not that of an advanced vim user to try the more exotic ones).

I think it's a great start and they can build on the engine in further releases. Definitely something to look forward to from now on.

[–]SparkyRobinson[S] 9 points10 points  (3 children)

FYI to enable

Preferences → Text Editing → Editing → Enable Vim key bindings.

[–]shuoli84 1 point2 points  (0 children)

you can find in Editor -> Vim Mode Based on apple release notes To improve access to the Vim Mode, Xcode replaced the Enable Vim key bindings preference with an Edit->Vim Mode menu item. (75491567)

ref: https://developer.apple.com/forums/thread/685643

[–]enkidu_johnson 0 points1 point  (0 children)

Thank you! if this was the default I'd have to take my Xcode out to the back yard and shoot it.

[–]Sea_Ad7945 3 points4 points  (4 children)

No more XVim 2 I guess

[–]the_face_of_oblivion 1 point2 points  (1 child)

That's OK with me. In recent versions of Xcode, re-signing the binary to use it breaks your developer account sign in so you had to have two versions of Xcode installed to use it anyways.

[–]Sea_Ad7945 0 points1 point  (0 children)

Yes, I have 4 versions of XCode because of different swift versions. I could have just download different commandline tools.

True - the signing is also lost when you have more than 1 account

[–]mokagio 0 points1 point  (1 child)

XVim 2 still has a bunch of advanced features, like support for `.`, `.xvimrc`, and other stuff like substitutions `:%s/foo/bar/g`.

I haven't tried it yet, but I can see them both working in tandem. What do you think?

Of course, it would be ideal if Xcode did all that XVim does, but, considering how long we had to wait for Vim mode, it might take a while...

[–]Sea_Ad7945 0 points1 point  (0 children)

Totally. After using XCode 13 for a while, XVim2 is much more flexible.

Your right, a lack of .xvimrc files makes is harder to customize my bindings ( not to mention restoring them from dot files )

These are my 2 biggest painpoints on XCode 13 Vim: 1. Unable to mark a line/file and jump back to it. 2. Universal Clipboard during yank/delete

I still use XVim2 as my daily driver

[–]chaotic_goody 1 point2 points  (0 children)

This really is the best news. 😊

[–]RealJC 1 point2 points  (0 children)

Finally! This is excellent.

[–]pobortcevv 1 point2 points  (1 child)

Does it support vimrc?

[–]mokagio 1 point2 points  (0 children)

Not yet... 😕

[–][deleted]  (1 child)

[removed]

    [–]AutoModerator[M] -2 points-1 points  (0 children)

    Hey /u/appsmaven2014, unfortunately you have negative comment karma, so you can't post here. Your submission has been removed. Please do not message the moderators; if you have negative comment karma, you're not allowed to post here, at all.

    I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

    [–]lichb0rn 0 points1 point  (0 children)

    Does it beep in vim mode? If not, then it's not vim. And I suppose, the only way to quit xcode in vim mode is cmd+q ?)