On Wednesday 20 Jul 2011 20:53:06 Sean Carolan wrote:
I had this in my bash history:
IFS='\n'
That seems to have been the cause of the missing n's.
I know you used python in the end, but for the record this should have been:
IFS=$'\n'
i.e. the \n has to be expanded to a newline,
On Wednesday, July 20, 2011 03:23:58 PM Sean Carolan wrote:
[snip]
Where did all the letter n's go?
I can't duplicate the problem here on a CentOS 5.6 box. What locale are you
set to? Here's what I get (note that a copy from the e-mail you sent embedded
newlines, which had to be stripped out
2011/7/20 Lamar Owen lo...@pari.edu:
On Wednesday, July 20, 2011 03:23:58 PM Sean Carolan wrote:
[snip]
Where did all the letter n's go?
I can't duplicate the problem here on a CentOS 5.6 box. What locale are you
set to? Here's what I get (note that a copy from the e-mail you sent
Sean Carolan wrote:
This is kind of odd.
[scarolan@host:~]$ cat loremipsum.txt
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec quis
ipsum sed elit laoreet malesuada. Quisque rhoncus dui vitae eros
euismod fermentum sollicitudin sem scelerisque. Nulla facilisi.
Maecenas
[scarolan@server:~]$ echo $myvar
Lorem ipsum dolor sit amet, co sectetur adipisci g elit.
lots of letter !
Weird huh?
Ok, I'm a bonehead; I had this in my bash history:
IFS='\n'
That seems to have been the cause of the missing n's. Now the next
question would be, how can I include the \n
--On Wednesday, July 20, 2011 02:53:06 PM -0500 Sean Carolan
scaro...@gmail.com wrote:
Now the next
question would be, how can I include the \n characters in my variable
string, without fudging with $IFS?
Can you describe, functionally and a bit higher level, what you're
trying to achieve?
(No, I don't advocate perl for everything, but knowing more about the
problem can
help in determining a suitable solution.)
You're right, I gave up and used python instead. The basic idea here
was to gather together a long list of hostnames by grepping through a
few hundred files, check the
7 matches
Mail list logo