This is related to the expand comand's behaviour when you use it to
change tab
to spaces, and specifying two spaces per tab.
The point is, the spaces inserted for a 2 spaces/tab command are
actually the same as having specified 1 space/tab. And the difference is
observed when you specify 3 spaces/
That doesn't look like a bug to me. For example, the first line
of hints.txt contains
1 . T
so there are three columns before the tab, which means that expand -t1
and expand -t2 should behave the same. Perhaps you didn't notice the
?
___
Bug-coreu
[EMAIL PROTECTED] writes:
> Yes, I knew that the space was actually there.
>
> If you use the very first line of hints.txt file, as if you had a
> column ruleguide, you may notice that the output (expand-
> bug.txt) never show the start of the sentence below the
> first five of the ruleguide.
S