Saving Unreliable

Just gonna drop this here that saving is unreliable.

I really enjoy just using vscode instead of my browser as an editor. Unfortunately, on multiple occasions now, I've lost work even after an apparent successful save.

Sometimes after opening a browser it will revert the state it was last save, pre any changes I made in vscode (probably due to caching or something) and then vscode looses my work.

Lately when I go to shut down my computer I save what I've done in a separate text editor before shutting down my computer because even after a "save" and rebooting it just returns to what it was in HackMD without any of the changes I made in VS Code upon restarting.

Basically what this boils down to is the save function being so unreliable I have to save my text in a separate program to trust that my work wont be undone by the previous version of what's stored on HackMD overriding what I've done locally, even though when I save it should update MackMD with my saves. It only does this some of the time.

As nice of an idea as this plugin is, unreliable saving and losing multiple hours of work and having to use a separate app to save my state just makes it too clumsy. I use this extension because HackMD has native formating, like bolding headings without being told to that I wanted full control of styling, but then I lost reliable saving by switching to this plugin.

Inizia riproducendo il flusso di salvataggio di VS Code descritto: salva le modifiche, apri HackMD in un browser e riavvia il computer per verificare se uno stato precedente del documento sovrascrive il lavoro locale. Traccia il percorso di salvataggio e sincronizzazione dell’estensione e considera l’issue conclusa quando le modifiche persistono in questi scenari senza essere annullate.

Scritto dal modello di indicizzazione a partire dal testo della issue.