Am Thu, Sep 12, 2024 at 08:53:17AM -0500 schrieb Dale: > Frank Steinmetzger wrote: > > Am Thu, Sep 12, 2024 at 07:54:25AM -0500 schrieb Dale: > >> Howdy, > >> > >> I use Dolphin a lot. I like it and all but recently, it started doing > >> something that annoys me. When I'm doing something, I tend to open a > >> instance of Dolphin for whatever it is I'm doing. I also leave > >> instances open and ready for when I do routine things. Some things I do > >> so often, I leave them open all the time. Usually that is four > >> instances. If needed, for example when I'm getting videos off trail > >> cameras, I open another instance until I'm done with that task. So, I > >> use Dolphin for different things on different desktops with tabs in > >> different places. It just makes things easier, faster and works best > >> for me. > >> […] > > Dolphin settings, very first page, very first setting: set it to open a > > fixed location at startup. Then it will not restore any previous internal > > state. > > I saw that setting. First place I looked. Thing is, since I didn't > want it to always start at the same place, I thought that wouldn't > work. I thought that no matter what I clicked, it would open at that > place. Given you said that would work, I tried it. I set it to /, or > root, but if I click on a folder on the desktop, sure enough, it starts > and opens the folder I clicked on. Did that a few times just to be > sure. LOL I also plugged in a USB stick, mounted it and then told the > notification thingy to open in File Manager. Yep, it opened right where > it should. I was looking for a instance setting or something since it > kept copying other running instances and their tabs. I wouldn't have > ever thought to try that setting. > > They might want to explain that setting a little bit. While I saw it, I > certainly didn't expect it to behave this way. I expected it to open at > that location no matter how Dolphin was started.
Perhaps it’s actually a bug. Even if Dolphin is supposed to restore a previous session, it *should* open the location it is given by parameter. > P. S. Planning to try that checksum script soon. It's a large number > of files so it will take a long time to run. I think you mentioned that > if stopped, it will resume where it left off. Only if it creates checksums, because it knows by the existence of checksums where to resume. But if you want to read checksums and verify them, you need to use arguments to tell it how many directories to process and how many to skip at the beginning. Perhaps try it first with a few small directories to get a feel for its behaviour. The normal way to go is: dh -u [DIR] to create the checksum files dh [DIR] do read it back Use the --skip option to skip the given number of dirs at the beginning. Remember that by default it will not create checksums in directories that have subdirectories. I know this sounds a little strange, but for a hierarchy of music albums, this seemed sensible 10 years ago. -- Grüße | Greetings | Salut | Qapla’ Please do not share anything from, with or about me on any social network. Big events may cast their shadow under the eyes.
signature.asc
Description: PGP signature
