You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The exec builtin seems to support parsing flags (based on error messages if you try and provide one), but it doesn't actually define any flags. Bash's exec takes 3 flags, 2 of which are clearly useful and one of which is questionable. I think we should at least add support for the -l and -a flags.
-l: If the first argument to exec is -l then this prefixes the zeroth arg with a dash as login does.
-a name: This flag passes name as the zeroth arg.
exec -l foo is clearly just shorthand for exec -a -foo foo, but is admittedly convenient.
As it is, if I want to replace my fish shell with a command using a custom name I need to write something like exec bash -c 'exec -a foo bar' which is silly.
The text was updated successfully, but these errors were encountered:
The
exec
builtin seems to support parsing flags (based on error messages if you try and provide one), but it doesn't actually define any flags. Bash'sexec
takes 3 flags, 2 of which are clearly useful and one of which is questionable. I think we should at least add support for the-l
and-a
flags.-l
: If the first argument toexec
is-l
then this prefixes the zeroth arg with a dash aslogin
does.-a name
: This flag passesname
as the zeroth arg.exec -l foo
is clearly just shorthand forexec -a -foo foo
, but is admittedly convenient.As it is, if I want to replace my fish shell with a command using a custom name I need to write something like
exec bash -c 'exec -a foo bar'
which is silly.The text was updated successfully, but these errors were encountered: