3 ms·
It would be interesting to use a command line interface that acted like a text adventure game. > get file.txt YOU PICK UP THE FILE > inventory YOU ARE
by Splines 14y ago
It would be interesting to use a command line interface that acted like a text adventure game.
> get file.txt
YOU PICK UP THE FILE
> inventory
YOU ARE HOLDING:
file.txt
> gzip file.txt
FILE.TXT HAS BEEN COMPRESSED
> inventory
YOU ARE HOLDING:
file.txt (compressed)
> drop file.txt
YOU CAN'T PUT THAT HERE, THERE IS ALREADY A FILE.TXT HERE
> rename file.txt file.txt.gz
FILE.TXT HAS BEEN RENAMED
> drop file.txt.gz
YOU PUT DOWN FILE.TXT.GZ
Obviously not ideal, but at the very least the idea of inventory-as-clipboard would be useful on the command line.
- stephengillie 14y agoThat's a very fun idea you have there :)
- PotatoEngineer 14y agoYou are in a twisty set of deeply-nested directories.
- slurgfest 14y agoThis is interesting enough to criticize :) OK: you can get file.txt; gzip file.txt; rename file.txt file.txt.gz; drop file.txt.gz. However, it requires a get and a drop to fiddle the inventory, which doesn't seem to do anything (you are still specifying all the filenames each time). And I don't see a reason to generate a gzipped file of 'the same name' and then do a rename, it seems better for the new name to be an argument to the gzip operation. All you really want is to send information from file.txt through gzip to file.txt.gz. As in "gzip < file.txt > file.txt.gz" or "cat file.txt | gzip > file.txt.gz". But it feels like there should be cases where the clipboard/temporary holding area is much more useful than it is here, I just can't think of them?