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

[Eli Zaretskii <eliz@gnu.org>]

> Cc: 23840@debbugs.gnu.org
> From: Eliot Moss <moss@cs.umass.edu>
> Date: Sat, 25 Jun 2016 12:47:06 -0400
> 
> >> 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!

For the record, the "official" solution is to start a daemon session
of the Cygwin Emacs, possibly with the -nw option in your case, and
then use emacsclient to open frames in that session.  Alternatively,
setting the external editor to 'emacsclient --alternate-editor=""'
will start the daemon the first time it is invoked.

In any case, there's no Emacs bug here, so I'm closing the bug report.