| 1 |
On Sun, Aug 11, 2019 at 7:51 PM Michał Górny <mgorny@g.o> wrote: |
| 2 |
|
| 3 |
> On Sun, 2019-08-11 at 17:53 -0500, William Hubbs wrote: |
| 4 |
> > On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote: |
| 5 |
> > > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs <williamh@g.o> |
| 6 |
> wrote: |
| 7 |
> > > > If we are going to require a modeline, shouldn't we consider allowing |
| 8 |
> > > > them by default so we can work out of the box instead of having to |
| 9 |
> tweak |
| 10 |
> > > > our editor settings? |
| 11 |
> > > |
| 12 |
> > > Perhaps we should. Is this really an important point for you? |
| 13 |
> > > |
| 14 |
> > > I don't think any of that needs to hold up Michał's proposal though. |
| 15 |
> > |
| 16 |
> > Let's move away from talking about alignment for a minute. |
| 17 |
> > |
| 18 |
> > The reason I responded originally was that his proposal is a bit |
| 19 |
> > vague. It says that whitespace separates fields; that could be spaces |
| 20 |
> > or tabs. whitespace can also be a completely valid character in |
| 21 |
> > the notes field. So, since he says we can add more fields in the future, |
| 22 |
> > you either have to escape whitespace in the notes field or quote the |
| 23 |
> > field. |
| 24 |
> |
| 25 |
> We can add new fields *in the middle*. That's why there's explicit |
| 26 |
> header line. |
| 27 |
> |
| 28 |
> > Also, he may have used one whitespace character to separate fields in his |
| 29 |
> > example, but the spec allows any number of whitespace characters. |
| 30 |
> > |
| 31 |
> |
| 32 |
> awk does not have a problem with that. |
| 33 |
> |
| 34 |
|
| 35 |
I would advise against making new "specs" and use an existing spec. |
| 36 |
CSV, JSON and YAML are both popular machine-and-people readable |
| 37 |
specifications with broad support. |
| 38 |
|
| 39 |
-A |
| 40 |
|
| 41 |
|
| 42 |
> |
| 43 |
> |
| 44 |
> -- |
| 45 |
> Best regards, |
| 46 |
> Michał Górny |
| 47 |
> |
| 48 |
> |
Archives