Just piggybacking on this thread to ask if there is a way to configure the editor so it accepts the spread operator? I'm getting errors and my Google Fu is failing me.
Visual Studio Code 1.0
341–350 of 487 posts
Re: Visual Studio Code 1.0
#342Earlier quoted context omitted.
Having the git diff in your editor gives you syntax highlighting and let's you edit it (the right side) like you're used to. I guess the killer feature of VS Code is multiple cursors (Ctrl+D). I only know of Sublime Text and Atom who also have this feature on Linux, not sure about Kate. Sublime Text is closed source and not gratis, Atom is slow and buggy.
Not allowed to reply to your post, so replying here. No, not built-in. They both have plugins, and allow you to set the key shortcut to whatever you please. That they are not built-in really doesn't matter though. All these editors revolve around plugins, and it's common practice to save your preferences on github or the like so that it's easy to use the same settings and plugins on every machine.
> Not allowed to reply to your post, so replying here.
I think you have to wait a few minutes, then it gets activated.
> No, not built-in. They both have plugins, and allow you to set the key shortcut to whatever you please.
That's too complicated for me. Last time I've tried to set up vim and emacs to my liking it was a mess: A lot of copying and pasting around random code, changing configuration files I didn't understand, ...
Re: Visual Studio Code 1.0
#343I'm a long time Linux guy and absolutely hate Visual Studio, it's just clunky and unusable as Eclipse. This post prompted me to try VS Code and I must say, I'm really impressed. There are still a few rough edges but I do understand it's still young. As soon as the Vim extension becomes usable I'll be on board I think; things like visual selection don't appear to work correctly at the moment.
I'm the maintainer of amVim.
I don't know if you tried amVim. It supports Visual and VisualLine.
Also, you may find it handles detail behaviors of Vim much better.
Re: Visual Studio Code 1.0
#344VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…
"I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me" Sounds like an undeserving environment for a developer. Why not vote with your feet?
Because not everyone wants 20% below market rate, consntant negotiation headaches on stock dilution, an "infinite" vacation policy that actually means none, or being part of a culture that expects 70+ hour work weeks as normal, 3 months of maternity leave being ruinous to the company, etc.
It's a tradeoff, for sure.
But also most companies are waking up to the notion that trusted network models are not effective. It just takes time to change.
Re: Visual Studio Code 1.0
#345Earlier quoted context omitted.
For example the Git integration is awesome and even better than Atom's (you can commit, push, ...). Of course you can do a lot with extensions, but at least in Atom's case they break a lot for me.
This is something I really do not understand. I can switch to my terminal, build, run, stage, commit, push all in like 5 seconds. As well as anything else I need to do in the terminal. The only 'plugins' I use are a keyboard shortcut (cmd+space) which puts me in a terminal window and rupa/z[1] for jumping into a project directory. [1] https://github.com/rupa/z
Let's say you look at `git diff` and notice something needs to be changed. What do you do now? You need to quit, open the file, find the line, do the change, save and quit. Now you need to reopen git diff and scroll to the old position. This all takes a lot more than 5 seconds on the terminal.
Another scenario: You type `git status` and see a file called `src/a/very/long/path/file.c` hasn't been staged yet. Now you need to type that file path for git add or git diff. Takes more than 5 seconds, but it's just a simple click on a + symbol in VS Code.
Re: Visual Studio Code 1.0
#346Earlier quoted context omitted.
I've seen the vi keybindings complaint a few times in here, and it's my major complaint as well. There are a few plugins, but they just aren't even close to usable in my opinion.
amVim is doing well, and I can attest that its maintainer is both sharp and very humble (in contrast to a lot of what I've seen come out of this nouveau-OSS era that GitHub seems to have ushered in). It's a shame that more people seem to have flocked to the VSCodeVim extension instead. I guess there's something to be said for being the first to grab the "Vim" label to apply to yourself. Having said all that, many of…
Hi, we met again!
Thanks for the positive words! Appreciated!
Re: Visual Studio Code 1.0
#347Earlier quoted context omitted.
To me (not OP), Python mode means syntax highlighting, code linting, code completion, and unit test integration from within the editor. There's a few other nice-to-haves, but those are the big ones.
In a simple text editor? My requirement would just be that copy/paste does intelligent things with indents.
In Sublime, Paste and Indent (Shift-Cmd-V on Mac) does that fairly well. It's not based on an AST or anything like that, but it's rarely failed to do the right thing in my experience with these: Python, XML, HTML, CSS, SASS, PowerShell, YAML, Ruby
Re: Visual Studio Code 1.0
#348Just piggybacking on this thread to ask if there is a way to configure the editor so it accepts the spread operator? I'm getting errors and my Google Fu is failing me.
This is mentioned in the release notes for 1.0.0 [1].
Their suggested solution is to disable built-in JavaScript validation entirely and rely on ESLint instead.
> Some users want to use syntax constructs like the proposed ES7 Object Rest/Spread Properties. However, these are currently not supported by Salsa and are flagged as errors. For users who still want to use these ES7 features, we have revived the javascript.validate.enable setting to disable all built-in syntax checking.
Re: Visual Studio Code 1.0
#349VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…
> I do not like sublime as it isn't FOSS
VS Code is not FOSS, either, I believe? [EDIT: Wait... it is open source. Must have missed that announcement]
I do like it a lot, though. KomodoEdit is pretty neat, as well. Even though it's closer to a full IDE, it feels very responsive. If either VS Code or KomodoEdit added something like paredit, I'd switch to them.
Re: Visual Studio Code 1.0
#350Are there any emacs/vim users here who moved to GUI editors like atom or VS code? I would like to know what potential gains could come from using a GUI text editor.
I don't get this false separation. Vim is, mostly, the best way to edit text, no matter the editor. Other things, like VS, Emacs, etc. are just ways to organize how the text editor interacts with other stuff (windows, IDEs, etc.).
Why not both? I use Emacs+evil. I use VS+VsVim. I don't understand why this isn't the preferred mode for everyone? Pick the best environment/shell/whatever, then make sure it uses vim for actual text editing. Problem solved.