Skip to main content
Became Hot Network Question
deleted 9 characters in body
Source Link
Tetsujin
  • 117.7k
  • 26
  • 201
  • 346

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's Sometimes shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

It seem's weird !sudo output'soutputs sudo syscallbypid.d

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

It seem's weird !sudo output's sudo syscallbypid.d

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal? Sometimes shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

It seem's weird !sudo outputs sudo syscallbypid.d

added 58 characters in body
Source Link
ABC
  • 141
  • 7

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

It seem's weird !sudo output's sudo syscallbypid.d

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.

It seem's weird !sudo output's sudo syscallbypid.d

Source Link
ABC
  • 141
  • 7

MacOSX Big Sur - Terminal ZSH Shell Command's Execute Sometimes With "!" Exclamation Symbol In Front

Is this normal behavior for MacOS Big Sur ZSH (Z Shell) terminal behavior? Sometime's shell commands such as find and or launchd as just a simple example execute properly. This is with the exclamation symbol "!" in front, leading with the expected output and no privilege escalation.

For example, running: !find / will still work. Or !sudo will execute.

But !echo '@' will not. But lead to the next command sometimes.

Output for !echo

zsh: event not found: echo

Output for !launchd

launchd

launchd cannot be run directly.