Andre Berger wrote:
>
> On 2001-02-10 10:51 +0100, will trillich <[EMAIL PROTECTED]> wrote:
> > On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> > > Every once in a while I slip up at cat a binary file to the console. (Or
> > > just forget to give mkisofs the -o flag.) This cause
On 2001-02-11 14:02 +0100, Moritz Schulte <[EMAIL PROTECTED]> wrote:
> Andre Berger <[EMAIL PROTECTED]> writes:
>
> > > # bash
> > > set PS1="^V^O whatever> "
> >
> > Huh? Do you mean "export" instead of "set"? But the exported line
> > displays verbatim here? (potato)
> >
> > ^V^O whatever
Andre Berger <[EMAIL PROTECTED]> writes:
> > # bash
> > set PS1="^V^O whatever> "
>
> Huh? Do you mean "export" instead of "set"? But the exported line
> displays verbatim here? (potato)
>
> ^V^O whatever>
^V^O means you've to type Ctrl+V, Ctrl+O.
moritz
--
Moritz Schulte <[E
On 2001-02-10 10:51 +0100, will trillich <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> > Every once in a while I slip up at cat a binary file to the console. (Or
> > just forget to give mkisofs the -o flag.) This causes the console to use
> > WEIR
wow! that's the command I've been looking for. thanks (not my post thought ;)
rick
On Fri, 09 Feb 2001, Mike Dresser wrote:
> will trillich wrote:
>
> > On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> > > Every once in a while I slip up at cat a binary file to the console. (
will trillich wrote:
> On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> > Every once in a while I slip up at cat a binary file to the console. (Or
> > just forget to give mkisofs the -o flag.) This causes the console to use
> > WEIRD characters, just plain gibberish. Is there an
On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> Every once in a while I slip up at cat a binary file to the console. (Or
> just forget to give mkisofs the -o flag.) This causes the console to use
> WEIRD characters, just plain gibberish. Is there any way to get rid of
> this
And by invoking it, he therefore proved the last part about being
unsuccessful
;)
-c
- Original Message -
From: "John Galt" <[EMAIL PROTECTED]>
To: "Frederik Vanrenterghem" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, February 09, 2001 2:43 AM
Subject: Re: Cat-
On Fri, 9 Feb 2001, Frederik Vanrenterghem wrote:
>On Thu, 8 Feb 2001, Brian Frederick Kimball wrote:
>
>> Grrr. 6 people replying with the same answers is 5 people too many.
>>
>> Hitler! Hitler! Hitler!
>>
>
>I have to agree. At the time I wrote my answer, I did not see any other
>answers yet
On Thu, 8 Feb 2001, Brian Frederick Kimball wrote:
> Grrr. 6 people replying with the same answers is 5 people too many.
>
> Hitler! Hitler! Hitler!
>
I have to agree. At the time I wrote my answer, I did not see any other
answers yet, but of course they could have been delayed or something.
You going to write the FAQ to point to? :)
On Thu, 8 Feb 2001, Brian Frederick Kimball wrote:
>Grrr. 6 people replying with the same answers is 5 people too many.
>
>Hitler! Hitler! Hitler!
>
>Benjamin Pharr wrote:
>
>> Every once in a while I slip up at cat a binary file to the console. (Or
On Thu, Feb 08, 2001 at 07:30:15PM +0200, Tommi Komulainen wrote:
>
> You could also use a shell that doesn't corrupt your display, like zsh. :)
funny, i just exec zsh, and then did a cat /dev/urandom, let it go for
a second or two, and what do you know, my terminal was hosed ;-)
--
Ethan Benso
Grrr. 6 people replying with the same answers is 5 people too many.
Hitler! Hitler! Hitler!
Benjamin Pharr wrote:
> Every once in a while I slip up at cat a binary file to the console. (Or
> just forget to give mkisofs the -o flag.) This causes the console to use
> WEIRD characters, just p
Two possibilites (both in the affected tty):
1) reset (the command, not the button)
2) more the same file until the status line looks like it's in normal
characters, then quit out.
On Thu, 8 Feb 2001, Benjamin Pharr wrote:
>Every once in a while I slip up at cat a binary file to the console. (
On Thu, 8 Feb 2001, Benjamin Pharr wrote:
> Every once in a while I slip up at cat a binary file to the console.
> (Or just forget to give mkisofs the -o flag.) This causes the console
> to use WEIRD characters, just plain gibberish. Is there any way to
> get rid of this without rebooting? Than
> Every once in a while I slip up at cat a binary file to the console. (Or
> just forget to give mkisofs the -o flag.) This causes the console to use
> WEIRD characters, just plain gibberish. Is there any way to get rid of
> this without rebooting? Thanks!
>
> Ben Pharr
>
Try:
# setterm -
On Thu, Feb 08, 2001 at 11:18:34AM -0600, Benjamin Pharr wrote:
> Every once in a while I slip up at cat a binary file to the console. (Or
> just forget to give mkisofs the -o flag.) This causes the console to use
> WEIRD characters, just plain gibberish. Is there any way to get rid of
> this
t: Cat-ting binary files to the console
> Every once in a while I slip up at cat a binary file to the console.
> (Or
> just forget to give mkisofs the -o flag.) This causes the console to
> use
> WEIRD characters, just plain gibberish. Is there any way to get rid
> of
> this
On Thu, 8 Feb 2001, Benjamin Pharr wrote:
> Every once in a while I slip up at cat a binary file to the console. (Or
> just forget to give mkisofs the -o flag.) This causes the console to use
> WEIRD characters, just plain gibberish. Is there any way to get rid of
> this without rebooting? T
Every once in a while I slip up at cat a binary file to the console. (Or
just forget to give mkisofs the -o flag.) This causes the console to use
WEIRD characters, just plain gibberish. Is there any way to get rid of
this without rebooting? Thanks!
Ben Pharr
20 matches
Mail list logo
