-
when i try these commands inside clifm, they work perfectly:
I expect the same thing for alias internal command of clifm, but it doesn't work. why?
I didn't test other sub-commands and I don't know if this is a general behaviour or not. Is there any workaround for it? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Interesting. For
|
Beta Was this translation helpful? Give feedback.
-
Hi @LinArcX.
This precisely because
In this case there's not error message, since
This is the case for all internal commands. Since we do not support pipes or stream redirection, every time these shell functions are detected, and no internal command is involved, clifm sends the whole command to the system shell (which is why
Yes, but I'm pretty sure this is not what you're looking for. Since actions and aliases (just like most config stuff) are stored in text files (which as such are accessible from outside clifm), it is always possible to operate on these files using shell commands. Example: # Count number of aliases
grep ^alias $CLIFM/clifmrc | wc -l # Count number of actions
grep -Ev "^#|^$" $CLIFM/actions.clifm | wc -l This is a common procedure for writing plugins, but again, this is most likely not what you want. Note: The CLIFM environment variable holds the absolute path to your current clifm profile directory. |
Beta Was this translation helpful? Give feedback.
Hi @LinArcX.
This precisely because
alias
is an internal command. Clifm by itself does not support pipes or stream redirection, so that it is taking|
as a parameter for thealias
command, and since there's no such alias, it throws the appropriate error.In this case there's not error message, since
actions
does not take any parameter (they're just ignored).This is the case for all internal commands. Since we do not support pipes or …