[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report er
|
From: |
Eli Zaretskii |
|
Subject: |
bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external |
|
Date: |
Sun, 16 Jan 2022 11:04:29 +0200 |
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sat, 15 Jan 2022 20:03:46 -0800
>
> Despite this incompatibility, I still think this is the right change to
> make for all these commands. If a user passes unrecognized options to
> any of these, they should be informed of that fact.
OTOH, with the current behavior shell scripts that use options not
supported by Eshell commands will silently run unaltered, wheres with
your change they will error out. Do we care about this?
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Jim Porter, 2022/01/15
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external,
Eli Zaretskii <=
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Jim Porter, 2022/01/16
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Jim Porter, 2022/01/19
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Eli Zaretskii, 2022/01/20
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Jim Porter, 2022/01/20
- bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external, Lars Ingebrigtsen, 2022/01/21