Respect $TR_AUTH like cli tool transmission-remote about stig HOT 18 CLOSED

from stig.

Sounds great, even better than what official transmission-remote offers :)

from stig.

@doronbehar, I currently don't see the real benefit of reading $TR_AUTH. Why
don't put set srv.url user:password@host:port in your rc file?

from stig.

Well first of all, I think that having a password in plain text in a configuration file is a bad habit.

The way I set $TR_AUTH in my shell configuration files for transmission-remote is using pass just like this. I think it's much better than storing the password in the configuration file.
Another great solution would be to have something like srv.password_eval = pass transmission useful for people who use password managers like pass or gnome-keyring.

from stig.

from stig.

Haha, I liked that :)

Reading the environmental variable is a great start but as for having an option like password_eval just like in this programs:

• msmtp: https://wiki.archlinux.org/index.php/msmtp#GnuPG
• mutt: https://unix.stackexchange.com/a/20572
• vdirsyncer: http://vdirsyncer.pimutils.org/en/stable/keyring.html#command
• toxic (tox client): JFreegman/toxic#434

from stig.

from stig.

What you said Yuck about is exactly what I'm doing in the .zsh_credentials file in my dotfiles repository.

from stig.

from stig.

Oh now I understand, you were thinking of something similar to what they do in muttrc (as explained here: https://unix.stackexchange.com/a/20572).

Maybe you should enable splitting the srv.url into srv.host, srv.port, srv.user and optionally srv.password which could be interpreted with something similar to fetch. Then you won't have to worry to much about sub-shells and quotes, you could just make the fetch command by default interpreting a shell command. That's only one sub-shell if I'm correct.

from stig.

from stig.

You are funny :),

I don't think It has to brake backwards compatibility, it might be possible to specify in the manual or something that srv.url is overriding srv.host, srv.port, srv.user and srv.password or the other way around but than you will still have to solve #24 elegantly. I guess it will be much easier for you to remove the srv.url and use only the above variables instead exactly as you said.

I'll agree with either of those choices :)

from stig.

from stig.

Thanks for you reaching out your users 👍, Hope to see it in the next version.
Cheers!

from stig.

I've extended the 'set' command so that you can now append ':eval' to the name
of a setting to indicate that the value is a command:

set connect.password:eval pass transmission

from stig.

Works great! Thanks!

from stig.

Sorry for necrobumping but I wanted to share that this makes it possible to use env vars in the config 👍

set tui.theme:eval echo $XDG_CONFIG_HOME/stig/themes/stig_darker_theme.txt

from stig.

how do i set username?

from stig.