On Sat, 23 Mar 2024 09:44:54 -0700 (Seattle), Relf wrote:

Snag a .PDF file, any PDF file.

Make it a .TXT file & open it in a text editor.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Only on that dummy OS known as Microslop does one first
have to change the suffix to "TXT."

For any professional OS, just open the file in a text editor
because a professional OS doesn't give a flying fuck about
file name suffixes.

But Microslop STILL bases everything, including EXECUTION,
on the file name suffix.

How fucking retarded!

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

If only Jeff-Ass would commit himself (or herself) (its self?)
then we could begin to clean up COLA.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

rBowman:

Forth had it's uses.

Snag a .PDF file, any PDF file.

Make it a .TXT file & open it in a text editor.

Now you're editing "Forth" (PostScript).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Diego Garcia wrote:

Relf wrote:

Snag a .PDF file, any PDF file.

Make it a .TXT file & open it in a text editor.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Only on that dummy OS known as Microslop does one first
have to change the suffix to "TXT."

At the risk of incurring the wrath of -highhorse for spending time
configuring my work PC, IMO a properly-configured Windows machine has
a shortcut to a good text editor in the "sendto" menu. Right-click
and send any file to the editor.

I also clear out all the crap the M$ stupidly puts in the sendto menu.
One of many things required to get a WinDOS install "ready".

It's hard to believe that the default, compromise configuration out of
Redmond doesn't work well for everyone, right? /s

--
"Tell us again how you use Windows during the day to make an income
turd." - "Hadron", taking his best shot

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 23 Mar 2024 09:44:54 -0700 (Seattle), Relf wrote:

Now you're editing "Forth" (PostScript).

PostScript is somewhat different from Forth. I like to illustrate the difference this say: compare

YOU FORTH LOVE IF HONK THEN

versus

you postscript love {honk} if

In Forth, you have a distinction between “compile time” and “run time”. In
PostScript, hardly anything happens at “compile time”. Note how control constructs (conditionals, looping) are not specially handled at “compile time”; they are just built-in functions.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/23/2024 1:10 PM, Diego Garcia wrote:

On Sat, 23 Mar 2024 09:44:54 -0700 (Seattle), Relf wrote:

Snag a .PDF file, any PDF file.

Make it a .TXT file & open it in a text editor.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Only on that dummy OS known as Microslop does one first
have to change the suffix to "TXT."

Only a braindead OS and its mentally ill "developers" would create and distribute files with no extension.

Is it an executable? A text file? A library? An image file? A
gnumeric spreadsheet? A LibreOffice Calc spreadsheet?

"duhhh... let me waste lots of time opening a terminal and typing the
whole file name to ask 'file' to open the file and look for 'magic
bytes' and try to find them in the 'magic' database. I sure hope the
file type is in there.. duh..."

What a waste of personal time and computing cycles.

This! Is! Linux!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

DFS <nospam@dfs.com> wrote at 14:13 this Tuesday (GMT):

On 3/23/2024 1:10 PM, Diego Garcia wrote:

On Sat, 23 Mar 2024 09:44:54 -0700 (Seattle), Relf wrote:

Snag a .PDF file, any PDF file.

Make it a .TXT file & open it in a text editor.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Only on that dummy OS known as Microslop does one first
have to change the suffix to "TXT."

Only a braindead OS and its mentally ill "developers" would create and distribute files with no extension.

Is it an executable? A text file? A library? An image file? A
gnumeric spreadsheet? A LibreOffice Calc spreadsheet?

"duhhh... let me waste lots of time opening a terminal and typing the
whole file name to ask 'file' to open the file and look for 'magic
bytes' and try to find them in the 'magic' database. I sure hope the
file type is in there.. duh..."

What a waste of personal time and computing cycles.

This! Is! Linux!

A lot of Linux file managers use the file's magic number to display a
file type in the same way Windows does. Also, Windows doesn't know
every file type, there are plenty that just display the generic
"[EXT] file".
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

candycanearter07 wrote this copyrighted missive and expects royalties:

DFS <nospam@dfs.com> wrote at 14:13 this Tuesday (GMT):

Only a braindead OS and its mentally ill "developers" would create and
distribute files with no extension.

Is it an executable? A text file? A library? An image file? A
gnumeric spreadsheet? A LibreOffice Calc spreadsheet?

Cry harder.

"duhhh... let me waste lots of time opening a terminal and typing the
whole file name to ask 'file' to open the file and look for 'magic
bytes' and try to find them in the 'magic' database. I sure hope the
file type is in there.. duh..."

You could always open the file if "file" cannot detect it.

Or right click on it in a decent file explorer (e.g. Thunar) and look at its "Properties".

What a waste of personal time and computing cycles.

This! Is! Linux!

How often do you ever need to use "file", whiner? I did use it a few days ago to discover that a .po file was using ISO-8859-1 instead of UTF-8 encoding.

Hint: The encoding is not discoverable by <laughing> file extension.

A lot of Linux file managers use the file's magic number to display a
file type in the same way Windows does. Also, Windows doesn't know
every file type, there are plenty that just display the generic
"[EXT] file".

DFS is part of the "8.3" DOS crowd.

--
It has long been an axiom of mine that the little things are infinitely
the most important.
-- Sir Arthur Conan Doyle, "A Case of Identity"

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Chris Ahlstrom <OFeem1987@teleworm.us> wrote at 16:07 this Tuesday (GMT):

candycanearter07 wrote this copyrighted missive and expects royalties:

DFS <nospam@dfs.com> wrote at 14:13 this Tuesday (GMT):

Only a braindead OS and its mentally ill "developers" would create and
distribute files with no extension.

Is it an executable? A text file? A library? An image file? A
gnumeric spreadsheet? A LibreOffice Calc spreadsheet?

Cry harder.

"duhhh... let me waste lots of time opening a terminal and typing the
whole file name to ask 'file' to open the file and look for 'magic
bytes' and try to find them in the 'magic' database. I sure hope the
file type is in there.. duh..."

You could always open the file if "file" cannot detect it.

Or right click on it in a decent file explorer (e.g. Thunar) and look at its "Properties".

Fair

What a waste of personal time and computing cycles.

This! Is! Linux!

How often do you ever need to use "file", whiner? I did use it a few days ago to discover that a .po file was using ISO-8859-1 instead of UTF-8 encoding.

Hint: The encoding is not discoverable by <laughing> file extension.

It's also useful to quickly check the dimensions of multiple images.

A lot of Linux file managers use the file's magic number to display a
file type in the same way Windows does. Also, Windows doesn't know
every file type, there are plenty that just display the generic
"[EXT] file".

DFS is part of the "8.3" DOS crowd.

oh
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 26 Mar 2024 12:07:58 -0400, Chris Ahlstrom wrote:

Hint: The encoding is not discoverable by <laughing> file extension.

If file extensions are so important, why does Windows go to the trouble of hiding them?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 26 Mar 2024 10:13:24 -0400, DFS wrote:

Is it an executable?

If it has executable permissions, then yes. Otherwise, no.

What language is it written in? Is it a compiled binary? Or an interpreted language? Who cares? If I change the implementation from one to the other, should I have to change the name? Do users have to invoke it a different
way? No.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Lawrence D'Oliveiro wrote this copyrighted missive and expects royalties:

On Tue, 26 Mar 2024 12:07:58 -0400, Chris Ahlstrom wrote:

Hint: The encoding is not discoverable by <laughing> file extension.

If file extensions are so important, why does Windows go to the trouble of hiding them?

Probably to avoid scaring the typical Windows user.

--
You'll wish that you had done some of the hard things when they were easier
to do.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Chris Ahlstrom <OFeem1987@teleworm.us> wrote at 12:23 this Tuesday (GMT):

Lawrence D'Oliveiro wrote this copyrighted missive and expects royalties:

On Tue, 26 Mar 2024 12:07:58 -0400, Chris Ahlstrom wrote:

Hint: The encoding is not discoverable by <laughing> file extension.

If file extensions are so important, why does Windows go to the trouble of >> hiding them?

Probably to avoid scaring the typical Windows user.

Yeah, and that's also why they warn the user when renaming the extension manually.
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

candycanearter07 wrote this copyrighted missive and expects royalties:

Chris Ahlstrom <OFeem1987@teleworm.us> wrote at 12:23 this Tuesday (GMT):

Lawrence D'Oliveiro wrote this copyrighted missive and expects royalties:

On Tue, 26 Mar 2024 12:07:58 -0400, Chris Ahlstrom wrote:

Hint: The encoding is not discoverable by <laughing> file extension.

If file extensions are so important, why does Windows go to the trouble of >>> hiding them?

Probably to avoid scaring the typical Windows user.

Yeah, and that's also why they warn the user when renaming the extension manually.

On my work laptop (no longer relevant), I'd map the "*.text" extension to run gvim on a double-click. Goddam Notepad.

--
Let us endeavor so to live that when we come to die even the undertaker will be sorry.
-- Mark Twain, "Pudd'nhead Wilson's Calendar"

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Chris Ahlstrom <OFeem1987@teleworm.us> wrote at 19:23 this Tuesday (GMT):

candycanearter07 wrote this copyrighted missive and expects royalties:

Chris Ahlstrom <OFeem1987@teleworm.us> wrote at 12:23 this Tuesday (GMT): >>> Lawrence D'Oliveiro wrote this copyrighted missive and expects royalties: >>>

On Tue, 26 Mar 2024 12:07:58 -0400, Chris Ahlstrom wrote:

Hint: The encoding is not discoverable by <laughing> file extension.

If file extensions are so important, why does Windows go to the trouble of >>>> hiding them?

Probably to avoid scaring the typical Windows user.

Yeah, and that's also why they warn the user when renaming the extension
manually.

On my work laptop (no longer relevant), I'd map the "*.text" extension to run gvim on a double-click. Goddam Notepad.

Oh cool, I forgot Windows has vim.
--
user <candycane> is generated from /dev/urandom

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 2 Apr 2024 19:40:13 -0000 (UTC), candycanearter07 wrote:

Oh cool, I forgot Windows has vim.

Most definitely. It's the second thing I install right after Brave. Even
better both Visual Studio and VS Code have Vim extensions.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)