Commits
- Commit:
3b1814ed992e43565c9f7b4339aa9438676df79d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
update the readme
- Commit:
86ba454213bfee77bd74411bb1417e8634fdfdcd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
revert the readline workaround
- Commit:
ba8b636b4d90e2197c7ea1949b7be79f9d1f1d89
- From:
- Omar Polo <op@omarpolo.com>
- Date:
drop REG_BASIC
It doesn't seem to be widely available (at least musl doesn't have it)
and it's the default anyway.
- Commit:
fb1a36c0a6028fb69d26ed62cafee077a0c345ce
- From:
- Omar Polo <op@omarpolo.com>
- Date:
restructure project and switch build system
use by default the OpenBSD mk infrastructure to build and test all the
kamid components.
- Commit:
507b56e50b583013fc420b2f728f2506dd6243bd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove comment
- Commit:
2f54e8f761eb748767ae4e443cbf881df4b34a74
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve draw_bar
cache tty_width to avoid calling ioctl in a loop and handle cases when
stdout is not a tty.
- Commit:
52586771172ed747dd0e1952283dbee9d3400448
- From:
- Omar Polo <op@omarpolo.com>
- Date:
adjust get to use walk_path
- Commit:
be727c17aab457ecfb1acc981c5fb82d2dc82c52
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make sure we don't draw a bar larger than the screen
if p->done goes up, way over p->max, we end up with perc being > 100.
in this case, reporting the correct percentage is fine, but drawing a
bar larger than the screen is not.
The bar could still "overflow" and occupy a second line, but only if
the percentage number takes more then 4 digits, so it's unlikely.
- Commit:
f4f42cd328771f335ec1dc15884f2bf337bdf36a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
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.
- Commit:
63b9781e99a5b7519106753eb93d50fb568d4d4c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make pwdfid a variable
- Commit:
a77ed65d76c7a9ad255e397169a02cc1256b0f7b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix two bugs in expect
- looking for Terror doesn't make sense, it's Rerror
- consume the tag before reading the error string
- Commit:
6658888da36b684c02f27edaf6f7752b9db9a92c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
simplify walk_path interface
- Commit:
17391a5db4bf92ad21c2da3d6d2b2f1205606dd3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ftp: draft `cd' command
- Commit:
983250eda8e0a63778e2066f73e46b34aeaf93df
- From:
- Omar Polo <op@omarpolo.com>
- Date:
implement barebone get
to implement the get command:
- implement do_stat and do_read
- implement a simple progress bar
- Commit:
db8967e939125bf527b94b2e694fb5c49fb916b6
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add tstat