Hi Tomas,
> Oh, I see. My problem in understanding how to use kwalletcli stems
> from the ambiguity of the word "folder". It can also mean a
> directory, as in directory in the filesystem.
No, only on Windows® really, and even there it’s wrong terminology
people got used to over years of misuse (like using + to concatenate
keys depressed simultaneously; I’ve got early Microsoft® manuals
getting both things right).
A folder is the thing in IMAP where you store eMails in, and
the thing you put in a shelf, into which you put archived
invoices and stuff like that. Well, in general IT terminology.
In KDE Wallet terminology, a “folder” is like the DN of an
LDAP entry, and an “entry” is like an attribute.
> So what I was doing is:
>
> kwalletcli -e entry -f $PATH_TO_THE_WALLET
The “PATH_TO_THE_WALLET” is called a Wallet in KDE Wallet
terminology. kwalletcli only supports using the default
wallet; KDE 5 ships another CLI which supports using ar‐
bitrary wallets, but requires the user to specify the one
to use, so it does something different from kwalletcli.
> May I suggest this patch to the man page to disambiguate the meaning
> of folder or respectively to make it's context more clear, and to add
> a simple example:
I’ll think about it. I might not use the exact patch, but
thanks for correcting my assumption that shipping four
example scripts was enough.
> +echo MYPASSWORD | kwalletcli -e Stackoverflow -f Websites -P
「\*(Ba」, not a raw 「|」; also, “echo” would add a newline,
which breaks other users of the wallet data, as the newline
would be interpreted as being part of the password (hence the
“printf '%s' "$password"” in my example).
bye,
//mirabilos
--
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)
