On 6 Aug, Carl Johnson wrote:
> I think my solution is even simpler. I added a '^O' to the beginning
> of my prompt, so the prompt automatically corrects this type of
> problem. There are other types of problems, but this is one less to
> worry about.
I like that - good suggestion!!
--
Ric
On Mon, 7 Aug 2000, Triggs; Ian wrote:
> I have noticed that if I accidently 'more' or 'cat' or whatever a
> binary file and the terminal displays unreadable characters, the best
> thing to do is to 'more' the file again, keep pressing space until the
A "better" way is to use the 'reset' command.
"Triggs; Ian" <[EMAIL PROTECTED]> writes:
> I have noticed that if I accidently 'more' or 'cat' or whatever a binary
> file and the terminal displays unreadable characters, the best thing to do
> is to 'more' the file again, keep pressing space until the more prompt
> which says the percentage at
I have noticed that if I accidently 'more' or 'cat' or whatever a binary
file and the terminal displays unreadable characters, the best thing to do
is to 'more' the file again, keep pressing space until the more prompt
which says the percentage at the bottom changes back to readable
characters and
4 matches
Mail list logo
