Conversation

Notices

1. Karl Voit :emacs: :orgmode: (publicvoit@graz.social)'s status on Wednesday, 23-Mar-2022 11:37:05 UTC Karl Voit :emacs: :orgmode:

   RT @chazhutton@twitter.com

   Today’s Comic (version 12_old_NEW)

   🐦🔗: https://twitter.com/chazhutton/status/1506218579414458368

   • Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • TeMPOraL (temporal@mastodon.technology)'s status on Wednesday, 23-Mar-2022 11:37:34 UTC TeMPOraL

     in reply to

     @publicvoit yeah, OSes badly need a per-file version control as a base platform API.

     Also, I just realized another problem with the modern "no files, no save" paradigm - while continuous auto-saving may be fine in principle, you lose the opportunity to tag versions at specific point in time. E.g. "this, right here, is 'we sent this to customer X'".

     (Not that file-based UX makes that easy.)

     We need a single-click/press feature that's equivalent of Save + Copy w/ rename + mark the copy as read-only.

   • Karl Voit :emacs: :orgmode: (publicvoit@graz.social)'s status on Wednesday, 23-Mar-2022 11:39:15 UTC Karl Voit :emacs: :orgmode:

     in reply to

     • TeMPOraL

     @temporal I'm not sure if we really do need a per-file VCS.

     However, the Save copy with different name is a good idea and also a standard feature of most tools I'm using: "Save as ..."

   • TeMPOraL (temporal@mastodon.technology)'s status on Wednesday, 23-Mar-2022 11:39:15 UTC TeMPOraL

     in reply to

     @publicvoit Yes, but my point is that it's backwards for typical workflow. "Save as ..." asks you to provide a new name for the document you'll continue to edit. But usually, the old name is fine for that - what you want is to provide a name for the copy that you *won't* be editing.

     E.g. I'm writing a proposal (proposal.docx), I send the current version to customer and continue working on it - I want to "Save current as copy" to 2022-03-23-proposal-sent-to-ACME.docx and continue editing proposal.docx.

     Santa Claes 🇸🇪🇭🇰🎅 likes this.