From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: termcap bug on Linux
Date: Wed, 30 May 2001 07:41:02 +0000 [thread overview]
Message-ID: <1010530074102.ZM1290@candle.brasslantern.com> (raw)
In-Reply-To: <000001c0e8d1$33b431b0$21c9ca95@mow.siemens.ru>
On May 30, 10:24am, Andrej Borsenkow wrote:
}
} > On May 28, 10:25pm, Bart Schaefer wrote:
} >
} > Should I commit the patch?
}
} Yes.
OK, but sourceforge seems to be either inaccessible or at a painful crawl
just now, so I'm not going ot get to it for at least several hours.
} About scantermcap - I am not sure. Currently it returns "no" for both
} unexisting and unset flags; if we change this as well, it will return
} nothing for unexisting flags.
I'd say we do need to change it, then ... scantermcap() should produce
the same results as doing $termcap[$cap] for every possible $cap.
} I am not sure how useful $termcap is at all, given that there is no
} way to associate returned values with capabilities.
I don't think I understand what you mean. Do you mean, there's no way
to tell whether a returned value should be interpreted as a boolean, a
number, or a string? That is a shortcoming, it's true.
Parameterized capabilities like "move N columns left" really require
`echotc' to insert the N in the right place, too.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-05-30 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 13:09 Andrej Borsenkow
2001-05-28 22:25 ` Bart Schaefer
2001-05-29 16:05 ` Bart Schaefer
2001-05-29 18:56 ` Clint Adams
2001-05-30 6:24 ` Andrej Borsenkow
2001-05-30 7:41 ` Bart Schaefer [this message]
2001-05-30 8:03 ` Andrej Borsenkow
2001-05-30 14:00 ` Clint Adams
2001-05-30 15:29 ` Bart Schaefer
2001-05-30 19:54 ` PATCH (again) " Bart Schaefer
2001-05-29 18:06 ` Andrej Borsenkow
2001-05-29 20:12 ` Clint Adams
2001-05-29 18:48 ` Clint Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1010530074102.ZM1290@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).