opened 04:40PM - 17 Jul 21 UTC
error
## xonfig
<details>
```
+------------------+----------------------+
| xo…nsh | 0.9.27 |
| Git SHA | 71fe9014 |
| Commit Date | Jan 29 08:58:58 2021 |
| Python | 3.9.5 |
| PLY | 3.11 |
| have readline | True |
| prompt toolkit | 3.0.19 |
| shell type | prompt_toolkit |
| pygments | 2.9.0 |
| on posix | True |
| on linux | True |
| distro | ubuntu |
| on darwin | False |
| on windows | False |
| on cygwin | False |
| on msys2 | False |
| is superuser | False |
| default encoding | utf-8 |
| xonsh encoding | utf-8 |
| encoding errors | surrogateescape |
| on jupyter | False |
| jupyter kernel | None |
| xontrib 1 | apt_tabcomplete |
| xontrib 2 | direnv |
| xontrib 3 | kitty |
+------------------+----------------------+
```
</details>
## Expected Behavior
When running a (pipeline) command that's not found, a simple error message should be generated, e.g. bash does this
```
egnor@ostrich:~$ asfdafd
asfdafd: command not found
```
## Current Behavior
With xonsh I see two generally redundant error prints:
```
$ asfdafd
xonsh: subprocess mode: command not found: asfdafd
asfdafd: command not found
```
## Steps to Reproduce
1. Run a command that doesn't exist
2. Experience a teensy, tiny, itty bitty moment of minor cringe at the duplicate message
## For community
⬇️ **Please click the 👍 reaction instead of leaving a `+1` or 👍 comment**