Tyriar

10 ms·

61.
by Tyriar 8y ago
Hi, I'm part of the VS Code team. We have a page on our wiki that describes in a fair amount of detail how we structure iterations: https://github.com/Microsoft/vscode/wiki/Development-Process
62.
by Tyriar 8y ago
Hi, I build the terminal in VS Code and am a maintainer on xterm.js. There is some reinventing of the wheel happening but that's because xterm.js is the best option out there for building a terminal in a web context. As WorldMaker ment
63.
by Tyriar 9y ago
The slow prompt is a result of https://github.com/Tyriar/pretty-git-prompt inspecting the git repo and presenting info though, splitting itself should happen near instantaneously.
64.
Xterm.js 3.0 – Full in-browser terminal, now up to 45 times faster(github.com)
10 points by Tyriar 9y ago|0 comments
65.
by Tyriar 9y ago
Iridium's stable release is based on Chromium v61 and Chrome is on v62. Sure they can boast about enhanced privacy, but I'm not so sure about security unless their base Chromium version is always up to date.
66.
by Tyriar 9y ago
Hi I'm on the VS Code team, this is one of the next focuses for the terminal.
67.
by Tyriar 9y ago
You find this through task manager on Windows, `ps aux | less` will work on macOS/Linux.
68.
by Tyriar 9y ago
> and while you'd think you could speed this up by making it open a new tab in your current window and and return control the parent process when you close that tab ("code -r -w", I believe), that's not possible. Exac
69.
by Tyriar 9y ago
For excessive Code Helper CPU usage, you should be able to surface what the file/arguments were used to launch a Code Helper instance (how you do this depends on the OS). That will tell exactly which component is acting up, eg. TypeScr
70.
by Tyriar 9y ago
Author of the blog post here. The standard shortcuts are ctrl+` for toggling the panel and ctrl+shift+` for creating a new terminal. This is what I use on top of that: { "key": "ctrl+`", "command": "workbe
71.
by Tyriar 9y ago
Author of the blog post here. Canvas works fine for HDPI screens, you just need to handle it by tweaking the size of the canvas element (in CSS pixels, .style.width) and the number of actual pixels in the canvas (.width).
72.
Integrated Terminal Performance Improvements(code.visualstudio.com)
95 points by Tyriar 9y ago|70 comments
73.
by Tyriar 9y ago
You should expect latency similar to a web app in Chrome, just that this has a backing pty processing the input and output.
74.
by Tyriar 9y ago
I looked into this quite a bit when I was optimizing xterm.js. Based on my findings, ^C is highly related to the speed of the output because the process running in the shell may be way ahead of the terminal's parsing/rendering. Im
75.
by Tyriar 9y ago
I work on the VS Code terminal/xterm.js[1]. Hyper which currently uses a fork of hterm, is in the process of moving over to xterm.js due to the feature/performance improvements we've made over the past 12 months. Hyper's
76.
by Tyriar 10y ago
No worries, just bringing people up to date :) Unfortunately there's quite a bit to get done because everything was built around the assumption there would only ever be a single folder. In the meantime I recommend Git Project Manager,
77.
by Tyriar 10y ago
Hi sashk, I'm on the VS Code team. We did an initial investigation into what we would need to do to make this happen last week. It's definitely on the roadmap, more updates should come soon https://github.com/Micro
78.
Show HN: Mastering Visual Studio Code's Terminal(growingwiththeweb.com)
1 points by Tyriar 10y ago|0 comments
79.
by Tyriar 10y ago
Hi eduren, I'm on the VS Code team. The minimap this release is just a preview focused on getting the performance aspects of it right. You can read about what's to come at the bottom of the minimap section https://code.
80.
by Tyriar 10y ago
Thanks for the report chrisper, tracking this in https://github.com/Microsoft/vscode/issues/21654
81.
by Tyriar 10y ago
Hi brudgers, I'm on the VS Code team and I look after most of the Linux related stuff. I feel your pain as I've been updating my Insiders build nearly every day for the past 12 months. When you install this version, an apt repo an
82.
by Tyriar 10y ago
Thanks for pointing this out, expect a fix to come soon in the recovery build. https://github.com/Microsoft/vscode/issues/19775
83.
by Tyriar 10y ago
It already existed, you can see when we started shipping the integrated terminal pretty clearly from the contribution graph :) https://github.com/sourcelair/xterm.js/graphs/contributors The project itself is
84.
by Tyriar 10y ago
Hi, I worked on those improvements. Yes that is indeed what would happen when you ran a command with heaps of output, it would also lock up the UI while doing it. You probably haven't observed it much as you don't do recursive dir
85.
by Tyriar 10y ago
If it's missing functionality you need you could request by filing an issue to https://github.com/hiro-sun/vscode-emacs
86.
by Tyriar 10y ago
Hot exit is still useful when auto save is on as it works with untitled files. Crash recovery also comes with hot exit regardless of whether the feature is on or off. (I'm on the vscode team)
87.
by Tyriar 10y ago
I'll be looking into this for 1.9, the issue tracking this is https://github.com/Microsoft/vscode/issues/14613
88.
by Tyriar 10y ago
FYI that's being tracked here https://github.com/Microsoft/vscode/issues/15749
89.
by Tyriar 10y ago
If you mean keeping track of dirty files between sessions (aka hot exit), work started during this release and it should come to stable in v1.8. See https://github.com/Microsoft/vscode/issues/101
90.
by Tyriar 10y ago
We recently improved this for Linux, the latest .rpm package for example is now named code-1.5.1-1473370243.el7.x86_64.rpm. This is a good suggestion, I created an issue :) https://github.com/Microsoft/vscode/issue

More ›