Hi.
Thank you for the comment. YAD is just there to be used or not. What I do is basically avoid the command-line for mcrypt where I sometimes forget options and have to repeat my actions.
Quote:
Originally Posted by Habitual
zenity/yad is "cute" but in the end, I'd only write something for end users.
|
Right. But the options, even for YAD are many and the frugal task to create a GUI around a script will be a chore, when you first have to work out all the details. As for the exercise, mcrypt asked for some digging into the syntax for YAD and I also had to make the resulting values palatable to mcrypt. This is a new way to write shell-scripts for me. I cannot say that I were shell-guru and believe that it shows anyway.
Quote:
# Remove pre-existing files if we are about to replace them anyway.
Should that happen after the encrypt?
|
There are two use-cases:
remove the encrypted file, before writing a new one and
remove the decrypted file, prior decrypting again. My impression is that both work with the current script. This way, I avoid the program asking for the user's decision.
No, but what I was really aiming for (not with YAD but) with this thread was your comments on mcrypt and the possible uses. I admit, that I could have been more specific but the question is not really clear to myself...
The information that
something is wrong with mcrypt does not satisfy me and having my problems with
gpg2 -c or crypting stuff with OpenSSL, mcrypt is still my utility of choice. I never understood the problem, nor if the library or only the executable program was affected. I have an encrypted partition, but admit that I have almost or actually no use for it. Moving encrypted files around is much more interesting for me than to store them for good and possibly destroy them all at once, in case of (what?) emergency...
In conclusion, if mcrypt is useable and nice, my YAD script might ... make it
even better, I guess.., or something.