this post was submitted on 23 Nov 2023
1 points (100.0% liked)

Remarkable

59 readers
2 users here now

Useful Links

founded 1 year ago
MODERATORS
 

Hi redditors!

I've been a 2.15 user with DDVK hack for some time now, and my experience has been great so far. New rm-hacks repo and 3.8 native features are tempting though.

I wanted to test the upgrade while beeing able to revert to 2.15 in case I don't like the new experience. I know the switch.sh script. My issue is the following : in 2.15, the only version I can update to seems to be 3.04, and not directly 3.8. However, if the update goes in two steps (2.15 -> 3.04, then 3.04 -> 3.8), I believe the 2.15 partition will be wiped by the two steps process, am I correct ? Then, how to upgrade to 3.8 and keeping the ability to revert back ?

Thanks for your help

Edit : Currently, one partition is on 2.15, the other one in 3.3

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 11 months ago (1 children)

Just to let you know, I was still able as expected to open 2.15 files in 3.8, but sure, once flipping to 2.15 again, the file cannot be open anymore since they are converted when first opened in 3.x

[–] [email protected] 1 points 11 months ago (1 children)

Thanks for letting me know.

So it sounds like the documents are converted the first time they're opened under the new software, rather than as a batch process when the new OS first boots.

If you had a document that worked in 2.x and didn't open under 3.x, was it still usable after downgrading back to 2.x? If so that would seem to confirm the theory.

[–] [email protected] 1 points 11 months ago

Absolutely. As long as you do not open a document in 3.x, they are still usable in 2.x. I was working on several documents in 2.15, and I was still able to open them after going to 3.8 then going back to 2.15. Actually, there is a message "Unable to display the document please upgrade the software" in every notebook you opened or created in 3.x. So indeed, conversion is on a per document basis and not a batch process at boot.

However, as you stated, it's still a rather unsafe situation as any miss click in 3.x will definitely make your document unusable in 2.x.