From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@sunsite.dk>
Subject: Re: read -s doesn't work with -t?
Date: Sun, 17 Feb 2008 18:16:55 -0800 [thread overview]
Message-ID: <080217181655.ZM10187@torch.brasslantern.com> (raw)
In-Reply-To: <20080217172225.1d8a8e4e@pws-pc>
On Feb 17, 5:22pm, Peter Stephenson wrote:
}
} To be honest, I can't really follow all the ins and outs and if your
} patch works (checking -k in combination with other options is probably
} the key) it's probably good enough and we can see if problems turn up as
} time passes.
Does it even make sense to use -d and -k at the same time? I know it
doesn't throw an error to use both (perhaps it should) but the loop
for -k doesn't recognize delimiters (or backslashes -- perhaps the doc
should say that -k implies -r ...?).
In any case I've tested this (use of "-rk" apparently redundant):
read -st 2 -rk 3 esc$'?\e['"${seq}"t
And these:
read -srd $'\e'
IFS=';' read -Arsd t
All appear to work with the patch from users/12600, on RHEL4 linux.
So, I'll go ahead and commit.
} It would be nice to have tests but they're particularly difficult to
} write for this.
They'd probably have to use zpty and operate along the lines of the
completion tests.
next prev parent reply other threads:[~2008-02-18 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <237967ef0802151327q1c6d3a19oa67a977b82c52f67@mail.gmail.com>
[not found] ` <080215191216.ZM29994@torch.brasslantern.com>
[not found] ` <237967ef0802152333g7f759674r806f61f9f76f86f2@mail.gmail.com>
[not found] ` <237967ef0802152350i1fec3369oba9268400a209b2e@mail.gmail.com>
[not found] ` <080216093755.ZM17001@torch.brasslantern.com>
2008-02-17 17:22 ` Peter Stephenson
2008-02-18 2:16 ` Bart Schaefer [this message]
2008-02-18 9:55 ` Peter Stephenson
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=080217181655.ZM10187@torch.brasslantern.com \
--to=schaefer@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).