On Tuesday 31 May 2005 01:01, Paul M Foster wrote:
> On Tue, May 31, 2005 at 12:44:22AM -0400, Paul M Foster wrote:
> > On Tue, May 31, 2005 at 12:10:26AM -0400, Bob Stia wrote:
> > > On Monday 30 May 2005 10:27, Eben King wrote:
> > > > On Mon, 30 May 2005, Paul M Foster wrote:
> > > > > I agree, you should recreate the script in something that
> > > > > won't mess with the content. There are tons of programs like
> > > > > this, designed strictly to output straight text. Most of them
> > > > > are console programs. There are vi, emacs, nano, pico, joe,
> > > > > vim, etc. etc.
> > > >
> > > > Unless you want to learn vi(m) or emacs, I recommend a WYSIWYG
> > > > editor, such as nano, pico, nedit, etc. Be sure to tell it
> > > > _not_ to wrap long lines.
> > >
> > > Eben, Paul, Rob and others who kindly tried to help me with this
> > > strange problem.
> > >
> > > It is finally solved but I really don't know why. Has to do with
> > > some strange hidden commands unseen in the script. I discovered
> > > it when I posted the script to a webpage for Eben to look at. And
> > > it only showed up in the webpage composer.
> > >
> > > When I put the script text onto the webpage composer I noticed
> > > some strange html markup in the script. Grey vertical lines
> > > before and after text within the script. Tonight I took the
> > > script text that Paul had composed an put it on an html page in
> > > the webpage composer. Same strange grey vertical lines in the
> > > html markup. So, there was something in there that was hidden
> > > even to Paul.
> >
> > Glad you got this solved!
> >
> > I checked the copy of the script I sent you privately in hex before
> > sending it. There was nothing untoward about it, nothing there that
> > shouldn't have been. Your response then tells me two things. First,
> > there _was_ something hidden in your original script (not the one I
> > sent you); I was incorrect in thinking that it was carriage
> > returns. Second, your email setup is hacking this stuff up. You
> > mentioned in an email to me that running the copy of the script I
> > sent you gave you the same errors. Since I can vouch for what left
> > my machine by email, something happened to it between the time it
> > arrived at your machine and the time you tried to run it, that put
> > errant characters in it.
>
> ACH! I was completely wrong here! I was puzzled after sending this
> message, so I took _one more look_ at the script copy I sent you. I
> had originally looked at it in hex, but not thoroughly enough.
> Interspersed in the file are hex A0 (sic) characters in some of the
> beginnings of the lines. This is like a space character with the high
> bit set, or an accented "a" in the IBM character set. But it doesn't
> show up in my editor (nano), nor in my email client (mutt), nor in
> the less command. Bash is seeing this character and thinking it's the
> name of a command, then giving you the errors you got.
>
> My apologies. I should have looked more carefully at your original
> script and the copy I sent you. Both have this problem.
>
Paul,
No apologies necessary. Thanks for your effort. Many of the Sluggers
here finally led me to find the problem. Could not have done it without
your collaborative help. Would have been frustrated and wondering
forever what was wrong and never had found out. I certainly learned a
lot.
FYI, I went back and found the original email that I copied the script
from and examined it. (before I modified it for my own use) The errors
were there when I "lifted" it !! Sooo,and I will never know, maybe it
wasn't my email client but the originator's who put that unseen hidden
junk in there.
It is still mind-boggling to me that this kind of stuff can happen and
be undetected. Anyway, I am learning. Have patience with me the next
time I pose a weird question.
Bob S.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:57:27 EDT