Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c++ > #90713 > unrolled thread

Parsing multi-byte keystrokes

Started by"R.Wieser" <address@is.invalid>
First post2023-06-25 19:45 +0200
Last post2023-06-26 19:24 +0200
Articles 20 on this page of 143 — 19 participants

Back to article view | Back to comp.lang.c++


Contents

  Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-25 19:45 +0200
    Re: Parsing multi-byte keystrokes "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-06-25 20:34 +0200
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-25 21:39 +0200
      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 15:06 -0700
        Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-25 20:18 -0400
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 19:10 -0700
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:46 +0200
    Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-25 18:39 -0400
      Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 00:53 +0100
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 09:11 +0200
          Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 09:32 +0200
          Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 13:50 +0100
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 15:03 +0200
              Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 22:27 +0200
                Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 22:48 +0200
                  Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:35 -0700
                  Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-06-26 23:58 +0200
                    Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 16:26 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:50 +0200
        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:39 -0700
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:43 +0200
            Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-06-26 15:26 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 18:04 +0200
            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:01 -0700
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 21:59 +0200
                Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:15 -0700
                Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 22:35 +0000
                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 13:15 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:03 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:49 +0200
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:23 -0700
        Re: Parsing multi-byte keystrokes red floyd <no.spam.here@its.invalid> - 2023-06-28 14:35 -0700
          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-29 00:17 +0000
            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-29 00:43 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 14:04 +0200
                Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-29 15:44 +0000
                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 18:37 +0200
                    Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-30 14:14 +0100
                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 18:12 +0200
                        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 20:32 +0200
                        Re: Parsing multi-byte keystrokes Paavo Helde <eesnimi@osa.pri.ee> - 2023-06-30 22:57 +0300
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 09:49 +0200
                        Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-30 21:36 +0100
                        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-30 13:45 -0700
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 10:33 +0200
                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-01 11:58 -0700
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 11:03 +0200
                                Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-07-02 23:15 +0200
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 09:12 +0200
                                Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-02 15:39 -0700
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 10:12 +0200
                                    Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-03 13:28 +0000
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-03 12:43 -0400
                                Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-03 15:41 +0000
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 21:32 +0200
                                    Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-03 21:06 +0000
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 05:20 -0400
                                      Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-04 13:56 +0000
                                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 16:03 -0400
                                          Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 21:03 +0000
                                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-04 14:33 -0700
                                              Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 21:55 +0000
                                                Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 13:58 +0000
                                            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 13:56 +0000
                                    Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-04 15:54 +0000
                                      Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-04 18:03 +0200
                                        Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 16:33 +0000
                                          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-04 16:41 +0000
                                            Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-04 16:52 +0000
                                          Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-05 09:50 +0200
                                            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 14:00 +0000
                                            Re: Parsing multi-byte keystrokes "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-07-05 11:21 -0700
                                              Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-05 20:24 +0000
                                            Re: Parsing multi-byte keystrokes kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-07-05 19:31 +0000
                                        Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-04 19:05 +0000
                                      Re: Parsing multi-byte keystrokes red floyd <no.spam.here@its.invalid> - 2023-07-05 18:31 -0700
                                        Cars (Was: Parsing what is Linux?) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 08:40 +0000
                                        Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-06 08:55 +0000
                                          Cars (Was: Parsing multi-byte keystrokes) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 09:27 +0000
                                            Re: Cars (Was: Parsing multi-byte keystrokes) Muttley@dastardlyhq.com - 2023-07-06 15:43 +0000
                                              Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes)) gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-06 16:53 +0000
                                                Re: Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes)) Muttley@dastardlyhq.com - 2023-07-07 07:15 +0000
                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-06-30 17:00 -0400
                          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-01 07:53 +0000
                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-01 10:30 +0200
                            Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 04:04 -0400
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 11:27 +0200
                                Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 14:51 -0400
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 22:49 +0200
                                    Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-02 18:56 -0400
                                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 10:59 +0200
                                        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-07-03 13:34 +0000
                                        Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-03 12:20 -0400
                                          Re: Parsing multi-byte keystrokes Richard Harnden <richard.nospam@gmail.com> - 2023-07-03 18:02 +0100
                                            Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-03 14:40 -0700
                                          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 22:50 +0200
                                            Re: Parsing multi-byte keystrokes James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-07-04 05:47 -0400
                                          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-07-03 14:36 -0700
                            Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-03 11:38 +0200
                              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 13:04 +0200
                                Re: Parsing multi-byte keystrokes David Brown <david.brown@hesbynett.no> - 2023-07-03 15:11 +0200
                                Re: Parsing multi-byte keystrokes Christian Gollwitzer <auriocus@gmx.de> - 2023-07-03 20:35 +0200
                                  Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-07-03 19:16 +0000
                                  Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-03 22:55 +0200
                          Re: Parsing multi-byte keystrokes Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-07-01 03:03 -0700
                            Re: Parsing multi-byte keystrokes Muttley@dastardlyhq.com - 2023-07-01 10:30 +0000
                    Re: Parsing multi-byte keystrokes "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2023-07-01 22:37 +0200
                      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-07-02 09:42 +0200
        Re: Parsing multi-byte keystrokes Pavel <pauldontspamtolk@removeyourself.dontspam.yahoo> - 2023-06-29 22:21 -0400
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-30 17:50 +0200
    Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-25 23:20 +0000
      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-25 17:10 -0700
        Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 09:21 +0200
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:29 -0700
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:30 +0200
              Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:18 -0700
                Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 22:37 +0200
                  Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 14:32 -0700
                  Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 22:41 +0000
                    Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-29 13:58 +0200
                      Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-29 13:59 -0700
          Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 01:30 -0700
            Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:00 +0000
          Re: Parsing multi-byte keystrokes "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2023-06-26 12:31 +0200
            Re: Parsing multi-byte keystrokes "Fred. Zwarts" <F.Zwarts@HetNet.nl> - 2023-06-26 12:47 +0200
            Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:56 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 13:58 +0000
        Re: Parsing multi-byte keystrokes Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-06-26 12:08 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 08:56 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:02 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:46 +0200
            Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 18:19 +0100
              Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 18:36 +0000
              Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 21:24 +0200
                Re: Parsing multi-byte keystrokes Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-06-26 22:12 +0100
    Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-26 02:06 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 13:49 +0200
        Re: Parsing multi-byte keystrokes scott@slp53.sl.home (Scott Lurndal) - 2023-06-26 14:05 +0000
          Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 17:58 +0200
        Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-27 13:32 -0700
          Re: Parsing multi-byte keystrokes gazelle@shell.xmission.com (Kenny McCormack) - 2023-06-28 02:17 +0000
            Re: Parsing multi-byte keystrokes wij <wyniijj5@gmail.com> - 2023-06-27 20:26 -0700
      Re: Parsing multi-byte keystrokes "R.Wieser" <address@is.invalid> - 2023-06-26 19:24 +0200

Page 3 of 8 — ← Prev page 1 2 [3] 4 5 6 7 8  Next page →


#90798

FromPaavo Helde <eesnimi@osa.pri.ee>
Date2023-06-30 22:57 +0300
Message-ID<u7nc46$2kjar$1@dont-email.me>
In reply to#90793
30.06.2023 19:12 R.Wieser kirjutas:

> [quote=Alf P. Steinbach, Sun, 25 Jun 2023 15:06:29 -0700]
> curses takes over the entire (text / terminal) screen, keeping track of what
> character is shown at each location and using minimal output to update it as
> needed.
> [/quote]
> 
> Which is /absolutily not/ what I'm currently looking for.  Thats like using
> a cannon to kill a mosquito.

Yes, that's the way it goes nowadays. But ncurses is not really a 
cannon, maybe a water pistol.

$ cat `find ncurses/ -name '*.c' -o -name '*.cpp' -o -name '*.h'` | wc -l
129139

For comparison, this is a cannon:

$ cat `find aws-sdk-cpp/ -name '*.c' -o -name '*.cpp' -o -name '*.h'` | 
wc -l
15210261

That's pretty impressive for a library which just copies files from one 
place to other (at least that's what we are using it for).





[toc] | [prev] | [next] | [standalone]


#90804

From"R.Wieser" <address@is.invalid>
Date2023-07-01 09:49 +0200
Message-ID<u7op6j$2shgi$2@dont-email.me>
In reply to#90798
Paavo,

> $ cat `find aws-sdk-cpp/ -name '*.c' -o -name '*.cpp' -o -name '*.h'` | 
> wc -l
> 15210261
>
> That's pretty impressive for a library which just copies files from one 
> place to other (at least that's what we are using it for).

With that size I can only assume that it supports copying those files by 
"avian carrier" (rfc 1149) for the transport. :-)

> $ cat `find ncurses/ -name '*.c' -o -name '*.cpp' -o -name '*.h'` | wc -l
> 129139

but its not about the size, but about the "side" effects.  I don't want to 
have to relinquish control of the screen just to be able to get access to 
preparsed keystrokes.  Thats not an acceptable solution.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]


#90799

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2023-06-30 21:36 +0100
Message-ID<87fs683cxy.fsf@bsb.me.uk>
In reply to#90793
"R.Wieser" <address@is.invalid> writes:

>> As far as I can tell there /is/ a solution, but this, being a C++
>> group, is not the best one for the question so maybe no one has
>> given the details.
>
> 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.

Someone using Linux will not necessarily know about the details of
programming with curses.  It's just odd to think that an interest in C++
will correlate, significantly, with detailed knowledge about curses.

>> ncurses provides a function to do this parsing with and without
>> a timeout.  If that is not, in fact, what you want then you should
>> explain why ncurses's "keypad" setting does not do what you want.
>
> I would need to install it (its not part of the OS installation) and I've 
> heard that its a bit "demanding" :

You don't have to install it to read about it!

> [quote=Alf P. Steinbach, Sun, 25 Jun 2023 15:06:29 -0700]
> curses takes over the entire (text / terminal) screen, keeping track of what 
> character is shown at each location and using minimal output to update it as 
> needed.
> [/quote]
>
> Which is /absolutily not/ what I'm currently looking for.  Thats like using 
> a cannon to kill a mosquito.

It may not do /only/ what you want, but wanting to parse input into keys
and /not/ wanting the other stuff if rare enough that it's a reasonable
starting point.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]


#90800

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-06-30 13:45 -0700
Message-ID<877crksmps.fsf@nosuchdomain.example.com>
In reply to#90793
"R.Wieser" <address@is.invalid> writes:
>> As far as I can tell there /is/ a solution, but this, being a C++
>> group, is not the best one for the question so maybe no one has
>> given the details.
>
> 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?

>> ncurses provides a function to do this parsing with and without
>> a timeout.  If that is not, in fact, what you want then you should
>> explain why ncurses's "keypad" setting does not do what you want.
>
> I would need to install it (its not part of the OS installation) and I've 
> heard that its a bit "demanding" :
>
> [quote=Alf P. Steinbach, Sun, 25 Jun 2023 15:06:29 -0700]
> curses takes over the entire (text / terminal) screen, keeping track of what 
> character is shown at each location and using minimal output to update it as 
> needed.
> [/quote]

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.)

> Which is /absolutily not/ what I'm currently looking for.  Thats like using 
> a cannon to kill a mosquito.

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.

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:

https://stackoverflow.com/q/48715793/827263
https://stackoverflow.com/a/48716136/827263

-- 
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 */

[toc] | [prev] | [next] | [standalone]


#90806

From"R.Wieser" <address@is.invalid>
Date2023-07-01 10:33 +0200
Message-ID<u7op6k$2shgi$4@dont-email.me>
In reply to#90800
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 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 ? :-)

> 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.

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.

Thanks nonetheless.

Regards,
Rudy Wieser


[toc] | [prev] | [next] | [standalone]


#90810

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-07-01 11:58 -0700
Message-ID<87zg4fqx07.fsf@nosuchdomain.example.com>
In reply to#90806
"R.Wieser" <address@is.invalid> 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 */

[toc] | [prev] | [next] | [standalone]


#90818

From"R.Wieser" <address@is.invalid>
Date2023-07-02 11:03 +0200
Message-ID<u7rehv$3996f$2@dont-email.me>
In reply to#90810
Keith,

> You could post a single message on this thread saying that
> you're going to continue the discussion in comp.unix.programmer.

Ah yes, about that : Are you aware that Linux != Unix ?  I might well be 
told to leave that group for the same reason you are trying to eject me from 
this one ...

> You can still do that.  It would be far less rude than what
> you're doing now.

Which is ?    That I ignore your "I'm a Windows C++ programmer and could not 
care less about the Linux C++ programmers that are here" attitude ?

Something about the pot calling the kettle black ...

> You get no points for continuing to deliberately flout longstanding
> Usenet conventions.

And you get no points from trying to push such conventions upon others as if 
they are Laws.

You also should re-read it.   It rather specifically tells you that what 
they say in there are /not/ strict rules, but *guidelines* for keeping 
usenet conversations running smoothly.

And seeing how you are able to pick out my responses to you without showing 
any problems with it I think that my "just the posters name" works quite 
well.

And to be frank about it, in this newsgroup (and several others that I 
visit) you are one of less than a handfull in many years having a problem 
with it.  What does that tell you ?

IOW, you're behaving like the equivalent of a "grammar nazi".  And I don't 
like them either.

> You skipped the part where Thomas Dickey demonstrated using
> ncurses without taking over the screen.

Lol.

Third paragraph, first sentence :

"Here's a *non-working* example of what I'm trying to do."

(bolding by me).

A quick peek at the result could have told you the same :

"
Press UP, DOWN, Escape, LEFT, RIGHT
Incorrect input: (-1, -1, -1, -1, -1)
"

He even mentions the "intimately tied to taking over the entire screen" as a 
standing problem in his "update" paragraph.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]


#90822

FromChristian Gollwitzer <auriocus@gmx.de>
Date2023-07-02 23:15 +0200
Message-ID<u7spco$3dqj1$1@dont-email.me>
In reply to#90818
Am 02.07.23 um 11:03 schrieb R.Wieser:
> Keith,
>> You skipped the part where Thomas Dickey demonstrated using
>> ncurses without taking over the screen.
> 
> Lol.
> 
> Third paragraph, first sentence :
> 
> "Here's a *non-working* example of what I'm trying to do."
> 
> (bolding by me).

Is it your first time you read StackOverflow? Of course, the one who 
asks the question has a non-working solution. You should read the 
answer, not the question.



	Christian

[toc] | [prev] | [next] | [standalone]


#90825

From"R.Wieser" <address@is.invalid>
Date2023-07-03 09:12 +0200
Message-ID<u7u2na$3lmer$1@dont-email.me>
In reply to#90822
Christian,

> You should read the answer, not the question.

Can you tell me what the first line of that answer was ?  Was it something 
like

[quote]
The filter function, called before initscr, tells curses to use a single 
line (rather than the whole screen).
[/quote]

?

Yeah, no.  I have been quite clear I can't use cooked input, and it still 
messes with the screen.

Luckily Pavel was a bit more forthcoming than you, and made it clear that 
there was a bit of a trick involved.   Which ofcourse was not mentioned 
there.

But if it actually does grab a screenline (and displays any output and/or 
restores that screenline after exiting the call) while allowing me to grab 
keystrokes (does the callback have a "ignore this keystroke" return value ? 
I have not looked yet) than I again can't use it.

Bottom line : Yes, I ready that answer.   To me it looks that you didn't. 
Or perhaps just ignored the "side effects" of that method, because they do 
not matter to you.

If I'm wrong and that method actually doesn't mess with the screen *at all* 
than you're welcome to point out how thats been done.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]


#90823

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-07-02 15:39 -0700
Message-ID<877crix7ip.fsf@nosuchdomain.example.com>
In reply to#90818
"R.Wieser" <address@is.invalid> writes:
> Keith,
>
>> You could post a single message on this thread saying that
>> you're going to continue the discussion in comp.unix.programmer.
>
> Ah yes, about that : Are you aware that Linux != Unix ?  I might well be 
> told to leave that group for the same reason you are trying to eject me from 
> this one ...

Yes, I'm aware.  At least the first part of your original question was
not specific to Linux.  Recognizing arrow keys on input, for example,
can be done using interfaces defined by POSIX, which is supported by all
Unix-like systems.  The curses interface (which provides similar
functionality in a way that doesn't quite meet your requirements) is
defined by POSIX.

You mentioned the "console", apparently referring to the Linux virtual
console, but in most ways it behaves very similarly to any other modern
terminal emulator.

I'm not the only person who has suggested that comp.unix.programmer
would be a better place for your question.  Apparently you'd rather
stay here and argue with people who are trying to help you.

Detecting modifier keys (shift, control, alt) separately is another
matter.  It's impossible in some contexts.  Detecting them on a
Linux virtual console is probably possible, but I don't know how.
That might be a question for a Linux-specific newsgroup; I don't know
which one, but perhaps something under the comp.os.linux.* hierarchy.
"man console_codes" might be helpful; it does discuss modifier keys.

>> You can still do that.  It would be far less rude than what
>> you're doing now.
>
> Which is ?    That I ignore your "I'm a Windows C++ programmer and could not 
> care less about the Linux C++ programmers that are here" attitude ?

No, you've been posting here repeatedly without asking anything that's
specific to C++.

[...]

>> You skipped the part where Thomas Dickey demonstrated using
>> ncurses without taking over the screen.
>
> Lol.
>
> Third paragraph, first sentence :
>
> "Here's a *non-working* example of what I'm trying to do."
>
> (bolding by me).

Yes, I know.  I wrote that in my question.

> A quick peek at the result could have told you the same :
>
> "
> Press UP, DOWN, Escape, LEFT, RIGHT
> Incorrect input: (-1, -1, -1, -1, -1)
> "
>
> He even mentions the "intimately tied to taking over the entire screen" as a 
> standing problem in his "update" paragraph.

Yes, *I* wrote that as part of the *question*.  I was suggesting
that you read Thomas Dickey's *answer*.  (FYI, he's been maintaining
ncurses since 1996.)

Don't expect any more help from me.

-- 
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 */

[toc] | [prev] | [next] | [standalone]


#90826

From"R.Wieser" <address@is.invalid>
Date2023-07-03 10:12 +0200
Message-ID<u7u2nb$3lmer$2@dont-email.me>
In reply to#90823
Keith,

>> Ah yes, about that : Are you aware that Linux != Unix ?
...
> Yes, I'm aware.

Than why did you try to push me to that newsgroup.  It makes zero sense.

> At least the first part of your original question was
> not specific to Linux.

You mean the part above the "second question" ?    If so, what *didn't* you 
understand about

[quote=me, initial message]
I was wondering if this perhaps is already part of Linux ...
[/quote]

?

Also, thruout the thread there are multiple mentionings of Linux specific 
usage, some of which I acknowledged to having found them myself.   If 
nothing than that should have given you a clue to what OS I was working on.

You complain abut me not reading everything and thus missing stuff ?   I 
suggest you take a long, hard look in the mirror.

> You mentioned the "console", apparently referring to the Linux virtual
> console

I have no idea, as my "/please/ tell me the difference between them" 
requests have never been answered.  Which, by the way, feels to me like 
nobody here actually knows the distinction themselves.

... and you have now introduced yet another phrase to that list, bringing it 
up to ... six?

But looking at the "virtual" part of it, isn't that not something that can 
only be true when you use a GUI ?   In that case I think you might also have 
missed my mentioning (in my second post) of "my "bullseye lite" 
installation".

... Which also should have been a clue-by-four that I was indeed using 
Linux.

> I'm not the only person who has suggested that comp.unix.programmer
> would be a better place for your question.

True.  You're one of exactly two who said that.  And that makes it better 
... how exactly ?    How many people are there in this newsgroup ?

Besides ofcourse that you tried to dump me into a non-Linux newsgroup. :-(

> Apparently you'd rather stay here and argue with people who are
> trying to help you.

The people who wanted to help me already did.   You and james are just 
keeping on claiming I should not be here.  Other than some "because I say 
so" I have not gotten any clarification of that.

> I was suggesting that you read Thomas Dickey's *answer*.

I refer you to my reply to 'Christian', just before my reply to you.

> Don't expect any more help from me.

Like you trying to set me up to fail by suggesting I (re)post in a Unix 
related group ?  Yeah, I surely could do without such shennigans.

But, thank you for your (initial) attempts to come up with something 
workable. Alas, as I've mentioned, something with a "side" effect of 
touching the screen is unusable to me.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]


#90834

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-03 13:28 +0000
Message-ID<u2AoM.9948$fNr5.6767@fx16.iad>
In reply to#90826
"R.Wieser" <address@is.invalid> writes:
>Keith,
>
>>> Ah yes, about that : Are you aware that Linux != Unix ?
>...
>> Yes, I'm aware.
>
>Than why did you try to push me to that newsgroup.  It makes zero sense.

It makes total sense to everyone but you, which is your problem, not ours.

[toc] | [prev] | [next] | [standalone]


#90840

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-03 12:43 -0400
Message-ID<u7uts3$3obki$1@dont-email.me>
In reply to#90826
On 7/3/23 04:12, R.Wieser wrote:
> Keith,
> 
>>> Ah yes, about that : Are you aware that Linux != Unix ?
> ...
>> Yes, I'm aware.
> 
> Than why did you try to push me to that newsgroup.  It makes zero sense.

Because Linux tends to comply with the requirements of the POSIX
standard. As long as what you're talking about doesn't involve any
linux-specific features (I might have missed something, but this issue
doesn't seem to involve any such features), it's at least as good a
place to go as a Linux-specific forum, and possibly better, because the
answer might be portable to other POSIX-conformant platforms.

...
> You mean the part above the "second question" ?    If so, what *didn't* you 
> understand about
> 
> [quote=me, initial message]
> I was wondering if this perhaps is already part of Linux ...
> [/quote]
> 
> ?

Sorry, I made the mistake of assuming that you would be interested in a
POSIX solution that worked on Linux, even if that solution doesn't
involve any features specific to linux.

>> I'm not the only person who has suggested that comp.unix.programmer
>> would be a better place for your question.
> 
> True.  You're one of exactly two who said that.  And that makes it better 
> ... how exactly ?    How many people are there in this newsgroup ?

Because there's lots of Unix experts in that newsgroup, most of whom are
also Linux experts, who might be able to find a Unix solution to your
problem that works under Linux.

...
>> I was suggesting that you read Thomas Dickey's *answer*.
> 
> I refer you to my reply to 'Christian', just before my reply to you.


You mean the answer that said "If you're clever, you can turn off echo,
and (since filter suppresses the screen erasure), pretend that it
updates nothing at all."?

[toc] | [prev] | [next] | [standalone]


#90837

FromMuttley@dastardlyhq.com
Date2023-07-03 15:41 +0000
Message-ID<u7uq6n$3o0ms$1@dont-email.me>
In reply to#90818
On Sun, 2 Jul 2023 11:03:42 +0200
"R.Wieser" <address@is.invalid> wrote:
>Keith,
>
>> You could post a single message on this thread saying that
>> you're going to continue the discussion in comp.unix.programmer.
>
>Ah yes, about that : Are you aware that Linux != Unix ?  I might well be 

The distinction vanished long ago from a programming POV. The vast majority
of unix development these days is done on Linux. I've posted linux specific
questions on that group and no one complained.

[toc] | [prev] | [next] | [standalone]


#90846

From"R.Wieser" <address@is.invalid>
Date2023-07-03 21:32 +0200
Message-ID<u7vcl8$3q06c$1@dont-email.me>
In reply to#90837
Muttly,

> I've posted linux specific questions on that group and no
> one complained.

Thanks for that.

Though mine is not a programing question, but /an availability/ of something 
in Linux.   There, AFAICT, the the distinction matters.

To me it feels like asking a Fort dealer about something thats going to be 
used in an Audi.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]


#90849

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-03 21:06 +0000
Message-ID<u7vd8c$1pu9p$2@news.xmission.com>
In reply to#90846
In article <u7vcl8$3q06c$1@dont-email.me>, R.Wieser <address@is.invalid> wrote:
>Muttly,
>
>> I've posted linux specific questions on that group and no
>> one complained.
>
>Thanks for that.
>
>Though mine is not a programing question, but /an availability/ of something 
>in Linux.   There, AFAICT, the the distinction matters.

I've been following this thread since the beginning - I've read all the
posts, and already commented once or twice.  I've also often wished for an
off-the-shell solution to this problem - the closest does indeed seem to be
ncurses - but that's less than optimal for all the reasons that we've all
seen listed here.

That all said, this is really what I'd call a "software" problem.  I.e.,
if I were laying out a newsgroup hierarchy, the ideal group for this
question would be something like:  comp.linux.software (or maybe comp.unix.software)
(I have no idea if a group of that name already exists).

The idea is that you want to know if software already exists to do what you
want.  Note, BTW, that many of us have in fact already implemented some
homespun version of this (at least, you, me, and one other poster here),
and the thing we all have in common is a feeling of annoyance at having had
to do so.  There really *should* be an off-the-shell solution.

BTW, doing it in full generality is nowhere near as easy or straightforward
as some here have been making it out to be.  I may, in a future post, share
some details of my solution - you'll be amazed at how many special cases
there are.

-- 
The whole aim of practical politics is to keep the populace alarmed (and hence clamorous
to be led to safety) by menacing it with an endless series of hobgoblins, all of them imaginary.

H. L. Mencken

[toc] | [prev] | [next] | [standalone]


#90854

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-04 05:20 -0400
Message-ID<u80o8u$25n8$1@dont-email.me>
In reply to#90846
On 7/3/23 15:32, R.Wieser wrote:
> Muttly,
> 
>> I've posted linux specific questions on that group and no
>> one complained.
> 
> Thanks for that.
> 
> Though mine is not a programing question, but /an availability/ of something 
> in Linux.   There, AFAICT, the the distinction matters.
> 
> To me it feels like asking a Fort dealer about something thats going to be 
> used in an Audi.

Linux generally meets the requirements of the POSIX standard. What do
Audis and Fords have in common that is analogous to that relationship?

[toc] | [prev] | [next] | [standalone]


#90858

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-04 13:56 +0000
Message-ID<dyVoM.17049$N3_4.15605@fx10.iad>
In reply to#90854
James Kuyper <jameskuyper@alumni.caltech.edu> writes:
>On 7/3/23 15:32, R.Wieser wrote:
>> Muttly,
>> 
>>> I've posted linux specific questions on that group and no
>>> one complained.
>> 
>> Thanks for that.
>> 
>> Though mine is not a programing question, but /an availability/ of something 
>> in Linux.   There, AFAICT, the the distinction matters.
>> 
>> To me it feels like asking a Fort dealer about something thats going to be 
>> used in an Audi.
>
>Linux generally meets the requirements of the POSIX standard. What do
>Audis and Fords have in common that is analogous to that relationship?

There are dozens of standards that govern automobiles, starting with the
SAE and/or Metric standards used for fasteners, and up through various
standards that apply to the on-board software, CAN bus (being replaced
by ethernet on newer vehicles) and processors (from RAS
to security).

[toc] | [prev] | [next] | [standalone]


#90871

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-04 16:03 -0400
Message-ID<u81tv0$6hb7$1@dont-email.me>
In reply to#90858
On 7/4/23 09:56, Scott Lurndal wrote:
> James Kuyper <jameskuyper@alumni.caltech.edu> writes:
>> On 7/3/23 15:32, R.Wieser wrote:
...
>>> To me it feels like asking a Fort dealer about something thats going
>>> to be used in an Audi.
>>
>> Linux generally meets the requirements of the POSIX standard. What do
>> Audis and Fords have in common that is analogous to that relationship?
>
> There are dozens of standards that govern automobiles, starting with the
> SAE and/or Metric standards used for fasteners, and up through various
> standards that apply to the on-board software, CAN bus (being replaced
> by ethernet on newer vehicles) and processors (from RAS
> to security).

So, Audis and Fords are probably related to each other by the fact that
they both have internals that obey certain standards.

That isn't quite the relationship between UNIX and Linux. UNIX and Linux
are not two different things that both conform to the same standard.
UNIX is a standard, and most distros of Linux come close to fully
conforming to it. According to one of the other posters on this thread,
there are even distros that fully conform to it.

[toc] | [prev] | [next] | [standalone]


#90872

Fromkalevi@kolttonen.fi (Kalevi Kolttonen)
Date2023-07-04 21:03 +0000
Message-ID<u821et$6tl4$1@dont-email.me>
In reply to#90871
James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
> UNIX is a standard, and most distros of Linux come close to fully
> conforming to it. According to one of the other posters on this thread,
> there are even distros that fully conform to it.

Right. It is clear that my information was outdated. 
The last I checked, no Linux distro had gone through 
the UNIX certification process. But according to:

  https://en.wikipedia.org/wiki/Unix

"Notably, EulerOS and Inspur K-UX are Linux 
distributions certified as UNIX 03 compliant."

I have no idea what "03" means but I am pretty
damn sure it does not stand for "2003".

br,
KK

[toc] | [prev] | [next] | [standalone]


Page 3 of 8 — ← Prev page 1 2 [3] 4 5 6 7 8  Next page →

Back to top | Article view | comp.lang.c++


csiph-web