[PATCH 21.5] Starting XEmacs 21.5 via cygwin's run command

[Vin Shelton]

Jonathan,

Thanks for replying with your detailed explanation.

On 8/19/07, Jonathan Harris <jonathan at xemacs.org> wrote:
> Vin,
>
> > Johnathan Harris edited the 21.5 version to remove the second call to
> > ShowWindow in May of 2002:
> >
> > 2002-05-06  Jonathan Harris  <jonathan at xemacs.org>
> >
> >       * frame-msw.c (mswindows_init_frame_3):
> >       Remove obsolete runemacs hack which called ShowWindow() twice.
> >
> > While I agree with the sentiment that 2 calls to ShowWindow is a hack,
> > it appears that the second call is necessary in this instance -
> > restoring the second call to ShowWindow makes the initial frame
> > appear.  This patch does restores mswindow_init_frame_3 to the
> > definition as it appears in 21.4.
>
> The problem with the second call to ShowWindow() is that it causes
> XEmacs to ignore any instructions to start up minimised or maximised, eg
> when started from a shortcut where the user has specified "Run:
> Minimized" or "Run: Maximized".
>
> If I understand correctly, you're using the cygwin run.exe command to
> suppress the console window that would be created if you started cygwin
> xemacs normally. The native Windows build of XEmacs doesn't have this
> problem - it is built as a "GUI" app and so does not create a console
> window on startup. So I suggest that you conditionalise the second call
> to ShowWindow() on ifdef CYGWIN.

Well, to clarify, if you were to use cygwin's run.exe to start the a
Windows native XEmacs, you would still see the problem (ie, no window
would pop up), but since the only reason to use run.exe is to start up
the application without creating a console window, there would be no
reason to use run.exe to start a Windows native XEmacs.  Therefore, I
think your suggestion to conditionalize around cygwin is a very good
one.Please see the attached patch.

Adrian - I added a pointer to the gmane permalink.

> (Or you could build cygwin XEmacs as a "GUI" app - but then you'd have
> to deal with the fact that you sometimes do want to see the output in
> the console window. Let me know if you're interested in taking this
> route and I'll explain how the native build gets round the problem).

Jonathan - I'm very interested in learning a little more about this.
Can you please send me a note explaining how the native port works
around this problem?

Thank you,
  Vin

-- 
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
-------------- next part --------------
A non-text attachment was scrubbed...
Name: frame-msw.diffs
Type: application/octet-stream
Size: 1977 bytes
Desc: not available
Url : http://lists.xemacs.org/pipermail/xemacs-patches/attachments/20070819/6bc232b0/frame-msw.obj