i am embarrassed to ask this, but i can't figure out what is going on.
the problem is i am using bash as my login shell
(of course, this is my problem, pure and simple, but i am trying to be
modern and submit my fate to the feckless taste of GNU software)
and i am afflicted with a weird double echo of input.
my TERM=dumb.
here is some sample input/output:

> zeno-23_andrew=; date
> date
> Wed May  1 19:06:48 EDT 2013


but when i run script, there is no double echo:

> zeno-23_andrew=; script poot
> script poot
> Script started, file is poot
> zeno-23_andrew=; date
> Wed May  1 19:06:59 EDT 2013
> zeno-23_andrew=; exit
> Script done, file is poot


sweet! and poot has the expected contents:

> Script started on Wed May  1 19:06:55 2013
> zeno-23_andrew=; date
> Wed May  1 19:06:59 EDT 2013
> zeno-23_andrew=; exit
> 
> Script done on Wed May  1 19:07:02 2013


of course straight after the script command, the double echo resumes:

> zeno-23_andrew=; exit
> Script done, file is poot
> zeno-23_andrew=; date
> date
> Wed May  1 19:07:05 EDT 2013
> zeno-23_andrew=; 


does anyone know what the frick is going on?
it seems unaffected by set +o vi or set +o emacs.

i normally use ksh, which although it has its own voibles, at least
affords me the opportunity to harrangue korn if it misbehaves
and whack him if its his fault. but i digress.

hopefully, someone has seen this before and knows how to fix this.
(and yes, i've read the wretched turgid bloated man page to no avail.)

-----------------------
Andrew Hume
623-551-2845 (VO and best)
973-236-2014 (NJ)
and...@research.att.com



_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to