bug#23840: runemacs does not seem to pass command line arguments through to emacs properly

[Eliot Moss]

On 6/25/2016 12:08 PM, Eli Zaretskii wrote:
> > From: Eliot Moss <moss@cs.umass.edu>
> > Cc: 23840@debbugs.gnu.org
> > Date: Sat, 25 Jun 2016 11:53:22 -0400

> > If this theory is right, what I need / desire is for runemacs to wait
> > for the emacs child.  But AFAICT runemacs is not designed to do this.
> > I end up desiring a case not provided for, and hence probably need to
> > just live with the annoying pop up console window.
>
> That's a sensible explanation.
>
> > At least I think we have an explanation.  Still, it would be nice if
> > I could tell runemacs to wait ...
>
> You should be able to have that if you give runemacs the -wait option.
> But that's a very unusual way of using Emacs, so I won't be surprised
> if there are more problems on the way.

Aha!  It indeed works with -wait, which needs to be at the beginning of
the command line passed to runemacs (I looked at the source to verify
this).  So, I have a solution -- thank you for your help!

Regards -- EM