When you feed search results to a listbox and close Krusader and then immediately apply the command
find . *.* -mtime -0,01 -type f -printf "%TY-%Tm-%TdT%TT %p\n" | sort -r | ssed -R 's/^([^.]+)\.\d+ (.*)$/\1 \2/'
you see which files have been modified during the last 1/4 hour or so. Investigating file modification dates you see, that these two files are modified by Krusader:
~/.config/krusaderrc
~/.local/share/krusader/virtualfilesystem.db
Both of them are printable. Both together keep record on what you did and find out with Krusader. The second file contains the VFS made by find operations followed by "Feed to listbox".
It looks like that one can manipulate both files with an editor or by a script. After deletion they are reconstructed when Krusader starts. However after deleting ~/.config/krusaderrc
Krusader starts with the lengthy prologue as if it had been started for the first time.
This script deletes the database and copies a reset-version over ~/.config/krusaderrc
:
#!/bin/bash
# ******************* ResetKrusader.sh *******************
# This script removes all vfs from Krusader.
# It deletes ~/.local/share/krusader/virtualfilesystem.db
# and it copies ~/.config/krusaderrc_reset to
# ~/.config/krusaderrc
# The reset version can be obtained by deleting
# ~/.config/krusaderrc, then starting Krusader and go
# through the first steps of Krusader until it is in the
# two-windows mode. Then leave Krusader.
# This way you get a new version of this file which
# has the two lines
#
# [ViewerModule]
# FirstRun=false
#
# at its end such that Krusader can enter its normal work
# mode without the "first run" prologue when started.
# Just make a copy ~/.config/krusaderrc_reset of
# ~/.config/krusaderrc at this moment.
# ********************************************************
rm ~/.local/share/krusader/virtualfilesystem.db
rm ~/.config/krusaderrc
cp ~/.config/krusaderrc_reset ~/.config/krusaderrc
Just make a reset state version ~/.config/krusaderrc_reset-state
as described in the comment inside the script.
I guess it would not be very difficult to add a housekeeping function about the memorized VFS to krusader itself letting one decide to delete one or the other memorized VFS. There doesn't seem to be much programming capacity behind this project, but actually Krusader is very useful!
On the other hand, the entry barrier is quite high to change the code of programs like Krusader by oneself and upload an improved proposal. I have failed so far to get something like this into the IDE Eclipse (not to mention all the difficulties that come afterwards!)