Liste des Groupes | Revenir à col advocacy |
On 4/17/2024 6:36 PM, vallor wrote:On Wed, 17 Apr 2024 16:08:47 -0400, DFS <nospam@dfs.com> wrote in
Note: I do know how to write C to scan directories and list files and
check file types and open and read the contents, etc.
>
<FPDeI.3446$IC5.734@fx24.iad>
<KSGdH.282124$5_4.76405@fx40.iad>
>
Feeb does not.
I looked at those, and had to do a double-take with the second one.
Calling "file" is "cheating". ;)
No doubt! Everything should always be written in assembly language.
You can get crafty with a lookup table and stat(2).
I did stat against text files and a couple files in usr/bin, and against
EXCEL.EXE, and it called all of them 'regular files'.
How would I use stat and a lookup table to get a better description,
like 'file' provides? Isn't file and the 'magic' db as good as it gets?
I mention this mainly because if Laughing Boy was capable of reading
your article, he'll surely launch into a cackling fit that might brake
his brane. (That is...if he understood the program, which he probably
wouldn't.)
If you read the thread (it's old so hard to get to), Fool Feeb's
response to that code was to say it didn't actually work, because it
didn't use ncurses.
> (Regarding article lookups and such, I use a shell script that callsopenssl(1) s_client to connect, log in, and leaves me with the NNTP
prompt...a place at which Feeb would be lost.)
I use these most of the time: https://imgur.com/a/cj36AzT
Also custom python programs using the soon-to-be-deprecated nntplib
library.
Using that NNTP prompt, can you store messages locally? How?
Les messages affichés proviennent d'usenet.