From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1123 invoked by alias); 10 Nov 2015 19:54:42 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20946 Received: (qmail 23843 invoked from network); 10 Nov 2015 19:54:39 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0 a=Rb7dudWe+J2gL+/7yVpO1Q==:117 a=Rb7dudWe+J2gL+/7yVpO1Q==:17 a=N659UExz7-8A:10 a=GcyzOjIWAAAA:8 a=hcEHYXgVW4YndwovyaMA:9 a=pILNOxqGKmIA:10 a=o-YXdGfRABcA:10 Message-id: <56424470.7020909@eastlink.ca> Date: Tue, 10 Nov 2015 11:24:32 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-version: 1.0 To: zsh-users@zsh.org Subject: Re: zcurses keycodes References: <5641407E.4030107@eastlink.ca> <20151110093634.6490fe9d@pwslap01u.europe.root.pri> In-reply-to: <20151110093634.6490fe9d@pwslap01u.europe.root.pri> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 8bit On 11/10/2015 01:36 AM, Peter Stephenson wrote: > On Mon, 9 Nov 2015 16:55:26 -0800 > Ray Andrews wrote: >> I'm looking at a list of allowable keys in Sebastian's stuff, It includes: >> >> EOT >> NAK >> DLE > Hmm... *those* look like ASCII key names rather than curses key > definitions. Try "man ascii" or > > http://man7.org/linux/man-pages/man7/ascii.7.html > > pws > Thanks Peter, yeah I know they're ASCII, but there seems to be a conflict, or one of those situations where one has no idea who owns a key. I tried to add 'EXT' (^C of course), but it wouldn't take. The ones I mention show up in my editor as bright white boxes--clearly they are recognized as special--but no luck with EXT (tho I could capture ^C with " ${\x0A} "). case "$NKEY" in (${\x0A}) ACTION='QUIT'; REPLY=-1 ;; ($'\n') REPLY=$IN[currentE]; ACTION='' ;; ($'\b'||BACKSPACE) SEARCH_BUFFER="${SEARCH_BUFFER%?}" ;; (ETB) [ "$SEARCH_BUFFER" = "${SEARCH_BUFFER% *}" ] &&\ " ETB " had to be added ... it didn't actually paste over, because I understand that it's some symbol, not literal text. Point is that " ETB " 'works', but not " EXT ". So, I'm wondering who/where I'm not getting control of ^C via 'EXT' in zcurses. Also, ^C behaves very strangely. " zcurses input " treats ^C differently depending on whether the call is inside a function or not. In some situations it creates a repetition of the previous keystroke. Sometimes it exits the program, sometimes it's just ignored. I was hoping that there'd be some zcurses/ncurses list of all accepted keys, where I'd hope to see some mention of the ASCII acronyms and in particular what's going on with ^C. I'd suspect that something else, like the terminal, is getting in the way, but, again, I can handle ^C my way with " ${\x0A} " so it seems to be under my/zcurses control.