On Sun, Aug 11, 2019 at 7:51 PM Michał Górny <[email protected]> wrote:
> On Sun, 2019-08-11 at 17:53 -0500, William Hubbs wrote: > > On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote: > > > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs <[email protected]> > wrote: > > > > If we are going to require a modeline, shouldn't we consider allowing > > > > them by default so we can work out of the box instead of having to > tweak > > > > our editor settings? > > > > > > Perhaps we should. Is this really an important point for you? > > > > > > I don't think any of that needs to hold up Michał's proposal though. > > > > Let's move away from talking about alignment for a minute. > > > > The reason I responded originally was that his proposal is a bit > > vague. It says that whitespace separates fields; that could be spaces > > or tabs. whitespace can also be a completely valid character in > > the notes field. So, since he says we can add more fields in the future, > > you either have to escape whitespace in the notes field or quote the > > field. > > We can add new fields *in the middle*. That's why there's explicit > header line. > > > Also, he may have used one whitespace character to separate fields in his > > example, but the spec allows any number of whitespace characters. > > > > awk does not have a problem with that. > I would advise against making new "specs" and use an existing spec. CSV, JSON and YAML are both popular machine-and-people readable specifications with broad support. -A > > > -- > Best regards, > Michał Górny > >
