From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Carriage return
Date: Fri, 19 Jun 2009 09:51:12 -0400 [thread overview]
Message-ID: <1245419195-sup-7199@Longbow> (raw)
In-Reply-To: <1245410627-sup-2801@altis>
I'm not sure that this is carriage return related (Linux doesn't tend to
use these, right?). However, I'm certainly getting similar corruption.
This happens with errors, as well as just randomly sometimes after sup
closes/does something. My entire terminal actaully goes out of whack
and starts behaving like this.
I acutally just blamed it on my terminal being buggy somehow
(XFCE Terminal). I still think that's probably it. I'm not sure why sup
causes it though.
Anyway, reset fixes it when that happens. But yeah.... but yeah.
Cheers :)
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
Resisting temptation is easier when you think you'll probably get
another chance later on.
prev parent reply other threads:[~2009-06-19 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 11:27 Guillaume Quintard
2009-06-19 13:51 ` Andrei Thorp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245419195-sup-7199@Longbow \
--to=garoth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox