fix cd Walk can be successful in various conditions where cd has to fail. For instance, we may have reached a file or we couldn't walk all the required components. In these "soft-fail" cases, the walk has mutated the fids, so to abort the cd we have to do a walk using a second fid and then clunk the old or new one depending on if it was _completely_ successful or not. Another option may be to track the number of walked path and attempt to walk '..' the right amount of times, this would saves a Tclunk in the case the walk succeeded and require a slightly bigger 9P packet to be sent in the failure case. It would complicate the walk_path API though, so I've not chosen this option.

make pwdfid a variable

fix two bugs in expect - looking for Terror doesn't make sense, it's Rerror - consume the tag before reading the error string

simplify walk_path interface

ftp: draft `cd' command

implement barebone get to implement the get command: - implement do_stat and do_read - implement a simple progress bar

add tstat

ls: use fmt_scaled to print file size

import compat for fmt_scaled

tweak ls output

refactor stat parsing in its own function

fmt

- [regress-extra] added test for copying and moving a file; - [regress-extra] fixed 'make-huge-data' so that returns always the same value.

use shell prompts consistently in the README.md

- [regress-extra] fixed test 'test-read-a-tiny-amount-of-data', a condition signalled was expected.