Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.4

code.visualstudio.com

Post reply on HN
Print view View original

61–70 of 155 posts

Re: Visual Studio Code 1.4

#61

Post by julianz »

jordanlev wrote: post #55
aokyler wrote: post #25

Earlier quoted context omitted.

I don't know what it's called specifically in context of other open Windows, but I'm guessing the functionality could be described as a feature of "IntelliSense" (but I think IntelliSense is Microsoft's name for it).

I wasn't clear about this, but in my experience with Visual Studio back in the day, IntelliSense only operates off of defined symbols (function names, class names, variables, etc). Whereas text editors such as TextMate and Sublime don't seem to "understand" the code as much, so instead they just autocomplete based on all word they find in the open project or Windows. But I actually prefer this more loosy-goosy style…

In a dynamic language like javascript, yes VS Code works exactly like this.

Re: Visual Studio Code 1.4

#62

Post by flukus »

asimuvPR wrote: post #43
was_boring wrote: post #12

I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

As part of the Visual Studio Code effort, the .net intellisense was split into a stand lone server to be used from any editor. So I'm going the opposite way, hoping to do more and more in vim and less in VS.

Re: Visual Studio Code 1.4

#63

Post by 2bitencryption »

rossy wrote: post #24
akanet wrote: post #3

Earlier quoted context omitted.

If you're curious, the integrated terminal is actually xterm.js behind the scenes: https://github.com/sourcelair/xterm.js

What's interesting is that (at the bottom of the stack of JavaScript turtles) xterm.js depends on pty.js. Windows does not provide a pseudoterminal API like Linux, so there is no official way of writing a terminal emulator that behaves like the builtin one (conhost.exe.) Because of this, pty.js uses winpty-agent.exe and winpty-agent.exe does its magic by starting a hidden conhost.exe in the background, effectively sc…

I suppose if you had the Linux Subsystem enabled, you could host a session there, and I'm sure there are a billion tried and true ways of sharing that session with the built-in VSC terminal.

If the Linux Subsystem were standard, you could depend upon it, but I guess not since it needs to specifically be enabled?

Re: Visual Studio Code 1.4

#64

Post by 2bitencryption »

whatever_dude wrote: post #48
seanmcdirmid wrote: post #28

Earlier quoted context omitted.

It isn't Intellisense since it isn't using type information but the context of the text buffer to determine possible completions. Autocomplete is too vague.

I think it's just part of autocomplete, but it has to have an expanded set of contexts it uses. I think VSC only checks for actual existing types/properties in that context. But other editors can be more intelligent: IntelliJ's IDEs, for example, will automatically autocomplete a new method name to a method that some code is referring to but that doesn't exist yet (it knows I'm trying to create it). I'll check what v…

This is only 20% relevant, but I've been messing with the Vim extension YouCompleteMe, expecting very intelligent completion based on the syntax of the language.

However, at least for C++ code, it seems like just a dumb symbol-lookup, suggesting only other symbols in the file, regardless of whether they syntactically make sense or not.

I must be doing something wrong but I don't know what. It seems to do a better job with Python, where it knows about keywords and built in functions.

(fyi, compiled with Clang Complete enabled).

Re: Visual Studio Code 1.4

#65

Post by sotojuan »

sho_hn wrote: post #60
asimuvPR wrote: post #43

Earlier quoted context omitted.

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

I'm curious, what's the thought behind having an official company-wide text editor? The companies I've worked for usually take the route of "leave their choice in tools up to them", which I appreciate.

I never got this either especially when editorconfig exists.

Re: Visual Studio Code 1.4

#66

Post by matt4077 »

spraak wrote: post #57
darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

Came here to find if it had Vim bindings.. I guess I'll wait to use it :/

The current release notes explicitly mention some API changes they implemented to better support the vim extension: https://code.visualstudio.com/Updates#_extension-authoring

Re: Visual Studio Code 1.4

#67

Post by KiriGiri »

chenster wrote: post #45

What would be some of the cool features that only exist on VSC that Sublime doesn't have?

And some great features inherited from Visual Studio.

Peek definition. when you want to peek a few lines of a method or type, you don't have to go away from the current position. In Sublime and Atom, it really bothers to open another tab.

Navigation through overloaded methods.

When a text editor is built to help people coding easily and make itself extended easily, it has to include some basic infrastructure so that extensions can focus on their specific implementations.VSC does this well, it is not only a text editor, but also have a skeleton of an IDE, and left all other things to extensions.

Re: Visual Studio Code 1.4

#68

Post by avolcano »

darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

I wanted to use VSCode when I started writing TypeScript three months ago, but I found the Vim plugins super lacking, so I used Atom instead, which has a much more robust Vim plugin.

However, I tried VSCode again last week after being disappointed by continued bugs in atom-typescript, and was happy to discover the Vim plugin (https://github.com/VSCodeVim/Vim) had made a ton of progress since I'd last given it a shot. It's still not quite as good as Atom's, but it's definitely getting there. Plus, the project's team is very active and friendly - I actually submitted a PR a few days ago fixing a bug (the VSCode extension development workflow is super easy, it turns out!) and they quickly merged it :)

I also found out that the VSCode developers know that it's an important plugin, and they actually have a category of issues on the VSCode repo specifically for extension APIs they need to add to make the Vim plugin as powerful as possible. This new update includes several of those, and I have a feeling by the end of the year the Vim plugin in VSCode will be on par or better than that of plugins for other editors.

Re: Visual Studio Code 1.4

#69

Post by modarts »

asimuvPR wrote: post #43
was_boring wrote: post #12

I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

What's the rationale behind forcing people to use an editor (especially a specific editor for a single language)?

Re: Visual Studio Code 1.4

#70

Post by Scarbutt »

asimuvPR wrote: post #43
was_boring wrote: post #12

I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

How did you manage to leave vim keys so easily?
Post reply on HN