diff options
author | Omar Rizwan <omar@omar.website> | 2021-01-04 04:30:32 -0800 |
---|---|---|
committer | Omar Rizwan <omar@omar.website> | 2021-01-04 04:30:32 -0800 |
commit | 180a71732efab0d5d86cc8262ca975b669c4a2d7 (patch) | |
tree | 18a979dd8bc951b6cbc8e4207af72ac58357ec30 | |
parent | f47c7f066b821d26a8fdd31cc6429f96257f39df (diff) |
restore tabfs.c note; reword md
-rw-r--r-- | fs/tabfs.c | 6 | ||||
-rw-r--r-- | tabfs.md | 4 |
2 files changed, 8 insertions, 2 deletions
@@ -1,3 +1,9 @@ +// This file should rarely need to be changed. (which is intentional, +// because it is a pain to program here, it's a pain to recompile and +// reload it, and it's a pain to debug it.) Most of the behavior of +// TabFS -- the definitions of the synthetic files -- lives on the +// extension side, not here. + #include <stdlib.h> #include <stdio.h> #include <unistd.h> @@ -63,8 +63,8 @@ for that tab</p> This gives you a _ton_ of power, because now you can apply [all the existing tools](https://twitter.com/rsnous/status/1018570020324962305) on your computer that already know how to deal with files -- terminal -commands, scripting languages, graphical explorers, etc -- and use -them to control and communicate with your browser. +commands, scripting languages, point-and-click explorers, etc -- and +use them to control and communicate with your browser. Now you don't need to [code up a browser extension from scratch](https://twitter.com/rsnous/status/1261392522485526528) every |