emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Re: [babel] Sh problem when echo'ing input data with ' ins


From: Eric Schulte
Subject: Re: [Orgmode] Re: [babel] Sh problem when echo'ing input data with ' inside
Date: Mon, 17 Jan 2011 12:54:23 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

>>
>> and the sh code block expands to the following (with C-c C-v v) which is
>> not affected by commas...
>
> I've no trouble with commas, except that it's not an American formatting for
> amounts. Though, I does well have problems, as showed, with the apostrophe...
>

Sorry, I mis-typed, as far as I can tell the apostrophe works on my
machine without causing any issues.

>
> Previewing does work for me as well:
>
>> #+begin_src sh
>>   data=$(cat <<BABEL_STRING
>>   Num.ro du compte :;979-9500975-24;Compte Maxi
>>   Date valeur;R.f.rence de l'op.ration;Description;Montant de
>> l'op.ration;Devise;Date d'op.ration;Compte de contrepartie;Nom de la
>> contrepartie :;Communication 1 :;Communication 2 :
>>   04-06-2009;A9F04NT01WK300TG;Virem. 
>> internet;420,00;EUR;04-06-2009;799-5900947-23;PAYEE ONE; ; 
>>   24-02-2009;A9B24NT012K4018Z;Virem. 
>> internet;-54,93;EUR;24-02-2009;799-9974005-30;ME;Eigen rekening; 
>>   18-05-2008;A8E19NT000S604QI;Virem. 
>> internet;-1.000,00;EUR;19-05-2008;799-8068445-18;PAYEE TWO; ;
>>   BABEL_STRING
>>   )
>>   echo "$data"
>> #+end_src
>

if you execute the previewed code block as an independent shell script
on your machine does it throw errors or does it echo correctly?

>
> Evaluation does not.
>
>> Are you on a windows machine?  I'm not sure what else could be different
>> about the shell environment on our machines.
>
> Yes, it is on Windows ;-)  Though, with Cygwin bash support... which should
> behave as on any Linux...
>
>> note: some of the characters in your email weren't printable when I
>> tried to send this with gnus, so they've been replaced with "."s
>
> These are French accentuated letters.
>
>>> Any idea on how to:
>>> - circumvent such problem?
>>> - or, eventually, do this better?
>
> No idea on any workaround, then?  ;-(
>

I can't reproduce the problem locally, and I believe that this is due to
differences in our shell environments rather than Emacs-specific issues,
so it is hard for me to diagnose or propose a solution.

Sorry I can't be of more help -- Eric

>
> Best regards,
>   Seb



reply via email to

[Prev in Thread] Current Thread [Next in Thread]