Kate text-editor "projects" compile button...

[Tell-Sackett]

I formed a "debug button" "External Tools" template file for basic raylib projects/examples (similar to VSCode's "Run" button, I think) for the KDE project's text editor "Kate". My hope was to make something akin to the Notepad++ "projects" compile option provided by Raylib, but for Linux. I zipped the external-tool ini file, the raylib.ico file (one I downloaded from the Raylib source code), and the README.md file (which explains installation and customization options) together in this zip attatched below. However, (1) I've run out of time to work on this at the moment, (2) I don't know how to check markdown file syntax for GitHub README files, (3) I've never made a GitHub commit before (and am unsure of how to do so, as well as lack an understanding of understood formalities when making commits), and (4) am not looking to upkeep/update these files in the future. All of that said, I had already written-up this whole README.md file and felt it a shame to just trash it (especially considering some newer Linux users might find it useful).

If any proper developers finds these files useful such that you are willing to attempt a commit to GitHub and continue upkeep (or not continue upkeep, I suppose: hopefully the README instructions can continue to be useful enough as something of a guide in the future, even if the files themselves become deprecated), be my guest. Otherwise, I may pick this up again at some point down the road and attempt to make a commit... or not. As it stands, the file works, I just haven't (1) done a complete installation run-through (following the exact instructions, step-by-step, from the README.md) from a blank-slate machine, (2) completely triple-checked/proofread over the whole README.md file, and (3) checked that the syntax for the README.md file is correctly punctuated for GitHub's MarkDown renderer. I attempted to organize the zipped directory to emulate that of other Raylib "project" directories in the main branch.

If nothing is done/discussed with this discussion after some period of time, I will try and remember to come back and close it out (if it isn't already removed before then) in order to prevent clutter in this portion of the repository. Thanks.

Kate.zip

[Tell-Sackett]

After asking for advice over on Discord, I was told that it is generally bad practice to just provide a zip file download and that I should look at doing a PR with the individual files. Seeing as how I can't attatch each of the three, individual files here to the discussion (due to their file-types); I don't know how to make proper PR's; and I am not ready to commit to updates: I am closing-out this discussion thread.

What I stated above still stands, however: if you would like to take this and commit it, be my guest (you could probably do better than I did anyway, seeing as how I was unwilling to attempt a distro-agnostic installation script, for example).

If you don't care to make a commit and just want to learn how to implement this yourself, I'd recommend looking into Kate's built-in "External Tools" feature (and maybe look at the files provided above). The process of implementing this can be done via the GUI and without going into config files (contrary to how I chose to instruct the installation of my provided files), if one so chooses.

Sorry for not being committed enough to implement this.