Liste des Groupes | Revenir à col advocacy |
On Wed, 17 Apr 2024 16:08:47 -0400, DFS <nospam@dfs.com> wrote in
No doubt! Everything should always be written in assembly language.Note: I do know how to write C to scan directories and list files andI looked at those, and had to do a double-take with the
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.
second one.
Calling "file" is "cheating". ;)
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'.
I mention this mainly because if Laughing Boy wasIf 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.
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.)
openssl(1) s_client to connect, log in, and leaves me withI use these most of the time: https://imgur.com/a/cj36AzT
the NNTP prompt...a place at which Feeb would be lost.)
Les messages affichés proviennent d'usenet.