1  |   Order by index

Nov 2, 2001, 2:50pm

ok I was looking through my chat log and the majority of it was garbled, odd
characters and what not, but this section below stuck out, anyone have a
clue as to what it is?


Most commands optionally preceded by integer argument k. Defaults in
brackets.
Star (*) indicates argument becomes new default.
----------------------------------------------------------------------------
---
<space> Display next k lines of text [current screen size]
z Display next k lines of text [current screen size]*
<return> Display next k lines of text [1]*
d or ctrl-D Scroll k lines [current scroll size, initially 11]*
q or Q or <interrupt> Exit from more
s Skip forward k lines of text [1]
f Skip forward k screenfuls of text [1]
b or ctrl-B Skip backwards k screenfuls of text [1]
' Go to place where previous search started
= Display current line number
/<regular expression> Search for kth occurrence of regular expression [1]
n Search for kth occurrence of last r.e [1]
!<cmd> or :!<cmd> Execute <cmd> in a subshell
v Start up /usr/bin/vi at current line
ctrl-L Redraw screen
:n Go to kth next file [1]
:p Go to kth previous file [1]
:f Display current file name and line number
.. Repeat previous command
----------------------------------------------------------------------------
---

have no clue why this would be in my chat log, tho I have no clue why any of
the other crap was in there as well, lost well over half of my 13 meg chat
log

Tyberius

Nov 2, 2001, 3:39pm

To me that looks more like a bug in the viewer you
use than crap in your chat log. It's the help page
of a VI clone would be my guess.

Try a different viewer, use the command "pg" (or "more"),
or check (with "df /tmp") if your temp file system can
handle large files like that. VI and most VI clones
need at least the size of the file they edit in the /tmp
file system, or the file system where the /tmp folder is
located.

If that all does not help, split your log file into
smaller chunks and try to read those. As long as you
didn't type "ZZ" or ":w" in your editor, the file should
still be OK.

[View Quote] --
"_
|
/\
\ /
__/ /_

Nov 2, 2001, 3:42pm

There are two p[ossibilities:
1, you managed to crash AW whil it was writing the chatlog - picking up some garbage from the buffer memory
2, you have crosslinked files due to some windows crash (can happen only on FAT filesystem).

Remedy:
Run chkdsk /f on the disk you have AW

HTH,
Andras
[View Quote]

Nov 2, 2001, 4:11pm

also found a whole webpage in html in my chat log, but I'll go ahead and run
that chkdsk /f command and see if it helps, almost like files are bleeding
into the friggin chat log
[View Quote]

1  |   Order by index