Feature request: Shell alias expansion

[croissong]

It would be nice to be able to use aliases in the watch commands :)

[davidandradeduarte]

I've closed #9, since it was a duplicate of this one.

[davidandradeduarte]

Apparently if we do this:

alias my_alias="viddy " (note the extra space after the command)

It starts working with aliases:
my_alias k get pods -n all (k for kubectl)

[croissong]

True, but this has the same shortcoming as mentioned here: https://unix.stackexchange.com/a/25329

Unfortunately this method has a limitation that you cannot provide options to watch because the alias has to be the next word, whereas watch needs its arguments before the command to run. If you tried watch -n 10 , bash won't expand the alias

[sachaos]

To solve this, should I parse the file which is defining the aliases (e.g. bashrc or zshrc)?

I haven't come up with another good way to do it.

[croissong]

The command could be called via the shell:

shell := os.Getenv("SHELL")
cmd := exec.Command(shell, "-ci", "k get pods")

This could be considered insecure though, so maybe it could be opt-in via flag?

[davidandradeduarte]

Yep, that would be my suggestion too!

Get the shell and execute the command within that shell.

Should work for the most used shells at least.
* with fish i think the arguments order need to be ic instead of ci.

[sachaos]

Thank you! I understood.

[sachaos]

@croissong @davidandradeduarte I've added new options --shell, --shell-options in v0.1.8 .
Now, you can run alias command like following examples.

Please specify your aliases in ~/.profile (the files which are loaded on starting as login shell).

Define you aliases in .profile

alias ll="ls -l"

Run viddy

viddy --shell-options "--login" ll

How do you think this solution?

To run on the shell interactive mode, we should run a command on PTY.
It is not difficult implementation, but it is too complex to just support alias.
And interactive mode will load rc file (e.g. bashrc, zshrc), it is too heavy to call every time. (I'm defining much of functions and using complex prompt).
So I recommend to run a command on login shell with specifying --login option.
This will load profile file only.

The --shell-options is long name option, but I'm planning to implement loading the configuration from a file.

[davidandradeduarte]

It's good to at least have the option, but I don't think most users will maintain a separate file for aliases just to use in viddy :/

We can get them easily with:

alias | xargs -I {} echo "alias {}" > ~/.profile

But it's hard to maintain.

This will not work for me right now tho, because you're only getting the first string from the alias.
e.g

alias ll=ls -la

only gets ls instead of ls -la.

If I change it to

alias ll="ls -la"

with quotes, it works.

On another note, I've tried the --shell options with:

viddy --shell "/bin/zsh" ll

and doesn't seem to work either. Maybe I'm doing something wrong, haven't looked at the code yet.

Edit:

alias | parallel -I {} echo "alias {}" > ~/.profile

using parallel instead of xargs, doesn't remove the single quotes from aliases.

[sachaos]

@davidandradeduarte

This will not work for me right now tho, because you're only getting the first string from the alias.
e.g

alias ll=ls -la

I think this is invalid alias definition. The quotation is necessary.

On another note, I've tried the --shell options with:

viddy --shell "/bin/zsh" ll
and doesn't seem to work either.

When you want to use alias, you should specify --shell-options "--login" to load the alias definition file.

I think maintaining alias file is easy.
I suggest to create file for the aliases, and load that from .profile and rc file (e.g. .bashrc) like following.

Define alias in .alias

alias ll="ls -l"

Load that from .profile and rc file (.bashrc) too

source ~/.alias

[croissong]

@sachaos Thanks for the update!
It works as you described, and I understand the problems with the interactive mode.
For me personally, sourcing my aliases in .profile is fine.

I wasn't aware of the implications of using interactive mode outside of a pty, and to be honest, i still don't fully understand it (and how it can be solved).

But as far as i can tell, running the shell in non-interactive mode still provides all the other advantages of spawning a shell (e.g. pipes work), so i am perfectly happy with this solution 👍

[sachaos]

Thank you for trying out.

I couldn't get the output from interactive mode shell.
But, it might be my mistake.
Il've used golang pty package, and that worked.
I'm not using that now, to keep it simple.