https://bugs.documentfoundation.org/show_bug.cgi?id=165070
Jeff Fortin Tam <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Non-existent removed files |Non-existent removed files |remain shown in the open |remain shown in the open |"Recent Documents" menu's |"Recent Documents" menu's |list |list, without visual | |distinction --- Comment #7 from Jeff Fortin Tam <[email protected]> --- > Onus is on user or os/DE to restore the FS mounts? In my as-reported description, I personally am not in the usecase where the filesystem comes in and out of existence. I am dealing with local filesystem files have been deleted / moved away, they don't exist anymore, they will never come back in that exact spot, and I shouldn't have to baby-sit the office suite app to tell it that my local filesystem's deleted files were deleted, because it can check that automatically for me. By saying I understand the USB usecase, I'm just going the extra mile to try to accomodate _your_ usecase, even though I have some doubts about how common it is and whether it's actually critically needed to maintain history of recent files from hotplugged "external media" (i.e.: it would really not the end of the world for me if those files were purged from the recent documents list automatically, because whenever I plug a USB drive, the file manager will automatically open it in front of me and show me its contents, from which I can open a file directly). > Not something required of LibreOffice to track. It is, if you want the app to provide a smart humanized UX instead of cluttering the view with counterproductively stale results (instead of keeping those limited numbered slots dedicated to actual existing files) and expecting users to manually manage their filesystem in an office suite "in addition to managing it in their file manager". I shouldn't have to do the work in two places. In other words, I'm trying to advocate for LibreOffice to present more relevant "current" results rather than stale non-actionable ones. A concession/tradeoff I can make here is: if you really really really don't want to remove the non-existent-files results automatically, then they should at least be grayed out so that "offline/vanished" files are visually different and my eyes can ignore the grayed-out ones, to spot the actually relevant ones more easily... but that doesn't provide the advantage of being able to "free those spots" in the list for more actually-existing results. -- You are receiving this mail because: You are on the CC list for the bug.
