On Mon, Nov 24, 2025 at 1:49 PM Daniel Kiper <[email protected]> wrote: > I am not convinced we have to have this. I want to hear other folks > opinion here. If you convince me to have this behavior for these > commands I think this exception have to be documented in the GRUB > documentation.
I have found myself sometimes forgetting to add the -p, so for example having something like "blscfg (hd0,gpt2)/..." instead of "blscfg -p (hd0,gpt2)/..." and taking me a while to figure out why things didn't work as I expected them to. Coincidentally, this was the way a path was supposed to be passed to the implementation of the same command in the earlier versions of these patches. My logic was that it's better to error out explicitly when an unsupported argument is passed instead of just ignoring it silently, but let's see what others think. Thank you for the quick response and I'll prepare a new revision when a decision is made to keep this functionality or not. Best regards, Radoslav _______________________________________________ Grub-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/grub-devel
