From: Clint Adams <clint@zsh.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: make curses module not need wideness
Date: Mon, 15 Oct 2007 09:25:42 -0400 [thread overview]
Message-ID: <20071015132542.GA2882@scowler.net> (raw)
In-Reply-To: <071014151608.ZM26588@torch.brasslantern.com>
On Sun, Oct 14, 2007 at 03:16:08PM -0700, Bart Schaefer wrote:
> I'm not having much luck with this. The doc should mention that window
> zero is automatically created as the whole terminal. Also there's no
> check that the targetwin argument is really an integer; I typo'd a "q"
> for a "1", got some errors about the window already existing (apparently
> because non-integers are read as "0"), and ended up with a core dump:
I'll just disallow specification of window 0 for now.
> The doc for "zcurses -m" says "moves targetwin to new coordinates" but
> really it positions the cursor within the target window, doesn't it?
> Maybe better phrasing is all that's needed.
Agreed.
> Also I none of the strings I send with "zcurses -s" show up in the
> window. A border added with "zcurses -b" will display, but that's all.
> "zcurses -c" has a similar problem.
As I perhaps failed to express before, -c and -s work fine for me with
non-wide ncurses, and only -c functions properly with wide ncurses.
Index: Doc/Zsh/mod_curses.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/mod_curses.yo,v
retrieving revision 1.1
diff -u -r1.1 mod_curses.yo
--- Doc/Zsh/mod_curses.yo 14 Oct 2007 17:14:22 -0000 1.1
+++ Doc/Zsh/mod_curses.yo 15 Oct 2007 13:20:15 -0000
@@ -26,7 +26,8 @@
make any pending changes (such as characters you have prepared for output
with tt(-c)) visible on the screen.
-tt(-m) moves var(targetwin) to new coordinates var(new_y) and var(new_x).
+tt(-m) moves the cursor position in var(targetwin) to new coordinates
+var(new_y) and var(new_x).
Outputting characters and strings are achieved by tt(-c) and tt(-s)
respectively.
Index: Src/Modules/curses.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Modules/curses.c,v
retrieving revision 1.4
diff -u -r1.4 curses.c
--- Src/Modules/curses.c 14 Oct 2007 04:24:47 -0000 1.4
+++ Src/Modules/curses.c 15 Oct 2007 13:20:15 -0000
@@ -78,7 +78,7 @@
target = (unsigned)atoi(win);
- if (target > ZCURSES_MAX_WINDOWS) {
+ if (target > ZCURSES_MAX_WINDOWS || target < 1) {
zc_errno = ZCURSES_ERANGE;
return -1;
}
next prev parent reply other threads:[~2007-10-15 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 4:21 Clint Adams
2007-10-14 16:26 ` Bart Schaefer
2007-10-14 17:08 ` Clint Adams
2007-10-14 22:16 ` Bart Schaefer
2007-10-15 9:11 ` Peter Stephenson
2007-10-15 13:35 ` Clint Adams
2007-10-15 14:34 ` Clint Adams
2007-10-15 14:58 ` Peter Stephenson
2007-10-15 16:45 ` Clint Adams
2007-10-15 13:25 ` Clint Adams [this message]
2007-10-15 15:04 ` Bart Schaefer
2007-10-15 16: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=20071015132542.GA2882@scowler.net \
--to=clint@zsh.org \
--cc=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).