These are stored in ~/.config/gtk-3.0/bookmarks even though the version of PCManFM installed by default in Lubuntu 14.04 is gtk-2.0.īy the way, I use this alias when I want to find what's recently changed in my home folder: alias 5m='find ~/ ! -path "/home/dkb/.mozilla/*" ! -path "/home/dkb/.cache/*" ! -path "/home/dkb/.config/google-chrome/*" ! -path "/home/dkb/.config/libreoffice/4/user/*" ! -path "/home/dkb/.dropbox/*" ! -name "recently-used.xbel" -mmin -5 -type f -ls' (The /boot file copy that occurs during vessel launch for the boot file happens outside the context of the terminal interpreter, so it wouldn't normally appear on screen like all other exceptions would.Shortcuts appearing in the side pane are termed "bookmarks" in PCManFM.
Copypath kos code#
The second is to make special case code in the boot file initialization process that will communicate this message to the user in an unusual way. The fix is to also insert a message on the prior step, so that the reason the file is missing is made clear. The problem should be fixed, you are right, but the fix isn't to change that message. It's saying it cant' find it on the local volume.
Copypath kos archive#
It's not saying it can't find it on the archive volume. (Note the filename it's complaining about is "/boot/whatever" rather than "0:/boot/watever". Once the local copy doesn't exist, it's correct to say it can't find it. The problem is caused by the earlier step - when copying the file from the archive to the local volume - not issuing a complaint message when it doesn't fit and therefore fails to make the local copy. The error message that it cannot find the file is correct and shouldn't be "fixed". To check if the file exists first, and then if it does try to open it, is essentially causing the system to walk the directory twice over.Īnyway, it's not important because we don't have exception handling anyway and can't do it that way right now, and I'd rather wait until we can implement it right, rather than do it quick and easy and then have backward compatibility headaches later because of it.
Copypath kos software#
the usual way to deal with "file not found" errors in most software is that the software just tries to open the filename without checking first, and then uses the fact that the file open command returned an error code as its means of discovering that the file doesn't exist and the user should be shown an error message. (edit: well, technically, it's the rm program that would have to handle it, not bash, but it's the same general principle. (Or imagine being the writer of bash and having to deal with a user typing in rm alksdjfalksdjlfk without having bash crash because of it.) It's not the programmer of HAL's fault that Dave typed in garbage. Sorry, I could not find 'asdfasdfasdf', Dave. Which program are you trying to run> asdfasdfasdfasdf Whereas with using a boolean return value, it's the other way around and the default behvior from a lazy program would be no message, no indication that something is wrong, and the program continues on silently. It makes it so exiting the program is the default you get when you write lazy code, and you have to go out of your way to make it ignore the error and continue. The advantage of throwing an exception is that when you don't explicitly add error handling to your script, you will get it to bomb out with a message. I'd normally favor throwing an exception, were it not for the fact that kerboscript doesn't do exception handling so it would make the script writer powerless to detect it and do something about it. We really should pick one and stick with it.
I have no clue why it was that way originally, though. He probably just inherited that inconsistency because he was trying to keep things as similar as possible to the old way, and built on top of the way it worked before. The problem that "not found" throws an error, while "volume full" just silently fails without complaint was true long before implemented his changes.
0 kommentar(er)
