Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.unix.programmer > #17215
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Subject | Re: a battery monitor |
| Newsgroups | comp.unix.programmer, comp.windows.x, comp.lang.c |
| References | <87v78oop87.fsf@safunu.org> <117a5eg$35q9q$4@dont-email.me> <117b7jj$3ep01$2@dont-email.me> <117c59h$t5au$1@dont-email.me> <117dqml$d526$1@dont-email.me> |
| Message-ID | <FBAmS.1261$XsT2.867@fx01.iad> (permalink) |
| Organization | UsenetServer - www.usenetserver.com |
| Date | 2026-09-04 14:29 +0000 |
Cross-posted to 3 groups.
David Brown <david.brown@hesbynett.no> writes: >On 03/09/2026 17:55, boltar@caprica.universe wrote: >> On Thu, 3 Sep 2026 09:28:51 +0200 >> David Brown <david.brown@hesbynett.no> gabbled: >>> On 02/09/2026 23:45, Lawrence D’Oliveiro wrote: >>>> Instead of writing all that C code, why not using a preexisting >>>> GUI utility that can display simple widgets like progress bars, >>>> under the control of a shell script? >>>> >>> >>> The OP wrote a cross-post that was devoid of any C relevant content or >>> question for comp.lang.c. But he helpfully set follow-ups to a group >>> that presumably /is/ relevant - comp.windows.x. We already suffer >>> from far too many rambling off-topic threads, and suffer even more >>> from some of the obnoxious trolls that have followed. (To be clear, I >>> am /not/ counting the OP here!) If you want to give the OP advice on >>> writing gui programs for X, that's great - but please do so in a group >>> that is appropriate, and which the OP clearly thought was appropriate. >>> >>> (For those in the other groups listed who might be wondering - >>> comp.lang.c is about the C /language/ - the language and the >>> standards. Just because a program happens to be written in C, does not >>> mean it is relevant or topical in the group, any more than a random >>> post written in the English language is topical for >>> linguistics.languages.english. There are millions of lines of C code >>> written every day, and they cannot all be topical in a single group. >>> But if anyone wants to discuss details of the language itself, >>> comp.lang.c is the place to be.) >> >> Right, because usenet these days is overflowing with posts and wouldn't >> cope >> with many more. > >Many of us would rather have just a few interesting threads, than a few >interesting threads hidden amongst piles of rubbish. So drop all the groups other than comp.lang.c whenyou reply and you'll avoid continuing the thread.
Back to comp.unix.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
a battery monitor Anton Antimo <anton@safunu.org> - 2026-09-01 14:28 -0300
Re: a battery monitor Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-02 21:45 +0000
Re: a battery monitor Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-03 12:34 +0800
Re: a battery monitor Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-03 21:24 +0000
Re: a battery monitor Eli the Bearded <*@eli.users.panix.com> - 2026-09-04 02:51 +0000
Re: a battery monitor David Brown <david.brown@hesbynett.no> - 2026-09-03 09:28 +0200
Re: a battery monitor boltar@caprica.universe - 2026-09-03 15:55 +0000
Re: a battery monitor David Brown <david.brown@hesbynett.no> - 2026-09-04 09:07 +0200
Re: a battery monitor Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-04 15:14 +0800
Re: a battery monitor Lane W <cactus_DAC@yahoo.com> - 2026-09-04 05:32 -0600
Re: a battery monitor scott@slp53.sl.home (Scott Lurndal) - 2026-09-04 14:29 +0000
Re: a battery monitor Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-09-04 23:17 +0800
Re: a battery monitor gazelle@shell.xmission.com (Kenny McCormack) - 2026-09-04 12:05 +0000
csiph-web