proton 2016-02-14

@dvcrn: one thing missing is a minibuffer ala vim

@austincrft: no, I dislike the spacemacs default theme

I like the default proton theme

I don't like it either. I've gotten accustomed to solarized because it's available everywhere and I like consistency

solarized in emacs also sucks

the customized version that spacemacs used was great

after they switched to the one on melpa it sucked

some of the faces for magit didn't work -- when i toggled some of the switches for example

The problem with the default proton theme is that there are too many visual bugs. I noticed them too

Most people will probably change it, but what if we give the user a theme that’s so good that he doesn’t want to? 😄

What's wrong with the theme?

Why is there no minibuffer 😞

I like being able to type : and bring up ex

["proton.core.vim-provider" :vim-mode]

The default vim-mode-plus doesn’t have ex mode, but vim-mode does.

(albeit a limited ex mode)

I couldn’t find anything that vim-mode-plus did that wasn’t in vim-mode, am I missing something?

is there a C-g variant for atom?

vim-surround doesn't work like it does in emacs 😕

@robbyoconnor if you are using vim-mode-plus which is default, you need to add keymaps to perform surround actions. For example: https://github.com/geksilla/dotfiles/blob/master/proton#L77-L79 I don’t know why vim-mode-plus author removed them.

I’ve added such surround key maps to reflect https://github.com/tpope/vim-surround maybe we need to enable them by default...

I love spacemacs -- A LOT

I love spacemacs too ))

I dunno what to do now 😞

I’ve tried atom several times, and for now it’s really cool

much better performance and default experience

but still it eat a lot of RAM

s( also works on spacemacs but not in vim

in visual mode right?

I've used it to take a list and make it an array for example

1,2,3,4,5,6 Select everything and then s]

Added appropriate keymap, you can try to add to .proton :keymaps section

{:selector "atom-workspace atom-text-editor.vim-mode-plus.visual-mode" :keymap [                                                                                      ["s" ["vim-mode-plus:surround”]]]}

did it work? simple_smile

I use evil-surround A LOT

@geksilla: this needs to be enabled by default

yes, it works, just tested it and added to my .proton )

I might make a PR

👍 1

where the fuck do I add this

here core keymaps

unless you do it first

shit I have to check if vim-mode-plus is used -- fuck this

editing my proton config in spacemacs seems rather meta

@geksilla: I used your config simple_smile ❤️

vim-mode-plus vs vim-mode is a weird story. That’s why we added both because each has their own strengths. plus seems a lot more feature complete and fixes quirks like being able to copy into system register by default and incremental search. There’s a list with stuff it has over vim-mode https://github.com/t9md/atom-vim-mode-plus/wiki/Features

vim-mode-plus just felt a lot more solid and feature complete than normal vim-mode but with the big development team on the vim-mode side, this might change soon

I can deal with the lack of the minibuffer

it's cool simple_smile

Though the missing vim-surround keybindings

oh my word how do I disable the auto bracketing on clojure files?

It is making me crazy

@dvcrn: I just sent a pull request to fix the typescript layer linter issue, I think--let me know if there are any more issues, and sorry 😄

@jessejanderson: I think you mean Parinfer

@dvcrn: yah, figured it out how to disable it finally. I could not for the life of me figure out how to move the } to wrap elements inside. It would remove the one I tried to add further down, and wouldn’t let me delete the other one. Not sure how you’re supposed to use that thing.

it’s all about indentation 😛 It automatically creates / moves brackets if things are indented correctly

Ahh, so basically I just ignore the brackets and indent where things are supposed to go.

I couldn’t get as far as having the right bracket on the correct second line, was driving me nuts.

yep correctly. Just treat it as if the brackets are not there