[gforth] doc. bugs pertaining to files

[Ethan Gardener]

in gforth.texi.in, regarding the .gforth-history file,
one node says it defaults to $HOME/.gforth-history
another to ~/.local/share/gforth/history

nodes:
@node Environment variables, Gforth Files, Command-line editing, Gforth 
Environment
    $HOME/.gforth-history
@node Command-line editing, Environment variables, Leaving Gforth, Gforth 
Environment
    ~/.local/share/gforth/history

neither exactly fits the android port, although $HOME/.gforth-history is close 
enough to be recognizable.  note the "unix" remark in connection with the 
~/.local/share/gforth/history name; it's a little confusing when android is 
related to unix.  it doesn't help that i'm still more familiar with unix prior 
to freedesktop.org, when we didn't have these long paths for configuration 
files.  

perhaps mention both paths in the files node with a line like, "depending on 
system convention, the history file may be...".  then in the environment node 
it could be replaced by a cross-reference.


i'm also relying on guesswork to decide where to make gforthrc and gforthrc0 on 
android.  again it's "close enough to be recognizable", but i could find myself 
doing some trial and error to see whether gforthrc is .gforthrc or 
.config/gforthrc for example.  it's another place where it would be nice to see 
"depending on system convention".

relevant node:
@node Invoking Gforth, Leaving Gforth, Gforth Environment, Gforth Environment


-- 
Progress might have been all right once, but it has gone on too long -- Ogden 
Nash