Skip to content

Commit af94ee9

Browse files
committed
Add notes on unimplemented terminal events
1 parent 3f39343 commit af94ee9

File tree

1 file changed

+16
-7
lines changed

1 file changed

+16
-7
lines changed

ci/dev/vscode.patch

+16-7
Original file line numberDiff line numberDiff line change
@@ -1466,10 +1466,10 @@ index 0000000000000000000000000000000000000000..6ce56bec114a6d8daf5dd3ded945ea78
14661466
+}
14671467
diff --git a/src/vs/server/node/channel.ts b/src/vs/server/node/channel.ts
14681468
new file mode 100644
1469-
index 0000000000000000000000000000000000000000..95d0d3c51e4a25a9d7d0cada90d031c79bd86380
1469+
index 0000000000000000000000000000000000000000..7081bbf178c660803830675a4d8d596c5d0b7821
14701470
--- /dev/null
14711471
+++ b/src/vs/server/node/channel.ts
1472-
@@ -0,0 +1,860 @@
1472+
@@ -0,0 +1,869 @@
14731473
+import { field, logger } from '@coder/logger';
14741474
+import { Server } from '@coder/node-browser';
14751475
+import * as os from 'os';
@@ -2042,13 +2042,17 @@ index 0000000000000000000000000000000000000000..95d0d3c51e4a25a9d7d0cada90d031c7
20422042
+ this.dispose();
20432043
+ });
20442044
+
2045-
+ // TODO: exec command event
2045+
+ // TODO: I think `execCommand` must have something to do with running
2046+
+ // commands on the terminal that will do things in VS Code but we already
2047+
+ // have that functionality via a socket so I'm not sure what this is for.
20462048
+ // type: 'execCommand';
20472049
+ // reqId: number;
20482050
+ // commandId: string;
20492051
+ // commandArgs: any[];
20502052
+
2051-
+ // TODO: orphan question event
2053+
+ // TODO: Maybe this is to ask if the terminal is currently attached to
2054+
+ // anything? But we already know that on account of whether anything is
2055+
+ // listening to our event emitter.
20522056
+ // type: 'orphan?';
20532057
+ }
20542058
+
@@ -2307,16 +2311,21 @@ index 0000000000000000000000000000000000000000..95d0d3c51e4a25a9d7d0cada90d031c7
23072311
+ return this.getTerminal(args.id).getCwd();
23082312
+ }
23092313
+
2310-
+ private async sendCommandResultToTerminalProcess(args: terminal.ISendCommandResultToTerminalProcessArguments): Promise<void> {
2314+
+ private async sendCommandResultToTerminalProcess(_: terminal.ISendCommandResultToTerminalProcessArguments): Promise<void> {
2315+
+ // NOTE: Not required unless we implement the `execCommand` event, see above.
23112316
+ throw new Error('not implemented');
23122317
+ }
23132318
+
2314-
+ private async orphanQuestionReply(args: terminal.IOrphanQuestionReplyArgs): Promise<void> {
2319+
+ private async orphanQuestionReply(_: terminal.IOrphanQuestionReplyArgs): Promise<void> {
2320+
+ // NOTE: Not required unless we implement the `orphan?` event, see above.
23152321
+ throw new Error('not implemented');
23162322
+ }
23172323
+
23182324
+ private async listTerminals(_: terminal.IListTerminalsArgs): Promise<terminal.IRemoteTerminalDescriptionDto[]> {
2319-
+ // TODO: args.isInitialization
2325+
+ // TODO: args.isInitialization. Maybe this is to have slightly different
2326+
+ // behavior when first listing terminals but I don't know what you'd want to
2327+
+ // do differently. Maybe it's to reset the terminal dispose timeouts or
2328+
+ // something like that, but why not do it each time you list?
23202329
+ return Promise.all(Array.from(this.terminals).map(async ([id, terminal]) => {
23212330
+ const cwd = await terminal.getCwd();
23222331
+ return {

0 commit comments

Comments
 (0)