Sorry, never mind, folks... I told you it was probably a basic
misunderstanding on my part.
All I gotta do is:
parse/all line [thru "^-" copy price]
and it does precisely what I want it to.
<g>
I'm learning!
To explain it to those that might be interested. In parsing the line with
one tab embedded in it, I was not really losing the tab (just did not show
up when I printed because it was converted to spaces in the output). What my
error really was was not specifying the /all for parse. Thus all spaces and
various punctuation symbols were affecting my output and confusing both
Rebol and me. The parse/all usage splits the line neatly at the tab and I
then copy the price into a variable named price.
--Ralph
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 22, 1999 1:47 PM
> To: [EMAIL PROTECTED]
> Subject: [REBOL] tabs -- something basic or a bug? Re:
>
>
> that, of course should be:
>
> parse line [thru "^-" copy price"]
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, October 22, 1999 12:37 PM
> > To: [EMAIL PROTECTED]
> > Subject: [REBOL] tabs -- something basic or a bug?
> >
> >
> > This could be a basic misunderstanding on my part, but it's driving me
> > crazy...
> >
> > simple operation:
> >
> > I read in a text file into a variable using read/lines. At the
> end of each
> > line is a tab and a price.
> >
> > I want to strip out the prices and save to a variable.
> >
> > Easy enough, one would think. First get the line by pick. Then parse the
> > line with the statement:
> >
> > parse line [thru "^" copy price]
> >
> > works quite nicely THE FIRST TIME but then I find that ALL the
> > tabs are gone
> > not just from the line but the variable containing all the lines read in
> > from the text file.
> >
> > Is this like a bug or do I need to do something to preseve my tabs until
> > each line is processed?
> >
> > --Ralph
> >
>
>
>
