Tracking a tab?

[jtagcat]

#16 after you open a tab, or do something with it, getting a tab ID or something would be nice, as you could be sure multiple commands get directed at the same tab (even if you have duplicate tabs).

[osnr]

Yeah. I'm not sure how exactly we could do that with the current create file setup (you read it right afterward?); might need to change approach.

Maybe you can make a tab file or folder in a create directory and then read it to get the ID, or it immediately turns into a symlink to the new tab, or something. Or there's a synthetic file ./create which is actually an executable you can run that outputs the tab ID.

[JinchengWang]

How about a last_created_tab file containing the last created tab id?

[jtagcat]

Reading right after, and last created both have the problem of assuming non-async. While almost everything we are talking here are made to be async. You can't assume you're the only process interacting with tabs.

[osnr]

We could make it so that if you read it right afterward from the same file handle, you get the result (each caller would open it with a different handle). I don't know if that would be usable from normal command line tools, though.

btw, there are also a bunch of options that it would be nice to support if we end up rethinking the way create works

[JinchengWang]

BTW it would be nice to support windows.create as well. Similar user interfaces might work in both cases.

[jtagcat]

I know it might be a bad idea, a fs is nice and everything.

..but what about exposing the browser with solid commands first, and then give the ability to mount it?

It seems counterproductive to do it the other way around.