Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
alexdima
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Show HN: Copilot Next Edit Suggestions in VS Code
(twitter.com)
4 points
by
alexdima
2y ago
|
1 comments
2.
▲
by
alexdima
6y ago
Hi, I'm a developer on VS Code and wanted to clarify that there was actually a logical memory leak in there. The problem is that I tried to reproduce it back in October while running from sources, and I could not reproduce any leak. I
3.
▲
by
alexdima
8y ago
Hovering over the activation time will show the reason the extension is active. e.g. "Activated because you opened a javascript file", "Activated on start-up", etc.
4.
▲
by
alexdima
8y ago
Hi, I'm a developer working on VS Code. VS Code is architected in a way where extensions are not eagerly activated by default. Each extension can declare a list of activation events, such as e.g. opening a file of a certain language, i
5.
▲
by
alexdima
9y ago
Hi, I'm a VS Code developer. Can you please open a new issue and describe "as you would to a five year old" what's not working as expected. Even from reading this comment thread I simply don't get it, so it might be
6.
▲
by
alexdima
10y ago
When we started the project, we did write tokenizers by hand. I mention that in the blog post. You can write some very fast tokenizers by hand, even in JavaScript. Of course they won't be as fast as hand written tokenizers in C, but yo
7.
▲
by
alexdima
10y ago
I hate slowness and inefficiency too, that's why I try to make the editor as fast as possible :), but at least in this case, it is not the dynamic nature of JS to blame, but rather the nature of TM grammars. TM grammars consist of rule
8.
▲
by
alexdima
10y ago
Yes, those comparisons at the end show differences in rendering caused by the "approximations" used prior to VS Code 1.9. They were all caused by the difference between the ranking rules of CSS selectors and the ranking rules of T
9.
▲
by
alexdima
10y ago
- all the regular expressions in TM grammars are based on oniguruma, a regular expression library written in C. - the only way to interpret the grammars and get anywhere near original fidelity is to use the exact same regular expression lib
10.
▲
by
alexdima
10y ago
I love these questions! I've actually never tried to compute a diff and apply it inside a line, maybe I'll try it tomorrow :). A line is basically a list of spans, each having a certain class name and a certain text content. I
11.
▲
by
alexdima
10y ago
Thanks! Created https://github.com/Microsoft/monaco-editor/issues/6
12.
▲
by
alexdima
10y ago
We don't show leading/trailing whitespace diffs unless the diff consists only of leading/trailing whitespace changes. This is sort of what we do when diffing: * when we need to compare two buffers, we represent them as two ar
13.
▲
by
alexdima
10y ago
Here [1] is a working sample showing how to register a completion item provider for a language. The monaco-typescript [2] plugin shows how a lot of the language API can be used. [1] https://microsoft.github.io/monaco-editor&
14.
▲
by
alexdima
10y ago
Forgot to mention a funny fact I found. Minify everything [1] [1] https://top.fse.guru/nodejs-a-quick-optimization-advice-7353...
15.
▲
by
alexdima
10y ago
Implementing touch selection on a widget that is not native is not trivial. In the editor, when you select something, what you see painted is not really the browser (native) selection. It is simply a bunch of divs painted in such a way that
16.
▲
by
alexdima
10y ago
Lexicographical sorting at its best :)
17.
▲
by
alexdima
10y ago
We are definitely cheating there - we use the same colorizer for C and C++. I don't remember why we define two different languages that point to the same colorizer. Please help us out and contribute a PR. Here[1] is where we register t
18.
▲
by
alexdima
10y ago
The screenshot doesn't represent a statement on my part. I use Chrome, Edge and Firefox all the time. I especially enjoy debugging the editor in Edge's F12 Tools, because Edge's debugger is built with the monaco editor ;).
19.
▲
by
alexdima
10y ago
Hi, I'm working on the editor since almost 5 years now. Phew, time flies. There is no silver bullet, we mostly try to keep all computations limited to the viewport size (if you have 20 lines visible, then typing, colorizing, painting a
20.
▲
by
alexdima
11y ago
Thanks! We'll look into that
21.
▲
by
alexdima
11y ago
Or you could just type __directory, wait for the squiggly to show up and press ctrl-. => there is a code action there that will download the node.d.ts and add a /// reference for you
22.
▲
by
alexdima
11y ago
If you open a file with a UTF8 BOM, then the BOM will be preserved. New files don't have the UTF8 BOM.