Re: [Yaml-core] YAC#21: #TAB

[Brian I. <in...@tt...>]

On 06/03/02 07:32 -0500, Oren Ben-Kiki wrote:
> Clark C . Evans [mailto:cc...@cl...] wrote:
> Option 0 (8-space tabs):
>     Interop: 3
>     Cut&paste: 3
>     View: 1+ (All text viewers work. Some editors don't).
>     Edit: 1 (TASTY editors mostly work).
>     Score: 8
> 
> Option 1 (mixing is error):
>     Interop: 3
>     Cut&paste: 1 (invisibly fails between spaced and tabbed).
>     View: 3
>     Edit: 0 (All editors need care of configuration)
>     Score: 7
> 
> Option 5 (disallow tabs):
>     Interop: 3
>     Cut&paste: 3
>     View: 3
>     Edit: 0 (all editors need to be configured or great care must be taken).
> Score: 9
> 
> 
> Brian gave two proposals I don't quite understand... What does "no mixing
> for blocks" mean, exactly? I also don't see how explicit indentation helps
> any. Could you elaborate?

I gave one proposal and one insight. The insight was:

Option 1 is impossible because of our explicit block notation. One must 
use spaces or "tabs converted to spaces" because the indentation level
is specified in terms of spaces. Get it?

---
foo:
        bar: ]1 
            The quick brown yaml
         jumped over the lazy xml.
...
The proposal was that we combine options 0 and 5. Option 5 for multiline
leafs (where tabs can cross the border) and Option 0 for everything
else. Since only more sophisticated users (non config file applications)
would use multiline blocks it might make sense to do this.

FWIW, I'm not completely opposed to Option 5 for everything. It
definitely draws a line in the sand, but maybe that's ok.

Cheers, Brian