Hi Christian,
sorry for the delay caused by holidays.
Christian Weisgerber wrote on Thu, Aug 07, 2008 at 03:53:00PM +:
> Ingo Schwarze <[EMAIL PROTECTED]> wrote:
>> What i do not yet understand is why xterm has -oxtabs
>> by default but the terminfo(5) database has no OTpt for it.
>> Isn't t
Ingo Schwarze <[EMAIL PROTECTED]> wrote:
> In other words, a tab never makes xterm wrap to the next line.
This matches VT220 behavior.
> What i do not yet understand is why xterm has -oxtabs
> by default but the terminfo(5) database has no OTpt for it.
> Isn't that inconsistent?
I don't follow.
Sorry for not noticing at once, but here we go:
Stuart Henderson wrote on Wed, Aug 06, 2008 at 03:00:43PM + concerning
$ printf "1\t\t\t\t\t\t\t\t\t1234567\t123"
> Looks like an xterm bug. This works ok in a normal console,
> and works ok in screen in a normal console, but fails in an
> xterm
Stuart Henderson wrote on Wed, Aug 06, 2008 at 03:00:43PM +:
> Let's make it easier for people to test;
> $ printf "1\t\t\t\t\t\t\t\t\t1234567\t123"
Or even:
$ printf "\t\t\t\t\t\t\t\t\t\tX\n"
These are ten tabs. Each tab is supposed to be 8 characters wide.
Thus, the X is supposed to app
Stuart Henderson <[EMAIL PROTECTED]> wrote:
> Looks like an xterm bug. This works ok in a normal console,
> and works ok in screen in a normal console, but fails in an
> xterm or screen in an xterm.
>
> Let's make it easier for people to test;
>
> $ printf "1\t\t\t\t\t\t\t\t\t1234567\t123"
I ha
On 2008-08-06, Markus Lude <[EMAIL PROTECTED]> wrote:
> while using grep on tab separated data I spotted some strange thing
> today. Somehow the last tab isn't displayed:
>
> $ echo "1 1234567
> 123"
> 1
Markus Lude wrote:
Hello,
while using grep on tab separated data I spotted some strange thing
today. Somehow the last tab isn't displayed:
$ echo "1 1234567
123"
1
Hello,
while using grep on tab separated data I spotted some strange thing
today. Somehow the last tab isn't displayed:
$ echo "1
1234567 123"
1
1234567123
8 matches
Mail list logo
