From: Eliot Moss <moss@cs.umass.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23840@debbugs.gnu.org
Subject: bug#23840: runemacs does not seem to pass command line arguments through to emacs properly
Date: Sat, 25 Jun 2016 12:47:06 -0400 [thread overview]
Message-ID: <a3bdb017-92e3-7d75-fd01-8c72fe47bf8f@cs.umass.edu> (raw)
In-Reply-To: <83h9chz1wm.fsf@gnu.org>
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
next prev parent reply other threads:[~2016-06-25 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:57 bug#23840: runemacs does not seem to pass command line arguments through to emacs properly Eliot Moss
2016-06-24 19:02 ` Eli Zaretskii
[not found] ` <2d5c8e7b-1ca9-05fe-3946-b25b63655057@cs.umass.edu>
2016-06-25 6:59 ` Eli Zaretskii
2016-06-25 15:53 ` Eliot Moss
2016-06-25 16:08 ` Eli Zaretskii
2016-06-25 16:47 ` Eliot Moss [this message]
2016-06-25 18:44 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3bdb017-92e3-7d75-fd01-8c72fe47bf8f@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=23840@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).