[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23840: runemacs does not seem to pass command line arguments through
From: |
Eli Zaretskii |
Subject: |
bug#23840: runemacs does not seem to pass command line arguments through to emacs properly |
Date: |
Sat, 25 Jun 2016 19:08:57 +0300 |
> From: Eliot Moss <moss@cs.umass.edu>
> Cc: 23840@debbugs.gnu.org
> Date: Sat, 25 Jun 2016 11:53:22 -0400
>
> However, I think we're making progress on diagnosing this. When I
> looked very closely at the mode line in emacs, I could see the underscores
> were actually there. The two cases start up pointing to the same file
> name in the same folder. In the runemacs case, however, the file is
> not present by the time emacs pops up. Here is my theory. runemacs
> returns immediately after starting emacs. Thunderbird sees that
> return, reads back in the file it wrote, and deletes the file. Then
> emacs tries to open the file and does not see it.
>
> 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.