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 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8  Next page →


#90833

FromDavid Brown <david.brown@hesbynett.no>
Date2023-07-03 15:11 +0200
Message-ID<u7uhef$3n1sa$3@dont-email.me>
In reply to#90830
On 03/07/2023 13:04, R.Wieser wrote:

> Than again, most people would than just stop responding.  I've not quite
> gotten the hang of that yet. :-\
> 

Try harder.  We are all cheering for you.

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


#90843

FromChristian Gollwitzer <auriocus@gmx.de>
Date2023-07-03 20:35 +0200
Message-ID<u7v4de$3ov02$1@dont-email.me>
In reply to#90830
Am 03.07.23 um 13:04 schrieb R.Wieser:
> David,
> 
>> All in all, your only real hope in posting here would be from one of the
>> old regulars who have been coding for *nix systems since the beginning of
>> time.
> 
> And the reason you think that a library written for Unix (or a very old
> version of Linux) will be usable under a nowerdays version of Linux is ... ?

At this point, I believe you must be trolling.

	Christian

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


#90845

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-03 19:16 +0000
Message-ID<u7v6pl$1ps77$1@news.xmission.com>
In reply to#90843
In article <u7v4de$3ov02$1@dont-email.me>,
Christian Gollwitzer  <auriocus@gmx.de> wrote:
>Am 03.07.23 um 13:04 schrieb R.Wieser:
>> David,
>> 
>>> All in all, your only real hope in posting here would be from one of the
>>> old regulars who have been coding for *nix systems since the beginning of
>>> time.
>> 
>> And the reason you think that a library written for Unix (or a very old
>> version of Linux) will be usable under a nowerdays version of Linux is ... ?
>
>At this point, I believe you must be trolling.

Not so much trolling, per se, but on a quixotic hope that people (the kind
of people who inhabit CLC and CLC++) will change, evolve and grow.

It won't happen, but one can always hope.

-- 
People who want to share their religious views with you
almost never want you to share yours with them. -- Dave Barry

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


#90848

From"R.Wieser" <address@is.invalid>
Date2023-07-03 22:55 +0200
Message-ID<u7vcl9$3q06c$3@dont-email.me>
In reply to#90843
Christian,

> At this point, I believe you must be trolling.

As I must believe that (some of) you guys are doing, as not understanding a 
simple
question for so long takes a lot of effort.

Regards,
Rudy Wieser


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


#90807

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2023-07-01 03:03 -0700
Message-ID<4f5b2980-a7ba-44e3-9c9e-a8abe6c67a43n@googlegroups.com>
In reply to#90801
On Friday, 30 June 2023 at 22:00:37 UTC+1, James Kuyper wrote:
> On 6/30/23 12:12, R.Wieser wrote: 
> > Ben, 
> > 
> >> 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.
> Why would you go to a forum where "a good percentage of users would be 
> using Linux", rather than a forum devoted to Linux, where that 
> percentage could reasonably be assumed to be 100? It's significantly 
> less than 100% here - several of the people who post here dismiss any 
> Linux-specific comment in the belief that Linux is unimportant compared 
> to Windows.
>
Actually the usual pattern is that Linux programmers consider themselves to be technically
and even morally superior to those who program for some other proprietary platforms.
And so Linux-specific discussions get a free pass, unlike those on other operating
systems.

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


#90808

FromMuttley@dastardlyhq.com
Date2023-07-01 10:30 +0000
Message-ID<u7ov78$2t7gk$1@dont-email.me>
In reply to#90807
On Sat, 1 Jul 2023 03:03:57 -0700 (PDT)
Malcolm McLean <malcolm.arthur.mclean@gmail.com> wrote:
>On Friday, 30 June 2023 at 22:00:37 UTC+1, James Kuyper wrote:
>> On 6/30/23 12:12, R.Wieser wrote: 
>> > Ben, 
>> > 
>> >> 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.
>> Why would you go to a forum where "a good percentage of users would be 
>> using Linux", rather than a forum devoted to Linux, where that 
>> percentage could reasonably be assumed to be 100? It's significantly 
>> less than 100% here - several of the people who post here dismiss any 
>> Linux-specific comment in the belief that Linux is unimportant compared 
>> to Windows.
>>
>Actually the usual pattern is that Linux programmers consider themselves to be
>technically
>and even morally superior to those who program for some other proprietary
>platforms.

I disagree. We may be snooty about Windows compared to other OS's - not just
linux - but a C++ dev is a C++ dev regardless of platform. Having written C++
on both I am in no wish to hurry back to Windows due to the hoops you often
have to jump through to do basic (for *nix) stuff such as process forking, 
multiplexing sockets and the absurd distinction between console and GUI apps. 
That said Visual Studio is definately superior as an IDE to anything Linux has 
to offer and blows the bug ridden abortion known as Eclipse out of the water.

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


#90811

From"Alf P. Steinbach" <alf.p.steinbach@gmail.com>
Date2023-07-01 22:37 +0200
Message-ID<u7q2r1$314bg$1@dont-email.me>
In reply to#90785
On 2023-06-29 6:37 PM, R.Wieser wrote:
> 
> And by the way: I have quite a problem with the ^Z (26) being send as the
> start of a command sequence as well on its own when the ESC key is pressed
> (IOW, no escaping of the ESC key).  I do not see any way to, in a stream,
> detect if its one or the other.  Its just asking for trouble. :-(

Timing.

- Alf

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


#90817

From"R.Wieser" <address@is.invalid>
Date2023-07-02 09:42 +0200
Message-ID<u7rehv$3996f$1@dont-email.me>
In reply to#90811
Alf,

>> And by the way: I have quite a problem with the ^Z (26) being send as the
>> start of a command sequence as well on its own when the ESC key is 
>> pressed
>> (IOW, no escaping of the ESC key).  I do not see any way to, in a stream,
>> detect if its one or the other.  Its just asking for trouble. :-(
>
> Timing.

Yep, thats what I used.

But now imagine that I'm not using it to parse a raw, but instead a cooked 
(line-based) input.   Bye-bye timing. :-(

Granted, I did not indicate I would be using my/the parser for that (quite 
the opposite actually), but it did already enter my mind.

Regards,
Rudy Wieser

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


#90787

FromPavel <pauldontspamtolk@removeyourself.dontspam.yahoo>
Date2023-06-29 22:21 -0400
Message-ID<x%qnM.8072$W7d4.5898@fx18.iad>
In reply to#90724
R.Wieser wrote:
> Pavel,
> 
>> On Linux (strictly speaking, on a GNU system) specifically, try readline
>> function.
> 
> The problem with that is that I need the keys at the moment they are pressed
> (and released ?), not only after "enter" is pressed.
I got it from your first post :-).

With readline, you *don't have to wait till <enter> is pressed* to get 
the key.

I have posted this example in my response to Keith Thompson on 6/25/23 
10:18 pm, it might just work for your purpose.

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

#include <readline/readline.h>

int
up_callback(int count, int key) {
    printf ("the user just pressed up-arrow\n");
    return 0;
}

int
main(int argc, char *argv[])
{
   rl_bind_keyseq ("\\e[A", up_callback);
   free(readline("press a button > "));

   printf("\n");

   return 0;
}



> 
> Regards,
> Rudy Wieser
> 
> 

HTH
-Pavel

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


#90792

From"R.Wieser" <address@is.invalid>
Date2023-06-30 17:50 +0200
Message-ID<u7muuc$2j6av$1@dont-email.me>
In reply to#90787
Pavel,

> With readline, you *don't have to wait till <enter> is pressed* to get the 
> key.

[snip code]

Thank you very much.  I'm certainly going to check that out.  If that works 
the way it looks it saves me a /lot/ of work.

... though to be honest, I feel like I'm back in dos batch, abusing stuff 
left and right to get things done. :-| :-)

Regards,
Rudy Wieser

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


#90718

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-06-25 23:20 +0000
Message-ID<lZ3mM.83590$8uge.57668@fx14.iad>
In reply to#90713
"R.Wieser" <address@is.invalid> writes:
>Hello all,
>
>I've set the console input to raw so I can see keys coming in when they are 
>pressed.
>
>For that I've been writing a big "switch ... case" to parse the multi-byte 
>keystrokes into "records" that than can be easily worked with or discarded.
>
>As this parsing needs to be done by pretty-much every console-based program 
>which wants to do any kind of interactive stuff I was wondering if this 
>perhaps is already part of Linux ...
>
>If it is (and thats still a big "if"), where can I find it ?

$ man console_ioctl

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


#90720

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-06-25 17:10 -0700
Message-ID<87ilbb13tu.fsf@nosuchdomain.example.com>
In reply to#90718
scott@slp53.sl.home (Scott Lurndal) writes:
> "R.Wieser" <address@is.invalid> writes:
>>I've set the console input to raw so I can see keys coming in when they are 
>>pressed.
>>
>>For that I've been writing a big "switch ... case" to parse the multi-byte 
>>keystrokes into "records" that than can be easily worked with or discarded.
>>
>>As this parsing needs to be done by pretty-much every console-based program 
>>which wants to do any kind of interactive stuff I was wondering if this 
>>perhaps is already part of Linux ...
>>
>>If it is (and thats still a big "if"), where can I find it ?
>
> $ man console_ioctl

I believe that only applies to the Linux system console (the text-only
interface you typically get by typing Ctrl-Alt-N, where N is a small
integer).  I know the OP wrote "console", but I suspect they're looking
for something that works on a terminal emulator.

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


#90727

From"R.Wieser" <address@is.invalid>
Date2023-06-26 09:21 +0200
Message-ID<u7bee2$sht9$5@dont-email.me>
In reply to#90720
Keith,

> I know the OP wrote "console", but I suspect they're looking
> for something that works on a terminal emulator.

Nope, not an emulator.  As said, "bullseye lite" doesn't have a GUI.

As for the difference between a "console" and a "terminal" ?   I must say 
that its not quite clear (read: confusing) to me , as it seems to be used 
interchangably.   If you have a good description about the differences 
between a "console" and a "terminal" than I would like to hear about it.

Simply said, to me a "console" is the text-based interface you get on a 
'puter thats executing the commands.   A "terminal" is the program you use 
to remotely(?) connect to such a console.

Regards,
Rudy Wieser

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


#90729

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-06-26 01:29 -0700
Message-ID<877crq1va9.fsf@nosuchdomain.example.com>
In reply to#90727
"R.Wieser" <address@is.invalid> writes:
> Keith,
>
>> I know the OP wrote "console", but I suspect they're looking
>> for something that works on a terminal emulator.
>
> Nope, not an emulator.  As said, "bullseye lite" doesn't have a GUI.
>
> As for the difference between a "console" and a "terminal" ?   I must say 
> that its not quite clear (read: confusing) to me , as it seems to be used 
> interchangably.   If you have a good description about the differences 
> between a "console" and a "terminal" than I would like to hear about it.
>
> Simply said, to me a "console" is the text-based interface you get on a 
> 'puter thats executing the commands.   A "terminal" is the program you use 
> to remotely(?) connect to such a console.

The term "console", on Unix-like systems, typically refers to the system
console, sometimes accessed via /dev/console, while a "terminal" is a
more general term for a text-based interface, usually accessed via
/dev/tty* or similar.  (A typical user might never see the console.)

The details beyond that are probably off-topic here.

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


#90735

From"R.Wieser" <address@is.invalid>
Date2023-06-26 13:30 +0200
Message-ID<u7buf8$ue5n$1@dont-email.me>
In reply to#90729
Keith,

> The term "console", on Unix-like systems, typically refers to the
> system console, sometimes accessed via /dev/console, while a "terminal"
> is a more general term for a text-based interface, usually accessed via
> /dev/tty* or similar.  (A typical user might never see the console.)

As I said, the difference between them is /at best/ confusing.   That you 
than introduce "system console" without offering any explanation to it does 
not help either. :-|


I found a link which says that all things are terminals, and that a console 
is just a special one (your "system console").

In that case I'm working on/in the system console.

Though I'm going to have a hard time remembering that ALT F1 is a console, 
but that ALT F2...F6 are terminals (I probably, likely won't.  Too little, 
if any, distinction).

And it doesn't help that I have a couple of WYSE WY60 terminals standing 
behind me. :-)

Regards,
Rudy Wieser

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


#90756

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-06-26 12:18 -0700
Message-ID<87o7l2yqvo.fsf@nosuchdomain.example.com>
In reply to#90735
"R.Wieser" <address@is.invalid> writes:
> Keith,
>
>> The term "console", on Unix-like systems, typically refers to the
>> system console, sometimes accessed via /dev/console, while a "terminal"
>> is a more general term for a text-based interface, usually accessed via
>> /dev/tty* or similar.  (A typical user might never see the console.)
>
> As I said, the difference between them is /at best/ confusing.   That you 
> than introduce "system console" without offering any explanation to it does 
> not help either. :-|

Apparently it helped you to find more information.

> I found a link which says that all things are terminals, and that a console 
> is just a special one (your "system console").
>
> In that case I'm working on/in the system console.
>
> Though I'm going to have a hard time remembering that ALT F1 is a console, 
> but that ALT F2...F6 are terminals (I probably, likely won't.  Too little, 
> if any, distinction).

It's fairly common to use the word "console" (perhaps incorrectly) to
refer to terminals in general.

On Linux-based systems, and probably others, all the Alt-FN screens are
*virtual consoles*.  They're supported by the OS more or less directly,
and they don't depend on any GUI system like X11.  Terminal emulators
typically run as windows under X11 (or Wayland, or whatever).

And since this is all specific to Unix-like systems, and perhaps more
specifically to Linux-based systems, you might get better information in
a Unix-specific newsgroup, perhaps comp.unix.programmer.  (This is
comp.lang.c++, and I don't think I've seen any C++ code in this thread,
and the libraries we've been discussing are C, not C++.)

[...]

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


#90761

From"R.Wieser" <address@is.invalid>
Date2023-06-26 22:37 +0200
Message-ID<u7ctib$12pk1$2@dont-email.me>
In reply to#90756
Keith,

>> As I said, the difference between them is /at best/ confusing.   That you
>> than introduce "system console" without offering any explanation to it 
>> does
>> not help either. :-|
>
> Apparently it helped you to find more information.

No, it didn't.  I could not care less about what, on my machine, the 
difference is between a "system console" and a "console".  But I *had* to 
search for it, because it *could* have been of importance in regard to the 
distinction between a "console" and a "terminal".  It wasn't.  IOW, I wasted 
my time.

> It's fairly common to use the word "console" (perhaps incorrectly)
> to refer to terminals in general.

Thats what I said.  They are pretty-much used interchangably.

Currently I still do not know with what I should refer to the 
console/terminal/tty/whatever on which the boot-process outputs its progress 
and I than use to program in.  Or with what I should refer to the ones under 
ALT F2...F6.

> Terminal emulators typically run as windows under X11 (or Wayland,
> or whatever).

Any reason for the "emulator" postfix ?   Other than by habit I mean ?  And 
yes, I recognise that a console in a window puts character based content in 
a pixel-based environment.

To be honest, I took the "terminal emulator" as being a /program/ which runs 
on another computer, translating whatever it gets into screen output, and 
translates keyboard input to whatever the other side needs (VT100 codes or 
alike).

> And since this is all specific to Unix-like systems, and perhaps more
> specifically to Linux-based systems, you might get better information
> in a Unix-specific newsgroup, perhaps comp.unix.programmer.

I was assuming that there would be linux programmers here too.

But a good one, thanks.

Regards,
Rudy Wieser

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


#90765

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-06-26 14:32 -0700
Message-ID<87bkh1zz7t.fsf@nosuchdomain.example.com>
In reply to#90761
"R.Wieser" <address@is.invalid> writes:
> Keith,
>
>>> As I said, the difference between them is /at best/ confusing.   That you
>>> than introduce "system console" without offering any explanation to it 
>>> does
>>> not help either. :-|
>>
>> Apparently it helped you to find more information.
>
> No, it didn't.  I could not care less about what, on my machine, the 
> difference is between a "system console" and a "console".  But I *had* to 
> search for it, because it *could* have been of importance in regard to the 
> distinction between a "console" and a "terminal".  It wasn't.  IOW, I wasted 
> my time.

I do not accept responsibility for that.

>> It's fairly common to use the word "console" (perhaps incorrectly)
>> to refer to terminals in general.
>
> Thats what I said.  They are pretty-much used interchangably.

That's not what I said.  The term "console", when used correctly for
Linux-based systems and probably some others, refers to the virtual
consoles typically accessed via Ctrl-Alt-FN or Alt-FN -- *not* to
terminal emulators like xterm.  Some people are sloppy about the usage
(and it often doesn't matter, since they really are quite similar in
most ways.)

(There's also an "xconsole" command that runs under X11 and displays
messages sent to /dev/console.  The fact that these things that were
once handled in hardware are now almost entirely handled in software
does create some confusion.)

> Currently I still do not know with what I should refer to the 
> console/terminal/tty/whatever on which the boot-process outputs its progress 
> and I than use to program in.  Or with what I should refer to the ones under 
> ALT F2...F6.

They're called virtual consoles.

>> Terminal emulators typically run as windows under X11 (or Wayland,
>> or whatever).
>
> Any reason for the "emulator" postfix ?   Other than by habit I mean ?  And 
> yes, I recognise that a console in a window puts character based content in 
> a pixel-based environment.

Yes.  A literal *terminal* is a hardware device that includes a monitor,
a keyboard, and some kind of connector.  The VT100 is an example.  A
terminal emulator is a software program designed to emulate a terminal.
Terminal emulators are far more common these days than physical
terminals.

> To be honest, I took the "terminal emulator" as being a /program/ which runs 
> on another computer, translating whatever it gets into screen output, and 
> translates keyboard input to whatever the other side needs (VT100 codes or 
> alike).

Right -- except that it doesn't have to run on another computer.

[...]

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


#90769

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-06-26 22:41 +0000
Message-ID<FuomM.8435$JLp4.176@fx46.iad>
In reply to#90761
"R.Wieser" <address@is.invalid> writes:
>Keith,
>
>>> As I said, the difference between them is /at best/ confusing.   That you
>>> than introduce "system console" without offering any explanation to it 
>>> does
>>> not help either. :-|
>>
>> Apparently it helped you to find more information.
>
>No, it didn't.  I could not care less about what, on my machine, the 
>difference is between a "system console" and a "console".  But I *had* to 
>search for it, because it *could* have been of importance in regard to the 
>distinction between a "console" and a "terminal".  It wasn't.  IOW, I wasted 
>my time.
>
>> It's fairly common to use the word "console" (perhaps incorrectly)
>> to refer to terminals in general.
>
>Thats what I said.  They are pretty-much used interchangably.
>
>Currently I still do not know with what I should refer to the 
>console/terminal/tty/whatever on which the boot-process outputs its progress 
>and I than use to program in.  Or with what I should refer to the ones under 
>ALT F2...F6.

The unix 'tty' command will tell you the name of
the node in /dev that corresponds to your controlling
terminal.    That name might be /dev/console for the
device that owns the host keyboard/mouse/graphic card;
normally known as the system console.

The name might instead be /dev/ttys0, or /dev/usbtty0, or
/dev/serial/0 for a serial attached device, or may be
/dev/pts/17 for a pseudo-terminal pair (e.g. used by
xterm, gnome terminal and other gui and non-gui
terminal emulators.

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


#90779

From"R.Wieser" <address@is.invalid>
Date2023-06-29 13:58 +0200
Message-ID<u7js2f$25ate$2@dont-email.me>
In reply to#90769
Scott,

>>Currently I still do not know with what I should refer to the
>>console/terminal/tty/whatever on which the boot-process outputs its 
>>progress
>>and I than use to program in.  Or with what I should refer to the ones 
>>under
>>ALT F2...F6.
>
> The unix 'tty' command will tell [snip]

Alas, I thought that my above question (in the above quote) was clear 
enough.  But no.

I'll try again, but now dotting some "i"s.


1) The screen the boot process is outputting its progress into is called :

a) a console
b) a system console
c) a terminal
d) a virtual terminal
e) a tty
f) something else altogether.

Explain why.

2)The screen that becomes visible when the ALT F2...F6 keys is pressed is 
called :

a) a console
b) a system console
c) a terminal
d) a virtual terminal
e) a tty
f) something else altogether.

Explain why.

Bonus question :

For any of the choices in the above that have not already been used explain 
when those are used and why.

Regards,
Rudy Wieser

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


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

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


csiph-web