Daniel Burrows wrote the following on 01/30/2009 09:46 AM:

On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks <wix@mgssub.com> was heard to say:
I have just discovered that the command line in a gnome terminal window
doesn't wrap correctly. Instead of doing a line feed and continuing on
the next line it just returns to the beginning of the current line and
writes over it.


That sounds like something left your terminal in a bad state. Does
running "reset" help?

Daniel




Daniel;

No, reset didn't do it, but your comment gave me an idea.

I opened a new terminal window and it worked just fine!

I had eight terminal windows open in various workspaces and
they all malfunctioned the same way. After your suggestion I
opened another terminal window, didn't close the others, and
it worked! Just on a hunch I tried one of the others, and
now they *all* work as they should! Exceeding strange! But I
am now a happy camper, or would that be happy hacker?


Any way, thanks for the help and suggestions Ron and Daniel!

Good Luck!!
Dennis


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jan 30, 2009 at 10:28:03AM -0600, Dennis Wicks wrote:
> Daniel Burrows wrote the following on 01/30/2009 09:46 AM:
>> On Thu, Jan 29, 2009 at 09:21:21PM -0600, Dennis Wicks <wix@mgssub.com> was heard to say:
>>> I have just discovered that the command line in a gnome terminal
>>> window doesn't wrap correctly. Instead of doing a line feed and
>>> continuing on the next line it just returns to the beginning of the
>>> current line and writes over it.
>>
>> That sounds like something left your terminal in a bad state. Does
>> running "reset" help?
>
> No, reset didn't do it, but your comment gave me an idea.
>
> I opened a new terminal window and it worked just fine!
>
> I had eight terminal windows open in various workspaces and they all
> malfunctioned the same way. After your suggestion I opened another
> terminal window, didn't close the others, and it worked! Just on a hunch
> I tried one of the others, and now they *all* work as they should!
> Exceeding strange! But I am now a happy camper, or would that be happy
> hacker?

It might be useful to compare the terminal settings in the `bad' vs `good'
cases, e.g., using stty -a > bad, etc.. You might be able to find something
to tweak to fix that particular problem.

Well behaved programs should return the terminal to its original state,
but maybe that didn't happen. Killing programs with the KILL (-9)
signal would probably have this effect, vs using the default TERM (-15).

--
Ken Irving


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Ken Irving wrote the following on 01/30/2009 01:30 PM:



It might be useful to compare the terminal settings in the `bad' vs `good'
cases, e.g., using stty -a > bad, etc.. You might be able to find something
to tweak to fix that particular problem.

Well behaved programs should return the terminal to its original state,
but maybe that didn't happen. Killing programs with the KILL (-9)
signal would probably have this effect, vs using the default TERM (-15).

All of the terminal windows are bash sessions started with
the same shortcut. As far as I can tell they all started
malfunctioning at the same time and all started working
again at the same time. Of course not every command that I
type takes more than one line so it would be hard to tell
exactly when the problem started. I do know that
starting/opening another window fixed the problem in all of
the open windows/sessions.


More likely opening another window fetched a clean version
of some module or control file that they all use.


Thanks for the insight! I'll remember to use TERM when I
have to kill so errant process. It might save me a headache
in the future!



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks <wix@mgssub.com> was heard to say:
> Thanks for the insight! I'll remember to use TERM when I have to kill so
> errant process. It might save me a headache in the future!

The difference between TERM and KILL, btw, is that TERM asks the
program to shut down, whereas KILL just stops it instantly. So
programs killed with TERM can run cleanup actions before they shut
down, but programs killed with KILL don't get a chance. (this also
means that programs can ignore TERM, for instance because they've
crashed really badly -- KILL is really meant for situations where that
has happened)

Daniel


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 01/30/2009 11:58 PM, Daniel Burrows wrote:

On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks <wix@mgssub.com> was heard to say:
Thanks for the insight! I'll remember to use TERM when I have to kill so
errant process. It might save me a headache in the future!


The difference between TERM and KILL, btw, is that TERM asks the
program to shut down, whereas KILL just stops it instantly. So
programs killed with TERM can run cleanup actions before they shut
down,


I 'kill -15' iceweasel whenever I need to log out but want to retain
all my windows and tabs.



but programs killed with KILL don't get a chance. (this also
means that programs can ignore TERM, for instance because they've
crashed really badly -- KILL is really meant for situations where that
has happened)


--
Ron Johnson, Jr.
Jefferson LA USA

"I am not surprised, for we live long and are celebrated poopers."


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Jan 31, 2009 at 01:05:48AM -0600, Ron Johnson wrote:
> On 01/30/2009 11:58 PM, Daniel Burrows wrote:
>> On Fri, Jan 30, 2009 at 02:51:35PM -0600, Dennis Wicks <wix@mgssub.com> was heard to say:
>>> Thanks for the insight! I'll remember to use TERM when I have to kill
>>> so errant process. It might save me a headache in the future!
>>
>> The difference between TERM and KILL, btw, is that TERM asks the
>> program to shut down, whereas KILL just stops it instantly. So
>> programs killed with TERM can run cleanup actions before they shut
>> down,
>
> I 'kill -15' iceweasel whenever I need to log out but want to retain all
> my windows and tabs.

you may already know this, but iceweasel 3 does this for you. ctrl-q
and then <enter> (I think it's the default option, save session for
next time).

A