~vdupras/duskos

4e89006de870a1694a9526aecb3eadd565854ea1 — Michael Schierl 1 year, 1 month ago a416e35
doc: Trivial documentation fixes

I noticed these while implementing framebuffer grid driver.
3 files changed, 4 insertions(+), 3 deletions(-)

M fs/doc/gr/plane.txt
M fs/doc/struct.txt
M fs/doc/sys/file.txt
M fs/doc/gr/plane.txt => fs/doc/gr/plane.txt +2 -2
@@ 45,10 45,10 @@ Methods:
:pos! ( x y self -- )
  Set current target position.

:x+ ( n self -- )
:tx+ ( n self -- )
  Increase tx by n, wrapping around if necessary.

:y+ ( n self -- )
:ty+ ( n self -- )
  Increase ty by n, wrapping around if necessary.

:fill ( width height self -- )

M fs/doc/struct.txt => fs/doc/struct.txt +1 -1
@@ 105,7 105,7 @@ rebound. So, you can rebind structbinds with the word "rebind" (we can't use
All structs have a ":self" method which is a noop, and thus returns a reference
to the associated data. This can be used to get a structbind's data reference:

    data2 :self \ MyData1 is on PS TOS
    MyData1 :self \ data2 is on PS TOS

## Other field types


M fs/doc/sys/file.txt => fs/doc/sys/file.txt +1 -0
@@ 299,6 299,7 @@ dstfile Structbind to File, defaults to 0
## Path literals

There are 2 words for Path/File shortcuts: p" and f".
These literals cannot be compiled.

p" foo" is a shortcut for: