08-02-2022, 04:08 AM
I downloaded the attachment ZIP instead of going looking for my modifications LOL. It seems to run fine as it is on Linux.
One thing to remember is that NPPP seems to be only for Windows. There is sort of a counterpart for it called "notepadqq" but it's incredibly fiddly for me. The two programs look enough like each other.
It's possible to edit source code in GEdit (GNOME), Pluma (old GNOME now called MATE) or Mousepad (XFCE), which all have the same code base, but it won't be to everyone's liking programming in BASIC, while it does have style sheets for C++, Lua, Python and those other languages. I have yet to figure out if GEdit/Pluma stores configurations for style sheets and where, and then I might have ventured creating one of my own for QB64.
One that I'm using on Manjaro is called Leafpad but that's even simpler, almost like ordinary Notepad on Windows. It does have a few options like word-wrap and line numbering. Even simpler than that is nano, which uses the terminal for its viewport. It's good for quick-and-dirty details like editing ".somethingrc" or a "dot-d" inside "/etc".
Or you might want to go into complex realms such as Geany or Kate. The latter for KDE system is actually quite good for editing source code except it has one glaring oversight, it doesn't word-wrap as expected from an ordinary word processor, or like a text editor being used like word processor. There is a cut-down version of Kate called KWrite. I know and care less about Geany.
On all Linux-only programs mentioned you might want to watch out while using "Save As" and take note of "Line Ending" or "Newline" option in the dialog, choose "Windows" for CHR$(13) + CHR$(10), "Linux" for just CHR$(10) or (unlikely) "MacOS" for CHR$(13) only.
Otherwise I think there is a "sed" script somewhere that could convert Windows newlines into Linux and vice-versa. But "sed" is a program not for those who don't want to learn terminal-related things.
One more thing that I would have posted in another one of your threads weeks before I actually joined this site. Do not use apostrophe into a filename because it confuses the "bash" command processor. Sometimes on Linux it's better to give program names all in lowercase so it's easy to type, and for people who dislike using the [SHIFT] key. :/
One thing to remember is that NPPP seems to be only for Windows. There is sort of a counterpart for it called "notepadqq" but it's incredibly fiddly for me. The two programs look enough like each other.
It's possible to edit source code in GEdit (GNOME), Pluma (old GNOME now called MATE) or Mousepad (XFCE), which all have the same code base, but it won't be to everyone's liking programming in BASIC, while it does have style sheets for C++, Lua, Python and those other languages. I have yet to figure out if GEdit/Pluma stores configurations for style sheets and where, and then I might have ventured creating one of my own for QB64.
One that I'm using on Manjaro is called Leafpad but that's even simpler, almost like ordinary Notepad on Windows. It does have a few options like word-wrap and line numbering. Even simpler than that is nano, which uses the terminal for its viewport. It's good for quick-and-dirty details like editing ".somethingrc" or a "dot-d" inside "/etc".
Or you might want to go into complex realms such as Geany or Kate. The latter for KDE system is actually quite good for editing source code except it has one glaring oversight, it doesn't word-wrap as expected from an ordinary word processor, or like a text editor being used like word processor. There is a cut-down version of Kate called KWrite. I know and care less about Geany.
On all Linux-only programs mentioned you might want to watch out while using "Save As" and take note of "Line Ending" or "Newline" option in the dialog, choose "Windows" for CHR$(13) + CHR$(10), "Linux" for just CHR$(10) or (unlikely) "MacOS" for CHR$(13) only.
Otherwise I think there is a "sed" script somewhere that could convert Windows newlines into Linux and vice-versa. But "sed" is a program not for those who don't want to learn terminal-related things.
One more thing that I would have posted in another one of your threads weeks before I actually joined this site. Do not use apostrophe into a filename because it confuses the "bash" command processor. Sometimes on Linux it's better to give program names all in lowercase so it's easy to type, and for people who dislike using the [SHIFT] key. :/