well I’ll give you that but for a repo with only src and the compiled binary there’s not much detective work to do.
Like my code block states these
filename.swp files hold all the made changes to
filename since opening it for editing. These files are non-volatile, meaning they stay as long on disk as you do not close the open buffer (in this case a file to edit) properly. Now if you e.g. get a power outage or your terminal crashes you’d lose all your unsaved changes you were editing. However, since the .swp files exist you can recover the already made changes and continue working where you left of.
Furthermore, they serve as an actual lock file! Try opening a file in vim and in another terminal try opening the same file again. In the second terminal you’ll get a warning that the file you’re trying to open is already opened and changes you were about to make in this instance may cause troubles.
Nowadays in days of full fledged IDEs with permanent auto save features these
*.swp file could be seen as relicts from old times. Finally, when you use
vscode and you close your editor without saving all your files and open it up again later on (even after reboot) your unsaved but opened files are still there. That’s the same magic vim does for ages but less obvious to the user .
But that’s enough off topic for now. If you have further questions let’s move this to discord/dm