Normalizing --script and --load behavior to respect "--"

Normalizing --script and --load behavior to respect "--"

[Psionic K]

I noticed that --script does not seem to respect the normal "--" cutoff for
arguments.  I expected Emacs would consume all arguments it supports and
then set `argv' to the remaining arguments, using "--" to distinguish when
to stop trying to consume.

I believe --load and --script should be similar because otherwise a script
has to skip over or interpret arguments that were intended for Emacs.

My A/B problem is running tests with a graphical window versus without.
Because --quick --no-window-system --load <file> presents a dilemma of how
to report test feedback, I used --script to run tests without a window and
encountered the behavior difference.

I'm currently using a workaround to consume extra arguments conditionally
in the loaded elisp file.

Nix wrapper scripts exhibit problematic interaction with this issue.  I
used the direct path to the binary to confirm that the behavior exists
without the wrapper.  --script always sees all of the arguments while --load
only sees non-Emacs arguments.

-- 

Psionic K <psionik@positron.solutions>
Software Engineer

*Positron Solutions <https://positron.solutions>*

Re: Normalizing --script and --load behavior to respect "--"

[Emanuel Berg]

Psionic K wrote:

> I noticed that --script does not seem to respect the normal
> "--" cutoff for arguments. I expected Emacs would consume
> all arguments it supports and then set `argv' to the
> remaining arguments, using "--" to distinguish when to stop
> trying to consume.

Example ...

-- 
underground experts united
https://dataswamp.org/~incal