--- Begin Message ---
|
Subject: |
runemacs does not seem to pass command line arguments through to emacs properly |
|
Date: |
Fri, 24 Jun 2016 10:57:16 -0400 |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 |
I use a Thunderbird add-on called "External Editor", that will invoke an
arbitrary editor program, passing on the command line the name of a file
to edit. If I tell External Editor to use runemacs, the file is not
opened, and any underscores in the file name appear as spaces in the name
of the buffer. I can ^X^F to the actual file, so the file is there, but
something in the runemacs->emacs transition seems to have converted
underscore to space in the file name.
OTOH, if I tell External Editor to use emacs instead of runemacs, the
proper file is opened but I get an annoying console window, too.
I've not been able to find any documentation on runemacs's command line
arguments, etc. This suggests that it is intended to simply pass them
on unchanged emacs. But something work than that seems to be happening.
Regards -- Eliot Moss
(Note: I am not subscribed to the list.)
(PS: I used to use Xemacs for this, but it is moribund and with Windows
10 exiting it causes Windows to think that it has crashed, popping up
two annoying windows that you have to dismiss to get back to Thunderbird.)
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#23840: runemacs does not seem to pass command line arguments through to emacs properly |
|
Date: |
Sat, 25 Jun 2016 21:44:54 +0300 |
> Cc: address@hidden
> From: Eliot Moss <address@hidden>
> 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.
--- End Message ---