Path: csiph.com!news.mixmin.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++ Subject: Re: Parsing multi-byte keystrokes Date: Sat, 01 Jul 2023 11:58:48 -0700 Organization: None to speak of Lines: 62 Message-ID: <87zg4fqx07.fsf@nosuchdomain.example.com> References: <1t4nM.1647$fNr5.933@fx16.iad> <8735293xdb.fsf@bsb.me.uk> <877crksmps.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: dont-email.me; posting-host="b7dd3dc39b8f7f61e15fc922c859854e"; logging-data="3163474"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/UBOHJdlR2O+jzTBfZ9ZX1" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:U2HmJ9wjMDQ/7hJMNvqEV8uvsI8= sha1:Tgcu9WJXi4lAo8ED7G95HOJa5jE= Xref: csiph.com comp.lang.c++:90810 "R.Wieser" writes: > Keith, > >>> I assumed that a good percentage of users here would be using Linux, >>> and the question would make sense to them. I must have assumed wrong. >> >> And yet you're still posting here and *not* posting in an appropriate >> place. Why? > > Are you telling me I should just have stopped responding here and taken off > to that other newsgroup ? Where I live thats considered rude going on > offensive. You could post a single message on this thread saying that you're going to continue the discussion in comp.unix.programmer. Or you could cross-post a message to comp.lang.c++ and comp.unix.programmer, with followups directed to comp.unix.programmer. You can still do that. It would be far less rude than what you're doing now. >> You see, this is why you should leave attribution lines alone. Alf >> Steinbach didn't write that. I did. (He quoted it in a followup.) > > Funny, I took his name from your post, where the attribution lines where > (ofcourse) present ... > > But yes, I made a mistake. As you say, it was you who wrote that, in a > response to Alf. My apologies. > > ... But do I at least get points for using the correct date ? :-) You get no points for continuing to deliberately flout longstanding Usenet conventions. >> I have no problem with using a cannon to kill a mosquito. If >> ncurses had a good way to detect arrow key input without taking >> over the whole screen, I'd recommend that. > > And in that "no taking over of stuff" case I would most likely have used it. > >> Thomas Dickey, in response to a question I posted on Stack Overflow >> a few years ago, suggested something that might be the basis of a >> solution: > > Both of those links seem to end up showing the same content. The first link was to my question, the second to Thomas Dickey's answer. They both appear on the same web page. > I skipped the ncurses part, as it, as mentioned by yours truly, wants to > take over the screen. The "How to distinguish between escape and escape > sequence" link shows some code, but as mentioned, I've already got that part > down. You skipped the part where Thomas Dickey demonstrated using ncurses without taking over the screen. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Will write code for food. void Void(void) { Void(); } /* The recursive call of the void */