Search Results

Some more playing around and I'm also seeing the \r characters being truncated - BINMODE seems to help with GNU awk:

awk '{gsub(/\n/,"|"); gsub(/\r\|/,"\n"); print}' RS='' BINMODE=1 file

Try:
awk '{gsub(/"/,q,$NF); gsub("^" q "|" q "$","\"",$NF)}1' FS=, OFS=, q=\' file

You can read about quite a few of them here Xterm Control Sequences (http://www.xfree86.org/4.7.0/ctlseqs.html)

This worth a try if it is rows and columns.
#!/bin/bash
# Set window size down to 66 cols x 32 rows, not tested on mintty but worth a try...
printf "\x1B[8;32;66t"
# Write into the title bar;...

Well I won't pick apart at your code too much more then. ;)

To answer the question on whitespace, awk shouldn't be messing with them aside from the default FS being equivalent to...

But - hasn't that been shown to you in posts #2 and #3?
awk -vb=XXX 'BEGIN {a=b?b:"Default"; print a}'
XXX
awk 'BEGIN {a=b?b:"Default"; print a}'
Default

First, you have an extra dollar sign (shown in red above) that shouldn't be there.

Second: your default if empty string is misleading. With the form argument=${parm-word}, word is assigned only...

Well you could us the ? operator like this:

argument=length($1) ? $1 : "default if empty"

or like this:

argument=$1~"^$" ? "default if empty" : $1

Hi,
ternary operator is:
Condition ? one and only one true expr : one and only one false expr
you must have false expr also:
hour >= 12? amPm=" PM" : amPm=" AM"
hour >= 12? hour = hour - 12 : 0...

Ireland is currently UTC+1 while Phoenix is UTC+7 so the date displayed is correct.

Try:

$ TZ="Europe/Dublin" date
Mon, Apr 13, 2015 11:27:51 PM

It is unclear why you want to convert your local time to the time in Ireland. If what you really want is to display the current time in Ireland, the proper command would be:

TZ="Europe/Dublin" date

How do you know it does not work? If you are printing the content of the variable dump that also needs to be quoted:
echo "$dump"

It gets the value of the variable "expand" and treats this as a variable name and the fetches its value.

So
$ t=5
$ x=t
$ y=x
$ echo ${!x}
5
$ echo ${!y}
t

since you're using bash I'd say <<< "$string" is a much better option than < <(echo "$string").


$ IFS=: read -raa <<< "$PATH"
$ declare -p a
declare -a a='([0]="/home/mute/bin"...

Love the f_Parse function Bakunin. It got me thinking about a quoted_read function that works like read but supports quoted strings so I could call it like this

test='one two three four five...

What you describe is a (very simple) parser. The following sketch roughly does what you want, you will want to put it into a function in you script. I wrote it for ksh initially, so you will probably...

It's not whether it "likes" it or not. It's because of the order shell processes a statement.

The temporary IFS assignment only becomes valid when the statement is executed -- but in order to...

And where do you get this string? Perhaps it could be parsed in the first place instead of later.

Actually, I didn't know that either.

That's something totally different from what I was...

That is not because of read, but because the right hand side of the pipe is executed in a subshell in bash and some other bourne type shells. It works in ksh though...

--
Note that IFS=":"; read...

It has to, to avoid deadlocks. Which runs first, the echo or the read? Will either of them hang, waiting for the other? Make them independent and it doesn't matter.

Consider what happens when you do a |

echo a b c | some program

If "some program" were cat, would it change any memory or variables in your current shell? Of course not, it doesn't have access...

I'd suggest not using eval at all, just code your own allowed expansions e.g.:

expand='$RANDOM'
[ ${expand:0:1} = "$" ] && {
expand=${expand:1}
expand=${!expand}
}

So here we support...

Try echo -e "hello\ngoodbye\n####\ntesting" | while read line && [ "$line" != "XXXX" ]; do echo "$line"; done
hello
goodbye
####
testing

xargs -0 ( gnu xargs supports this )