HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
vscode-docs
Markdown2016–2024
microsoft / vscode-docs

vscode-docs

Public documentation for Visual Studio Code

Developer ToolsLearning & Reference
Explore on GitHubRead Hacker News discussions
11Distinct people
13Mentions
0Explicit recommenders
6.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Public documentation for Visual Studio Code

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year13 dated mentions

Observed mentions: 2016-03-21 22:11:17 UTC to 2024-07-03 12:24:30 UTC.

0123452016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 5 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC550
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303

What Hacker News says

13 sources
hollerith·Dec 18, 2022
I cloned github.com/microsoft/vscode-docs during my explorations of vscode. It proved much harder for me to work with than the documentation for Emacs is. I downloaded some NPM package (pardon me if I don't look up which one) to serve the markdown files in the repo on a port on my local machine, which worked okay I guess, but I never found a way to search the markdown files that is more graceful than using grep on the markdown files, which gets me the names of the files of interest, then using the aforementioned NPM package to visit the file, then using the find command in my browser to search for the lines of interest that grep printed. Also, there is a ton of basic information about web development that I needed to learn to try to start modifying my vscode install which of course is not included in that repo (vscode-docs) and I never fo
Read the rest
und an easy way of getting an offline copy of that information. In fact, IIRC I didn't even find troves of markdown files that could be cloned with git or other shell one-liners. Also, I have actually spent 100s of hours modifying Emacs "in anger" (i.e., although I wasn't getting paid for the work; the work was done as an earnest attempt to make my computing experience better or to make me more productive) while offline. Are you saying you've done the same with vscode? Heck: have you done that with any software implemented on web tech? I hope I don't sound combative: I really want to know if such a thing would become possible for me if I invested more of my time in learning web tech. I ask anyone reading this (not just the person I am replying to): is there anyone out there who routinely works on software implemented on web tech (i.e., browser or Electron or such) while disconnected from the net? For a definition of "disconnected", let us use this: it would take at least a few minutes of work (e.g., I must walk out of my apartment to another part of my apartment building to use the net) or at least a few minutes of waiting (e.g., I have internet service in my apartment, but I usually keep the modem unplugged, and every time I plug it back in, it takes a few minutes for the connection to come up and become usable).
In Emacs User Survey – 2022 Results
hollerith·Mar 2, 2017
Although vscode is a very impressive project, I get the impression it would prove frustrating for my use case: particularly, I am in the habit of using and hacking on my editor when I do not have net connectivity, and what this update and the last 2 updates have done is display a prominent banner in a contrasting background color saying "Error: the internet connection appears to be offline" that won't go away until I manually dismiss it. Then the banner reappears a few minutes later according to some criteria I have been unable to guess, and there is no "don't show again" button like there is on some other banners vscode shows me. Also I discovered no way to obtain a usable local copy vscode's documentation without acquiring deep knowledge of the system. (The deep knowledge becomes necessary after I clone the repo at github.com/Microsoft/
Read the rest
vscode-docs.) In summary, I'm going to encounter many frustrations if I make a deep dive into vscode the way it exists today, and I should wait till someone adapts it for offline use; is that not true?
In Visual Studio Code 1.10
carussell·Feb 13, 2017
> GitHub identifies people via their SSH key, not via a "name" or email address. Contrary to this, GitHub leans heavily on email addresses to identify contributors—in fact it may be correct to say it relies entirely on email addresses. This comes from both the documentation[1] and is borne out by experiments I've done to verify this[2]. The only thing I'm aware of that's of note is if you superficially try to change the author of the patch to give a different attribution before pushing to GitHub, then GitHub will say something like "Other-Name committed with Real-You". In this case, it all comes from Git—Git has a notion of "committer" as distinct from "author". So what's happening in the case of e.g. `--author=Other-Name <fake@example>`, Git reads your config, which specifies e.g. Real-You, and so based on that and the `author` flag,
Read the rest
will mark the commit with author Other-Name and committer Real-You. From this, GitHub displays the UI string of the form mentioned earlier. For example, from a recent commit[3] to the vscode-docs repo, if you do: $ git cat-file -p caa4bc3e50a96a93a1d4f5e39597cc3fc1cb9a4f ... then you get: tree 86c221e0f9e7e986068c50971ac322c738f5812f parent ccb9478342bba878111baedb412fb7f6911b40ad author João Moreno <mail@joaomoreno.com> 1486451758 +0100 committer Greg Van Liew <gregvanl@microsoft.com> 1486481582 -0800 Improve `code` docs for macOS Once again, this is all Git, and nothing specific to GitHub or any special inference that it derives from SSH keys (to my knowledge). If you have some other information, can you share it? Realistically, it's not feasible for GitHub to rely on SSH because it's not even necessary to set up SSH for your account. (Pushes from the command line can be done with a username/password pair—if you're hitting the https endpoint—and GitHub really likes people who do everything through their web UI. Forcing the latter group to mess with SSH is basically a non-starter, given GitHub's goals—which I'll clarify at every opportunity, is to be a social network first, and a software development platform second.) 1. https://help.github.com/articles/why-are-my-commits-linked-t... 2. http://www.colbyrussell.com/2016/02/13/keeping-a-low-profile... 3. https://github.com/Microsoft/vscode-docs/commit/caa4bc3e50a9...
In From AST to Lossless Syntax Tree

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.