Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: echotc/echoti
- X-seq: zsh-users 11994
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: echotc/echoti
- Date: Thu, 11 Oct 2007 23:06:10 -0700
- In-reply-to: <20071012030026.GA352@xxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20071011203036.19802.qmail@xxxxxxxxxxx> <20071012030026.GA352@xxxxxxxxxxx>
On Oct 11, 11:00pm, Clint Adams wrote:
} Subject: Re: echotc/echoti
}
} On Fri, Oct 12, 2007 at 09:30:33AM +1300, Atom Smasher wrote:
} > what are the differences (practical, theoretical, etc) between:
} >
} > % echotc xxx
} > % echoti yyy
} > and
} > % print -n ${termcap[xxx]}
} > % print -n ${terminfo[yyy]}
}
} echotc and echoti output the capability strings directly to the
} terminal, with output padding.
Well, directly to standard output, which is assumed to be the terminal.
echotc and echoti are also capable of replacing positional arguments
into the termcap/terminfo string. E.g.
echotc cm 12 20
or
echoti cup 12 20
places the cursor in row 12 column 20.
You can probably work out how to do this with some sort of replacement
on ${terminfo[cup]} but it won't be pretty.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author