[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ast-developers
Subject:    Re: ksh93 printf %#q not very useful, was: Re: [ast-developers] RFE: Extend ksh93 printf %q to accep
From:       "Clark J. Wang" <dearvoid () gmail ! com>
Date:       2012-04-19 12:27:54
Message-ID: CADv8-ohaOfDS2W3KgU8=eMBHJc4qmv9QugyYu2xBaJuX9aVTcg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2012/4/19 =D0=BE=D0=BB=D1=8C=D0=B3=D0=B0 =D0=BA=D1=80=D1=8B=D0=B6=D0=B0=D0=
=BD=D0=BE=D0=B2=D1=81=D0=BA=D0=B0=D1=8F <olga.kryzhanovska@gmail.com>

> Clark, I agree that %#q is not very intuitive. Stronger said, I HATE
> it. It lacks flexibility, has no room for future extensions, is not
> very descriptive and only covers one form of csv while there are MANY
> variants of CSV,
>

I did not expect too much. But it really helps me do some simple
manipulation on the csv file exported from Gmail contacts. I ever tried to
write some shell functions myself to do that and this is the only reason
for me to wish the shell (bash or ksh) to have csv support. :)


> http://en.wikipedia.org/wiki/Comma-separated_values#Lack_of_a_standard
> tells a bit of the story.
> There is rfc4180 (http://tools.ietf.org/html/rfc4180) but it lacks
> wide spread adoption yet and does not help with the millions of
> existing csv files and software which do not use the syntax of
> rfc4180.
>
> Olga
>

[Attachment #5 (text/html)]

2012/4/19 ольга крыжановская <span dir="ltr">&lt;<a \
href="mailto:olga.kryzhanovska@gmail.com">olga.kryzhanovska@gmail.com</a>&gt;</span><br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">

Clark, I agree that %#q is not very intuitive. Stronger said, I HATE<br>
it. It lacks flexibility, has no room for future extensions, is not<br>
very descriptive and only covers one form of csv while there are MANY<br>
variants of CSV,<br></blockquote><div><br>I did not expect too much. But it really \
helps me do some simple manipulation on the csv file exported from Gmail contacts. I \
ever tried to write some shell functions myself to do that and this is the only \
reason for me to wish the shell (bash or ksh) to have csv support. :)<br>

  </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <a \
href="http://en.wikipedia.org/wiki/Comma-separated_values#Lack_of_a_standard" \
target="_blank">http://en.wikipedia.org/wiki/Comma-separated_values#Lack_of_a_standard</a><br>
 tells a bit of the story.<br>
There is rfc4180 (<a href="http://tools.ietf.org/html/rfc4180" \
target="_blank">http://tools.ietf.org/html/rfc4180</a>) but it lacks<br> wide spread \
adoption yet and does not help with the millions of<br> existing csv files and \
software which do not use the syntax of<br> rfc4180.<br>
<br>
Olga<br></blockquote></div><br>



_______________________________________________
ast-developers mailing list
ast-developers@research.att.com
https://mailman.research.att.com/mailman/listinfo/ast-developers


[prev in list] [next in list] [prev in thread] [next in thread]