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


#90912 — Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes))

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-06 16:53 +0000
SubjectTotally insane (Was: Cars (Was: Parsing multi-byte keystrokes))
Message-ID<u86rhp$1tnei$1@news.xmission.com>
In reply to#90907
In article <u86nee$vnt1$1@dont-email.me>,  <Muttley@dastardlyhq.com> for some unknown reason wrote:
...
>If you don't understand unix don't comment on it. From a systems devs POV
>linux and unix are 99% interchangable. Yes the kernels differ but then the
>solaris kernel is a very different to AIX which is different to HP-UX.

This (preceding) paragraph is totally insane and was totally unnecessary.

-- 
The randomly chosen signature file that would have appeared here is more than 4
lines long.  As such, it violates one or more Usenet RFCs.  In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
	http://user.xmission.com/~gazelle/Sigs/Seriously

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


#90921 — Re: Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes))

FromMuttley@dastardlyhq.com
Date2023-07-07 07:15 +0000
SubjectRe: Totally insane (Was: Cars (Was: Parsing multi-byte keystrokes))
Message-ID<u88e1t$18m3k$1@dont-email.me>
In reply to#90912
On Thu, 6 Jul 2023 16:53:13 -0000 (UTC)
gazelle@shell.xmission.com (Kenny McCormack) wrote:
>In article <u86nee$vnt1$1@dont-email.me>,  <Muttley@dastardlyhq.com> for some
>unknown reason wrote:
>....
>>If you don't understand unix don't comment on it. From a systems devs POV
>>linux and unix are 99% interchangable. Yes the kernels differ but then the
>>solaris kernel is a very different to AIX which is different to HP-UX.
>
>This (preceding) paragraph is totally insane and was totally unnecessary.

So far all of your posts fit that criteria.

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


#90801

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-06-30 17:00 -0400
Message-ID<u7nfp3$2kvh5$1@dont-email.me>
In reply to#90793
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.

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


#90803

Fromgazelle@shell.xmission.com (Kenny McCormack)
Date2023-07-01 07:53 +0000
Message-ID<u7om17$1mifg$1@news.xmission.com>
In reply to#90801
In article <u7nfp3$2kvh5$1@dont-email.me>,
James Kuyper  <jameskuyper@alumni.caltech.edu> 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.

Those people are mostly idiots and can (and should) be ignored.  So,
really, no worries on that front.

-- 
A Catholic woman tells her husband to buy Viagra.

A Jewish woman tells her husband to buy Pfizer.

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


#90805

From"R.Wieser" <address@is.invalid>
Date2023-07-01 10:30 +0200
Message-ID<u7op6k$2shgi$3@dont-email.me>
In reply to#90801
James,

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

If I would know everything (including the knowledge of a more apropriate 
newsgroup ) than I would not have needed to post a question to begin with. 
Ever thought about that ?

> It's significantly less than 100% here

You don't say.

> several of the people who post here dismiss any Linux-specific comment in
> the belief that Linux is unimportant compared to Windows.

And those are not the ones who would have the Linux knowledge to answer my 
current question, so thats fine by me.

But thank you for the warning.

And for the record, if I would have had that other newsgroup in my shortlist 
I would have posted there.

Regards,
Rudy Wieser

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


#90816

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-02 04:04 -0400
Message-ID<u7rb24$38rc1$1@dont-email.me>
In reply to#90805
On 7/1/23 04:30, R.Wieser wrote:
> James,
> 
>> 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?
> 
> If I would know everything
...
> than I would not have needed to post a question to begin with.

Of course.

[Rearranging slightly]
>  (including the knowledge of a more appropriate
> newsgroup )

However, I did expect you to know how to search for an appropriate
newsgroup.

...
> And for the record, if I would have had that other newsgroup in my shortlist 
> I would have posted there.

Your message headers indicate that your newsreader is Microsoft Outlook
Express. I use the Outlook app on my smartphone, which has no obvious
way to access usenet newsgroups. I don't know how Outlook works on it's
native platform, Windows, so I'm afraid I can't help you with that.

However, most newsreaders have some way of searching for appropriate
newsgroups on a specified news server. I use Mozilla Thunderbird to
access the Eternal September news server. When I select that server,
right click and select "Subscribe" from the pop-up menu, and type
"Linux" in the search box, it lists several hundred newsgroups, many of
which would be a more appropriate place to post this question than this
newsgroup. I also use Google Groups, which has a similar capability. I
would expect the same would be true of Outlook.

You'll get better answers from people with more Linux-specific knowledge
in those newsgroups than here.

And of course, usenet newsgroups are far from being the only forums for
discussing Linux. See <https://www.linux.org/forums/>, for instance.

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


#90819

From"R.Wieser" <address@is.invalid>
Date2023-07-02 11:27 +0200
Message-ID<u7rfu8$39da1$1@dont-email.me>
In reply to#90816
James,

> However, I did expect you to know how to search for an appropriate
> newsgroup.
...
> it lists several hundred newsgroups,

Yeah, when I did ask my newsreader I got such a long list too.

> many of which would be a more appropriate place

And you know that one of those others would be more apropriate .... how ? 
Just by looking at the name ?   I did, and I by it posted here.

IOW, I (and you too) have to make a choice on very limited information.  And 
when I than do I get people like keith and you telling me I did it wrong 
*and wave me off* (1) to find another - which I would need to choose on the 
same, limited info I used for this one.

(1) As in : I could not care where you go as long as its not here.  Which is 
a few notches below being helpfull and causes me to ignore it.  Sorry (not 
sorry).

And I'll be damned if I would just subscribe to all of them, follow them for 
a few weeks to figure out what they are all about, and than pick one (with 
possibly still getting a "not here" response).

Besides, keith isn't all that good in picking a "more apropriate" newsgroup 
either, and you are not even trying ...

> You'll get better answers from people with more Linux-specific knowledge
> in those newsgroups than here.

:-) The Linux people here will /really/ like you for implicitily calling 
them non-knowledgable.

Regards,
Rudy Wieser

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


#90820

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-02 14:51 -0400
Message-ID<u7sh00$3cj3a$1@dont-email.me>
In reply to#90819
On 7/2/23 05:27, R.Wieser wrote:
> James,
> 
>> However, I did expect you to know how to search for an appropriate
>> newsgroup.
> ...
>> it lists several hundred newsgroups,
> 
> Yeah, when I did ask my newsreader I got such a long list too.
> 
>> many of which would be a more appropriate place
> 
> And you know that one of those others would be more apropriate .... how ?

Primarily because I know that this is outside the scope of this newsgroup.

> Just by looking at the name ?   I did, and I by it posted here.

You came here with a question that was primarily about Linux
functionality, because you thought that "C++" in the newsgroup name was
a stronger indication of appropriateness than "Linux"?

> IOW, I (and you too) have to make a choice on very limited information.

No, we don't. One of the best ways to find out which newsgroup is most
appropriate for a given topic is to do a search for messages containing
relevant keywords in Google Groups. Not all such messages will be about
the topic you're actually interested in, but you should be able to scan
the first several pages of search results to identify a newsgroup that's
appropriate.
On the other hand, if "C++" strikes you as a more relevant keyword than
"linux", your judgement of such matters is not to be trusted, so perhaps
asking for advice would be a better idea.

> Besides, keith isn't all that good in picking a "more apropriate" newsgroup 
> either, and you are not even trying ...

It's your search, I was just explaining how to conduct it. I've used and
programmed exclusively on Linux, both at work and at home, for nearly
three decades, but I've never had any reason to worry about the issues
you're worrying about, so I'm not sure where to direct you.
More importantly, as a general rule, when I am looking for OS-specific
solutions, I'm more interested in a POSIX generic solution rather than a
Linux-specific one. If such a solution would be acceptable to you, I'd
recommend going to comp.unix.programmer

>> You'll get better answers from people with more Linux-specific knowledge
>> in those newsgroups than here.
> 
> :-) The Linux people here will /really/ like you for implicitily calling 
> them non-knowledgable.

Huh?
I suggested nothing of the kind. Only that there are far fewer Linux
experts here than you could expect to find in an active Linux oriented
group. The average level of Linux expertise in this group is lower that
of the linux groups. The minimum level of linux expertise in this
newsgroup is 0, but should be non-zero in those newsgreups.

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


#90821

From"R.Wieser" <address@is.invalid>
Date2023-07-02 22:49 +0200
Message-ID<u7snst$3dlou$1@dont-email.me>
In reply to#90820
James,

>> And you know that one of those others would be more apropriate .... how ?
>
> Primarily because I know that this is outside the scope of this newsgroup.

Wrong answer.   Perhaps this is, outof all the newsgroups, the most 
apropriate.  But you would not know and you do not care.  As long as I 
believe your claim and leave.

> You came here with a question that was primarily about Linux 
> functionality,
> because you thought that "C++" in the newsgroup name was a stronger
> indication of appropriateness than "Linux"?

I already answered that. At least twice.   You going in circles doesn't work 
for me.  Sorry.

> One of the best ways to find out which newsgroup is most appropriate for
> a given topic is to do a search for messages containing relevant keywords
> in Google Groups.

Nice.  So you are going to do that for me ?  'Cause I have zero wish to sign 
up for "google groups".  Or any other like it.   I already have to see them 
necro-bumping multiple years  old posts or adverts for viagra, hacking 
services and crap like that.

besides, I already did my searching.  Quite a bit of it actually. If my 
answer would have been in there I would have already found it, and not have 
posted here.

> On the other hand, if "C++" strikes you as a more relevant keyword than
> "linux", your judgement of such matters is not to be trusted, so perhaps
> asking for advice would be a better idea.

Good, than we are now on the same page.  I seek  advice, and you think me 
asking for advice is a good idea.    So ?    Or are you no Linux person ? 
Actualy, I don't think I have to ask that.

>> Besides, keith isn't all that good in picking a "more apropriate" 
>> newsgroup
>> either, and you are not even trying ...
>
> It's your search, I was just explaining how to conduct it.

As I already explained to you, no you didn't.

> If such a solution would be acceptable to you, I'd recommend going to
> comp.unix.programmer

Another nitwit who doesn't seem to understand that Unix != Linux.

As I said it to Keith, I might there well be asked to leave for the same 
reason you use to try to eject me here.  And where you don't, they would 
actualy have a point.

>> :-) The Linux people here will /really/ like you for implicitily calling
>> them non-knowledgable.
>
> Huh?
> I suggested nothing of the kind.

You're not really smart, are you ?   I ask a Linux and programming related 
question as I assume that there would also be linux people here, some of 
which might well know what the answer to my question is.

But you're saying that my question is not apropriate here.  I can only 
assume that you do not think the Linux people could know the answer.

Actually, someone has already proven you wrong in that regard.

> The minimum level of linux expertise in this newsgroup is 0

You like to throw some great-sounding but actually meaning absolutily 
nothing blurbs like that around, do you ?    First the "significantly less 
than a 100%" - from a 100% you can only go down, and "significantly" can 
mean about /anything/ in that 100% range.  Is "5% less" significant ?  Is 
"50% less" significant ?  Well, that depends on what that "significant" is 
applied.

Yes, ofcourse the mininmum level is Zero.  Perhaps one of the Windows people 
has not ever heard about that OS (hard to imagine, but hey, its possible).

In the same vein I can, with absolute certainty, tell you that the maximum 
level of linux expertise here is 100%.

Next you will probably try to tell me that water is wet.   Or is that a bit 
of a spoiler ?

Regards,
Rudy Wieser

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


#90824

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-02 18:56 -0400
Message-ID<u7svbh$3eg6v$1@dont-email.me>
In reply to#90821
On 7/2/23 16:49, R.Wieser wrote:
...
> Nice.  So you are going to do that for me ?  'Cause I have zero wish to sign 
> up for "google groups".  Or any other like it.   I already have to see them 
> necro-bumping multiple years  old posts or adverts for viagra, hacking 
> services and crap like that.

"comp.os.linux.answers" appears to be a fairly active linux oriented
group, which frequently contains messages matching my search terms
"linux console raw keyboard terminal". I would still suggest that
<https://www.linux.org/forums/> might be more useful than any Usenet
Newsgroup.

Interestingly enough, when I also included "multi-byte", the messages
retrieved were posted almost exclusively in various newsgroups that had
"freebsd" rather than "linux" in their names. The reason might be
obvious to someone who knows more than I do about the relationship
between freebsd and linux.


> Good, than we are now on the same page.  I seek  advice, and you think me 
> asking for advice is a good idea.    So ?    Or are you no Linux person ?

As I indicated, I have been using almost exclusively Linux for 30 years
now. I also don't know how to solve your problem to your satisfaction.
If there is in fact a solution, you'll need someone with more Linux
expertise than me.

[Restoring snipped context]
>> I'm more interested in a POSIX generic solution rather than a Linux-specific one. 
[End of restored context]
>> If such a solution would be acceptable to you, I'd recommend going to
>> comp.unix.programmer
> 
> Another nitwit who doesn't seem to understand that Unix != Linux.

I very clearly distinguished Unix and Linux in the part of my message
that you chose to snip - how could you derive from that the conclusion
that I was confusing them?

>>> :-) The Linux people here will /really/ like you for implicitily calling
>>> them non-knowledgable.
>>
>> Huh?
>> I suggested nothing of the kind.
> 
> You're not really smart, are you ?   I ask a Linux and programming related 
> question as I assume that there would also be linux people here, some of 
> which might well know what the answer to my question is.
> 
> But you're saying that my question is not apropriate here.  I can only 
> assume that you do not think the Linux people could know the answer.

No, I think you'll get answers of varying quality, depending upon how
subtle the issue is. The biggest danger is that if a linux issue is too
subtle, an answer given by a Linux user in a C++ group might be wrong in
a way that's too subtle for any of the other Linux users here to catch.
That's less likely to be the case in a newsgroup devoted to Linux.

> Actually, someone has already proven you wrong in that regard.

Oh - who? The only response you've received that you haven't denigrated
yet was the one suggesting that you use readline(), and you haven't
posted any follow-up indicating that it actually met your needs. If
that's the solution to your problem, then your description of your
problem made it seem far more complicated than it actually was.

...
> Yes, ofcourse the mininmum level is Zero.  Perhaps one of the Windows people 
> has not ever heard about that OS (hard to imagine, but hey, its possible).

It's not just one such person - there's many people here who have made
it quite clear that they don't know much of anything about Linux, and
couldn't care less.

> In the same vein I can, with absolute certainty, tell you that the maximum 
> level of linux expertise here is 100%.

That seems incredibly unlikely to me. I've seen the levels of Linux
expertise displayed both here and in comp.UNIX.programmer - those levels
are much higher in c.u.p., which is entirely reasonable. If a lowly UNIX
group displays more linux expertise than a c.l.c++, how much higher
should the Linux expertise be in a group that actually has "linux" in
the group name?

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


#90827

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

> "comp.os.linux.answers" appears to be a fairly active linux oriented
> group

Thank you for that suggestion.  Alas, ethernal september (my newsgroup host) 
doesn't seem to carry it. :-\

> I would still suggest that <https://www.linux.org/forums/>

Thank you again for that suggestion.  Alas, I'm quite reluctant to sign up 
to anything just to get a single answer.

Also, when I try to have a peek at what they are offering I 1) get an 
"insecure connection".  When I than bypass the certificate problem I 2) end 
up on a cloudflare server which returns a "403 Forbidden".    It also 
doesn't help that 3) it demands JS to be enabled, which I keep disabled.

> As I indicated, I have been using almost exclusively Linux for 30 years
> now. I also don't know how to solve your problem to your satisfaction.

*Thank you* for saying that.    It means that I can stop trying to search 
for it (and just use whatever I already came up with myself).

>> Actually, someone has already proven you wrong in that regard.
>
> Oh - who? The only response you've received that you haven't denigrated
> yet was the one suggesting that you use readline(),

I rejected it the first time, as I have no use for cooked input.  It was 
Pavel who clarified it and showed that I could possibly use its callback to 
get what I wanted.

... though a more recent post seems to indicate that that call still grabs 
part of the the screen, which again/still makes it (way) less usable to me.

As for "denigrated" ?   Think (read) again. I'm not known for just saying 
"no" to something, I tend to describe why there is a mismatch between the 
offered solution and what I am after.    If you can't handle a "thats not 
quite it and {this} is the reason why" than thats your problem, not mine.

> I very clearly distinguished Unix and Linux in the part of my message
> that you chose to snip - how could you derive from that the conclusion
> that I was confusing them?

By trying to push my Linux related question into a Unix related newsgroup. 
Are you daft or something ?  Or just suffering from dementia ?

> No, I think you'll get answers of varying quality,

Which is another "water is wet" kind of thing.  Skipped.

> That's less likely to be the case in a newsgroup devoted to Linux.

I recently asked a RPi platform-specific hardware and Linux OS specific 
question in an RPi specific newsgroup.  For some reason people there where, 
for whatever reason, coming up with all kinds of Non-RPi references.  You 
where saying ?

IOW, that pendulum swings both ways.

But granted, there is a distinct possibility, and I'm open to suggestions. 
Just not bogus ones. :-(

>> In the same vein I can, with absolute certainty, tell you that the 
>> maximum
>> level of linux expertise here is 100%.
>
> That seems incredibly unlikely to me.  I've seen the levels of Linux
> expertise displayed both here and in comp.UNIX.programmer

:-)   Thats the problem with grabbing the correct interpretation of what 
you're reading.  As I tried to explain as reponse to your "less than a 100%" 
and "minimum is 0" blurbs.

Knowledge-wise you /cannot/ go under zero, just as your "significantly less 
than 100%" /cannot/ be anything than being less than that 100% (besides what 
"significantly" might actually be).

IOW, just like your "minimum is 0" blurb, the maximum is 100%.  And water is 
wet.  But while the minimum might actually be reached by just having a 
single nincompoop in the group, I grant you that the opposite will be much 
harder to reach - even for just a single person.

Regards,
Rudy Wieser.

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


#90835

Fromscott@slp53.sl.home (Scott Lurndal)
Date2023-07-03 13:34 +0000
Message-ID<j7AoM.9949$fNr5.8882@fx16.iad>
In reply to#90827
"R.Wieser" <address@is.invalid> writes:
>James,
>
>> "comp.os.linux.answers" appears to be a fairly active linux oriented
>> group
>
>Thank you for that suggestion.  Alas, ethernal september (my newsgroup host) 
>doesn't seem to carry it. :-\


Ah, so sad.  You must be aware that Google Groups does provide
an interface that would allow you to participate in that usenet
newsgroup.

It's sad that you don't seem to be able to find the information
yourself, which prior to the internet, was the standard way to learn
something.  Go to the library and read a book.  Go to the community
college and take a class.   Read publically shared code written by others
to get ideas.

But continuing your current pointless arguments with the long-time denizens
of this C++ language group expecting them to write your program for you
is the definition of insanity.

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


#90838

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-03 12:20 -0400
Message-ID<u7usfm$3nv7t$1@dont-email.me>
In reply to#90827
On 7/3/23 04:59, R.Wieser wrote:
> James,
> 
>> "comp.os.linux.answers" appears to be a fairly active linux oriented
>> group
> 
> Thank you for that suggestion.  Alas, ethernal september (my newsgroup host) 
> doesn't seem to carry it. :-\
> 

I should have checked that before posting, but it supports many other
members of the comp.os.linux hierarchy. If nothing else,
comp.os.linux.misc should, by definition, cover it.

..
>> I very clearly distinguished Unix and Linux in the part of my message
>> that you chose to snip - how could you derive from that the conclusion
>> that I was confusing them?
> 
> By trying to push my Linux related question into a Unix related newsgroup. 
> Are you daft or something ?  Or just suffering from dementia ?

What is Linux-specific about your question - other than the fact that
you have specified that you want a linux solution? How would a Unix
solution that was, therefore, also a linux soluction, be either
impossible or not useful to you?

> 
>> No, I think you'll get answers of varying quality,
> 
> Which is another "water is wet" kind of thing.  Skipped.
> 
>> That's less likely to be the case in a newsgroup devoted to Linux.
> 
> I recently asked a RPi platform-specific hardware and Linux OS specific 
> question in an RPi specific newsgroup.  For some reason people there where, 
> for whatever reason, coming up with all kinds of Non-RPi references.  You 
> where saying ?

I said "less likely" - I didn't say "impossible".

>>> In the same vein I can, with absolute certainty, tell you that the 
>>> maximum
>>> level of linux expertise here is 100%.
>>
>> That seems incredibly unlikely to me.  I've seen the levels of Linux
>> expertise displayed both here and in comp.UNIX.programmer
> 
> :-)   Thats the problem with grabbing the correct interpretation of what 
> you're reading.  As I tried to explain as reponse to your "less than a 100%" 
> and "minimum is 0" blurbs.
> 
> Knowledge-wise you /cannot/ go under zero, just as your "significantly less 
> than 100%" /cannot/ be anything than being less than that 100% (besides what 
> "significantly" might actually be).

I have no idea why you think those comments are relevant to my
statements. Nothing I said was so vacuous as to be equivalent to
pointing out that those are the lower and upper limits.

To make it concrete, if we were to imagine that it was possible to
objectively rate Linux expertise on a simple linear scale from 0 to 100,
then my experience is that a large fraction of those posting to
comp.lang.c++ have a rating less than 1, while those that do have a
higher rating have an average rating around 50. In contrast, very few of
the people posting to comp.unix.programmer have a rating less than 1,
and those that do have a higher rating have an average rating around 80.
I freely acknowledge that you have no obligation to believe me about
that. I certainly don't have any hard numbers, just subjective
assessments. However, if my assessments were correct, why would you want
to post a Linux-related question to comp.lang.c++ in preference to
comp.unix.programmer?

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


#90842

FromRichard Harnden <richard.nospam@gmail.com>
Date2023-07-03 18:02 +0100
Message-ID<u7uuut$3odnu$1@dont-email.me>
In reply to#90838
On 03/07/2023 17:20, James Kuyper wrote:
> On 7/3/23 04:59, R.Wieser wrote:
>> James,
>>


> assessments. However, if my assessments were correct, why would you want
> to post a Linux-related question to comp.lang.c++ in preference to
> comp.unix.programmer?

Normally you (or Keith, or anyone) would write a summary-so-far, x-post 
to c.u.p and set f/ups.

Why not this time?  Because Rudy is rude and/or too stubborn?

He doesn't have a question about c++, he has a question about posix - 
and c.u.p is exactly where he should be asking.

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


#90852

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-07-03 14:40 -0700
Message-ID<87y1jwwu50.fsf@nosuchdomain.example.com>
In reply to#90842
Richard Harnden <richard.nospam@gmail.com> writes:
> On 03/07/2023 17:20, James Kuyper wrote:
>> assessments. However, if my assessments were correct, why would you want
>> to post a Linux-related question to comp.lang.c++ in preference to
>> comp.unix.programmer?
>
> Normally you (or Keith, or anyone) would write a summary-so-far,
> x-post to c.u.p and set f/ups.
>
> Why not this time?  Because Rudy is rude and/or too stubborn?

Yes.

> He doesn't have a question about c++, he has a question about posix -
> and c.u.p is exactly where he should be asking.

I agree, and I've suggested that he should post to c.u.p.  His
unwillingness to do so does not suggest that he would participate in a
new thread started there by someone else.  At worst, it would just
increase the noise level in c.u.p.  And cross-posting to another
newsgroup and setting followups would probably not affect the
"discussion" 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]


#90847

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

>> Thank you for that suggestion.  Alas, ethernal september (my newsgroup
>> host) doesn't seem to carry it. :-\
>
> I should have checked that before posting,

I disagree.  Its not your task to be aware of everyones newsgroup providers 
and different newsgroups those offer.

> but it supports many other members of the comp.os.linux hierarchy.

Ah.  That gives a much shorter list.  Thanks.

> If nothing else, comp.os.linux.misc should, by definition, cover it.

And it seems to be active too. :-)

> What is Linux-specific about your question other than the fact that
> you have specified that you want a linux solution?

Because I'm running Linux, and have no use for a support thats available 
under Unix, but not Linux.

> I have no idea why you think those comments are relevant to my
> statements. Nothing I said was so vacuous as to be equivalent to
> pointing out that those are the lower and upper limits.

Thats the whole thing : you made it sound as if those two numbers where 
somehow of any importance, but in fact all they are the limits of the range. 
You cannot come up with a number above 100% or below the 0.   Therefore 
naming them as you did had zero meaning to me. Yet, you did.

> then my experience is that a large fraction of those posting to
> comp.lang.c++ have a rating less than 1, while those that do have a
> higher rating have an average rating around 50.

Wow.  I'm going to assume you think that you are one of the 50 percenters, 
here and as such you cannot really stand this newsgroup - because of all the 
nitwits ... ehhh ... 1 percenters in it.

> In contrast, very few of the people posting to comp.unix.programmer have
> a rating less than 1, and those that do have a higher rating have an 
> average
> rating around 80.

Sounds good.

> I freely acknowledge that you have no obligation to believe me about
> that.

I think you think you are saying the truth and that its relevant.

I however have my doubts that what you measured (software knowledge) was 
relevent to my question (availablility of something in Linux).

As my teacher said it "Measuring is knowing - if you know what you are 
measuring".

> However, if my assessments were correct, why would you want
> to post a Linux-related question to comp.lang.c++ in preference to
> comp.unix.programmer?

Absolutily.

But as said, even though I do not doubt your assessment, I do doubt its 
releveance.

Regards,
Rudy Wieser


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


#90855

FromJames Kuyper <jameskuyper@alumni.caltech.edu>
Date2023-07-04 05:47 -0400
Message-ID<u80pqv$25n9$1@dont-email.me>
In reply to#90847
On 7/3/23 16:50, R.Wieser wrote:
> James,
> 
>>> Thank you for that suggestion.  Alas, ethernal september (my newsgroup
>>> host) doesn't seem to carry it. :-\
>>
>> I should have checked that before posting,
> 
> I disagree.  Its not your task to be aware of everyones newsgroup providers 
> and different newsgroups those offer.

I normally use eternal-september with Thunderbird. One of the few
advantages of Google Groups over Thunderbird+Eternal September is better
search facilities (though they are far inferior to the ones that Deja
News provided before Google took over their archive). That's why I used
GG to find the group, but it would not have been difficult for me to
check for it's availability on eternal september before recommending it.

>> What is Linux-specific about your question other than the fact that
>> you have specified that you want a linux solution?
> 
> Because I'm running Linux, and have no use for a support thats available 
> under Unix, but not Linux.

Yes, but do you have any particular reason to believe that such lack of
Linux support is likely? Most Unix solutions work under Linux.

> 
>> I have no idea why you think those comments are relevant to my
>> statements. Nothing I said was so vacuous as to be equivalent to
>> pointing out that those are the lower and upper limits.
> 
> Thats the whole thing : you made it sound as if those two numbers where 
> somehow of any importance, but in fact all they are the limits of the range. 
> You cannot come up with a number above 100% or below the 0.   Therefore 
> naming them as you did had zero meaning to me. Yet, you did.

You were the one who mentioned 100%, not me, claiming that it was the
maximum level of Linux expertise in this newsgroup. My own assessment is
that the maximum is closer to 90%. Since I myself am not near the top of
that distribution, I can't be sure, but my experience suggests that
you'll find the 100%ers over in comp.unix.programming, not here.

I mentioned that the minimum level of Linux expertise in this group is
0, not just because that's the mathematical minimum, but also because a
large fraction of the posters have exactly that level of Linux
expertise, something which is true of very few of the people posting to
comp.unis.programmer.

>> then my experience is that a large fraction of those posting to
>> comp.lang.c++ have a rating less than 1, while those that do have a
>> higher rating have an average rating around 50.
> 
> Wow.  I'm going to assume you think that you are one of the 50 percenters, 
> here and as such you cannot really stand this newsgroup - because of all the 
> nitwits ... ehhh ... 1 percenters in it.

I come to this newsgroup to discuss issues about C++; it doesn't bother
me that some people here lack Linux expertise. I go to
comp.unix.programmer to discuss issues about Unix, including issues
about Linux. It doesn't bother me that some of the people there lack C++
experience. That's what happens when you choose the appropriate forum
for discussing a particular topic - expertise relevant to that topic is
maximized, at the expense of expertise in other areas.

>> I freely acknowledge that you have no obligation to believe me about
>> that.
> 
> I think you think you are saying the truth and that its relevant.
> 
> I however have my doubts that what you measured (software knowledge) was

I didn't measure it - I just observed it. And I was very specifically
talking about my observations of their knowledge of Linux software.

> relevent to my question (availablility of something in Linux).

Why would knowledge of Linus software not be relevant to a question
about the availability of a particular kind of Linux software?

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


#90851

FromKeith Thompson <Keith.S.Thompson+u@gmail.com>
Date2023-07-03 14:36 -0700
Message-ID<873524y8xb.fsf@nosuchdomain.example.com>
In reply to#90838
James Kuyper <jameskuyper@alumni.caltech.edu> writes:
> On 7/3/23 04:59, R.Wieser wrote:
>> James,
>> 
>>> "comp.os.linux.answers" appears to be a fairly active linux oriented
>>> group
>> 
>> Thank you for that suggestion.  Alas, ethernal september (my newsgroup host) 
>> doesn't seem to carry it. :-\
>> 
>
> I should have checked that before posting, but it supports many other
> members of the comp.os.linux hierarchy. If nothing else,
> comp.os.linux.misc should, by definition, cover it.

I'm also on Eternal September, and can confirm that it's not carried.
James, I think you're on Eternal September as well.

I took a look on groups.google.com, and it appears that the most recent
post was in 2011, subject "Moderator Vacancy Investigation:
comp.os.linux.answers".  It's possible GG's horrid user interface has
misled me.

How do you see it as "fairly active"?

[...]

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


#90828

FromDavid Brown <david.brown@hesbynett.no>
Date2023-07-03 11:38 +0200
Message-ID<u7u4ua$3lsae$1@dont-email.me>
In reply to#90805
On 01/07/2023 10:30, R.Wieser wrote:
> James,
> 
>> 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?
> 
> If I would know everything (including the knowledge of a more apropriate
> newsgroup ) than I would not have needed to post a question to begin with.
> Ever thought about that ?
> 
>> It's significantly less than 100% here
> 
> You don't say.
> 
>> several of the people who post here dismiss any Linux-specific comment in
>> the belief that Linux is unimportant compared to Windows.
> 
> And those are not the ones who would have the Linux knowledge to answer my
> current question, so thats fine by me.
> 
> But thank you for the warning.
> 
> And for the record, if I would have had that other newsgroup in my shortlist
> I would have posted there.
> 

It's also important to note that /using/ Linux is not the same as 
/programming/ for Linux.  (For example, most of /my/ C++ programming is 
done /on/ Linux, but not /for/ Linux.)  And the great majority of people 
who write code for Linux would have no need for such raw keyboard 
handling.  And if a library for handling all your needs is available, it 
will almost certainly be in C, not C++.

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 you seem to have insulted or annoyed most of them.

If your original post had been asking how to turn a horrible huge C 
switch into something more elegant and maintainable in C++, you'd be in 
the right place here.

I don't know of any newsgroups where you would be able to get the help 
you want.  It would have to be somewhere that covered such terminal 
access that is probably common to all POSIX systems, but the group could 
not mention UNIX, BSD or anything other than Linux because you believe 
them to be completely different.  The members should be happy to help a 
poster despite sarcasm and insults.  They should accept a total 
disregard for conventions and group standards.  The existing members of 
the group should be proud to search the web and group archives for you, 
so that you would not be exposed to any unpleasant adverts or posts. 
No, sorry, I don't know of any such Usenet groups or other forums.


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


#90830

From"R.Wieser" <address@is.invalid>
Date2023-07-03 13:04 +0200
Message-ID<u7ua0g$3mcje$1@dont-email.me>
In reply to#90828
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 ... ?

> And you seem to have insulted or annoyed most of them.

I think they are thankfull that I have not dumped a question in their 
newsgroup that has absolutily zero to do with the OS their newsgroup is for.

> If your original post had been asking how to turn a horrible huge C switch 
> into something more elegant and maintainable in C++, you'd be in the right 
> place here.

Too bad that that wasn't a question I wanted to ask.

> I don't know of any newsgroups where you would be able to get the help you 
> want.

Shucks.  And the question was such an easy one !  Does something like it 
already exist in Linux, and if so where can I find it.  I shrudder about 
what the result would be for a really complex question ...

> It would have to be somewhere that covered such terminal access

You misread.  I did not ask about terminal access. I asked if the parsing of 
such input would possibly already exist.  Nothing more.

> The members should be happy to help a poster despite sarcasm and insults.

That some people here have not been able to comprehend my, rather simple, 
question is one thing.

However, if they than start to demand that I take their resulting crap as 
the answer and refuse to accept my explanation to why it isn't and than keep 
pressing it nonetheless than they deserve my ire.

Try thinking of our situation in reverse : how long would it take for you to 
be fed up with such behaviour ?    My guess is, not much longer than it took 
me.

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

Regards,
Rudy Wieser

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


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

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


csiph-web