acme: check file content before declaring file "modified since last read" Bad remote file systems can change mtime unexpectedly, and then there is the problem that git rebase and similar operations like to change the files and then change them back, modifying the mtimes but not the content. Avoid spurious Put errors on both of those by checking file content. (False positive "modified since last read" make the real ones difficult to notice.)

acme: add log file in acme root directory Reading /mnt/acme/log reports a log of window create, put, and delete events, as they happen. It blocks until the next event is available. Example log output: 8 new /Users/rsc/foo.go 8 put /Users/rsc/foo.go 8 del /Users/rsc/foo.go This lets acme-aware programs react to file writes, for example compiling code, running a test, or updating an import block. TBR=r R=r https://codereview.appspot.com/89560044

acme: sync against Plan 9, remove -$ option

acme: add -m option and avoid looking in the mirror

Use gcc -ansi -pedantic in 9c. Fix many non-C89-isms.

More thread names.

openbsd

use nil instead of 0

bug fix in auth

add errors file

remove searching print; check fids in use; handle addr correctly again

change to use new thread library

change md argument to number etc. (which acted only as a flag) to an actual flag. buffer underrun check in number add xdata file for exactly the addressed region save addr across opens

Compare function pointers against 0 rather than nil.

undo the madness.