The Save As window does not remember last-used folder in the same session. Every subsequent time I Ctrl+S the same document, it should open in the folder I last saved to.
I can not confirm with Version: 6.1.0.0.alpha0+ Build ID: 88f6ffeb9e0c0b942c2b0bc9d60af7bb7a6caaf8 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; If you're using /tmp directory, then it doesn't work, because of patch: author Justin Luth <justin_luth@sil.org> 2017-01-20 15:59:25 +0300 committer Justin Luth <justin_luth@sil.org> 2017-02-03 04:37:25 +0000 commit eb9f90186ae52efa7ff884b3e64f5dd59ddc0329 (patch) tree f2a2dd0110154217505595223e6b11dea3b19a09 parent c0d3916cb7777918dbca359e88fb69f92ebf93ff (diff) tdf#80807 guisaveas: never recommend system's tempdir Various download-and-open mechanisms save to the system's $TEMP dir. If so, don't recomment saving in that same location in the GUI dialog! That's just silly. What's your last used folder?
It worked fine in ~/downloads and ~/documents, but it did not remember /tmp BTW I made a typo in my first post, it should have been "Ctrl+Shift+s" for "Save As", not "Ctrl+s" for "Save".
"That's just silly" Nothing silly about saving to /tmp when one wants the document to be gone after powering off. Seems like the patch was made in good faith, but the user knows better what the user wants.
(In reply to Stapler from comment #2) > It worked fine in ~/downloads and ~/documents, but it did not remember /tmp > Thanks for testing. Because it only doesn't work in /tmp , then closing as notabug -> see patch mentioned in comment 1
UX team, please take a look if some switch should make sense
As raal points out in c2 this feature was introduced for safety reasons. When you open a document from a website it is stored at /tmp and this may end up in data loss when we keep the path. You can save the file everywhere but /tmp will never be the suggested path. As a "workaround" for your problem just type /tmp/ before the file name.
Thanks for looking into it. "Safety feature" is sort of an explain-all which can easily be used to justify many a thing. It's not a convention among other software to handle /tmp in a special way with regard to UX. What this feature essentially does is presume I don't know what I'm doing, presume it knows better, and get in my way, so I oppose it.