view the rest of the comments
Mildly Infuriating
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
The amount of times I've fucked up my template documents for forms and had to go back and revert them because they were autosaving and I hadn't set them to read only makes me not a huge fan of autosave being on automatically. Is the problem easily solvable? Yes. Have I somehow still not gotten used to autosave even though it's the norm for like a decade at least? Also, yes. But there it is. A reason why for you.
Auto saving versions is the solution. Don't like the one from 5 minutes ago? How about 10 minutes ago? How about 15? Etc
Incremental auto saves, I like it
The versioning is how I revert them. Making them read only so I can only save change in a new file is how to actually prevent the issue in the first place.
"Easily solvable" is an understatement, though. Autosave should maintain parity with the undo buffer, and manual saves should be pointers to a specific point in time, like tags. The only way this gets complex is branching - if you go back in time and start making changes from there, do we just prune it, do we allow the user to go back and undo undo, or, if we have something decidedly less fucking garbage than MS Word, do we facilitate merging?
I'm talking about my specific issue when I say that it's easily solvable. Fixing the problem is as simple as making sure the template files are read only and if I do forget to do that revert them back to before I made edits using versioning.
I suppose, but I'd argue that in your case the deficiencies are even more obnoxious: modifying a template should require deliberate effort on your part, with the default save action automatically creating and switching to a new file - otherwise why even have template filetypes?
I don't have it saved as a different filetype. It's just a .docx. I'm not even sure there is a "template" filetype available with word. Maybe I should look into it.
Easy access to usable version control would help in both cases