could chirp be modified to accept these invalid csv files that are short fields?
It seems like a common problem to have (for many reasons) and an unabiguous fix,
even if it technically violates the spec

David Lang

  On Sun, 19 Dec 2021, Dan Berry wrote:

> Date: Sun, 19 Dec 2021 18:35:22 -0700
> From: Dan Berry <dgberry@gmail.com>
> Reply-To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
> To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
> Subject: Re: [chirp_users] No channels
>
> I'll give it a try.
>
> Dan
>
> On Sun, Dec 19, 2021, 6:29 PM Jim Unroe <rock.unroe@gmail.com> wrote:
>
>>
>>
>> On Sun, Dec 19, 2021 at 6:57 PM Dan Berry <dgberry@gmail.com> wrote:
>>
>>> Here is my csv file.
>>>
>>> Dan
>>> KI7TQX
>>>
>>>
>> The trailing commas were removed from each of the rows making the whole
>> CSV file invalid. The quickest way to fix it is to remove the equivalent
>> number of header names.
>>
>> Jim KC9HI
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users@intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Dan at dgberry@gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe@intrepid.danplanet.com
>
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Dan at dgberry@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com