Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Minor corrections

Browse source
This commit is contained in:
Jeff Parsons 2016-04-18 17:15:37 -07:00
commit 060c6b36d1
2 changed files with 7 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -151,7 +151,8 @@ Using the `--host` option makes it possible to access the web server from other
for example, you may want to run PCjs on your iPhone, iPad, or other wireless device.
Another useful variation is `--config _config.yml,_developer.yml` which uses the settings in `_developer.yml`
to override the defaults in `_config.yml`.
to override the defaults in `_config.yml`. Using development (non-production) settings in `_developer.yml` is
analogous to running the Node web server with certain development options; see [Debugging PCjs](#debugging-pcjs).
GitHub Pages says you can run `jekyll serve` instead of `bundle exec jekyll serve`, but with the addition of
more gems to `Gemfile` (eg, `jekyll-sitemap`), running `jekyll serve` may trigger dependency errors on some systems.
@ -294,9 +295,10 @@ to the server, or both.
Debugging PCjs
---
NOTE: The following information assumes you're running Node as your local web server, not Jekyll. You can still
debug PCjs while running Jekyll, using `http://localhost:4000/` and your favorite web browser's Developer Tools,
but none of the special server or client features discussed below will be available.
NOTE: The following information assumes you're running Node as your local web server, not Jekyll. You can certainly
debug PCjs while running Jekyll (ideally with `--config _config.yml,_developer.yml`), using `http://localhost:4000/`
and your favorite web browser's Developer Tools, but none of the special server or client features discussed below
will be available.
### Server Components

2
modules/pcjs/lib/bus.js
View file

@ -326,7 +326,7 @@ Bus.prototype.reset = function()
* powerUp(data, fRepower)
*
* We don't need a powerDown() handler, because for largely historical reasons, our state (including the A20 state)
* is saved by the saveMemory(), which called by the CPU.
* is saved by saveMemory(), which called by the CPU.
*
* However, we do need a powerUp() handler, because on resumable machines, the Computer's onReset() function calls
* everyone's powerUp() handler rather than their reset() handler.