[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help fixing NativeMessaging host: read 32-bit message length in nati
From: |
Lawrence Velázquez |
Subject: |
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order |
Date: |
Sat, 24 Jun 2023 20:38:31 -0400 |
User-agent: |
Cyrus-JMAP/3.9.0-alpha0-499-gf27bbf33e2-fm-20230619.001-gf27bbf33 |
On Sat, Jun 24, 2023, at 7:22 PM, guest271314 wrote:
> Thanks. Can you explain why the double quoting of assigned variables is
> impotant?
>
> On Sat, Jun 24, 2023 at 3:59 PM dan b <tekvax@hotmail.com> wrote:
>
>> “Important safety tip #427” :)
>>
>> Remember to always double quote around assigned variables.
>> The life you save maybe your own…
>> I was just caught by this in a while done read csv file variable, because
>> I failed to double quote the data=“$line” assignment, the string contents
>> were getting changed in strange ways.
To my knowledge, the following simple assignments are equivalent
to bash, although they may not be in other shells in certain
circumstances.
data=$line
data="$line"
Perhaps Dan is underexplaining or misattributing the quoting issue
he encountered.
--
vq
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, (continued)
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/25
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, dan b, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order,
Lawrence Velázquez <=
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, dan b, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Lawrence Velázquez, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Greg Wooledge, 2023/06/24
- Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, dan b, 2023/06/24
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, guest271314, 2023/06/24
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, Grisha Levit, 2023/06/24
Re: Help fixing NativeMessaging host: read 32-bit message length in native byte order, alex xmb ratchev, 2023/06/26