Emacs doesn't start from icon after update to 1.7.25

Ken Brown kbrown@cornell.edu
Mon Sep 23 13:16:00 GMT 2013


On 9/22/2013 5:38 PM, KARR, DAVID wrote:
>> -----Original Message-----
>> From:
>> Ken Brown
>> Sent: Sunday, September 22, 2013 1:13 PM
>> On 9/22/2013 2:06 PM, KARR, DAVID wrote:
>>>> -----Original Message-----
>>>> From: On Behalf Of
>>>> Ken Brown
>>>> On 9/21/2013 8:42 PM, KARR, DAVID wrote:
>>>>>> -----Original Message-----
>>>>>> From:  On Behalf Of
>>>>>> Ken Brown
>>>>>> On 9/20/2013 7:26 PM, KARR, DAVID wrote:
>>>>>>> Today I updated 1.7.25.  I was a handful of minor releases behind at
>> the
>>>>>> time.
>>>>>>>
>>>>>>> After the update, I can't start Emacs from the icon anymore.  The
>>>> shortcut
>>>>>> command I have for it is the following:
>>>>>>>
>>>>>>>         C:\Cygwin\bin\run.exe -p /usr/bin bash -l -i -c "emacs -display
>>>>>> 127.0.0.1:0.0 --debug-init"
>>>>>>
>>>>>> I don't think this has anything to do with emacs.  There have been
>>>>>> several reports of problems with run-1.3.0-1.  Try downgrading to the
>>>>>> previous version of run, or switch to run2.
>>>>>
>>>>> I first tried just changing the command line to "run2".  No change.
>>>>
>>>> run2 is not a drop-in replacement for run.  If you want to use it, you
>>>> have to install the run2 package and read the documentation.  Or you
>>>> could run the script /usr/bin/make-emacs-shortcut, which creates a
>>>> shortcut that uses run2.
>>>
>>> I already had run2 installed.  I ran "make-emacs-shortcut".  I moved the
>> resulting shortcut to the desktop, giving it a new name.  I double-clicked
>> it.  Nothing happened.  I than created a cmd window and pasted in the command
>> line from the shortcut and ran it.  Nothing.  I then pasted in the command
>> line from the old shortcut, and Emacs came up.
>>
>> I'd like to find out what went wrong with the shortcut created by
>> make-emacs-shortcut.  What's the target?  And what are the contents of
>> the emacs.xml file that it uses?
>
> Target: C:\Cygwin\bin\run2.exe --display 127.0.0.1:0.0 /usr/local/bin/emacs.xml
>
> /usr/local/bin/emacs.xml:
> ------------------
> <?xml version="1.0" encoding="us-ascii"?>
> <Run2Config
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>    xsi:noNamespaceSchemaLocation="run2.xsd">
>    <SelfOptions />
>    <Global>
>      <Environment />
>    </Global>
>    <GDI>
>      <Environment />
>      <Target filename="/usr/bin/bash.exe" startin="~">
>        <Arg>-l</Arg>
>        <Arg>-c /usr/bin/emacs-w32.exe</Arg>
>      </Target>
>    </GDI>
>    <X11>
>      <Environment>
>        <Set var="DISPLAY" value="127.0.0.1:0.0"/>
>      </Environment>
>      <Target filename="/usr/bin/bash.exe" startin="~">
>        <Arg>-l</Arg>
>        <Arg>-c emacs</Arg>
>      </Target>
>    </X11>
> </Run2Config>
> -----------------

This looks right, and it works fine for me on both 32-bit and 64-bit 
Cygwin.  I don't know why it doesn't work for you.  Does 'cygcheck 
/usr/bin/run2.exe' show anything unexpected?  What about 'run2 --help' 
(in a Cygwin bash shell)?

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list