[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#14841: Frames created invisible have their visibility parameter set

From: Eli Zaretskii
Subject: bug#14841: Frames created invisible have their visibility parameter set to t
Date: Mon, 29 Jul 2013 18:26:03 +0300

> Date: Mon, 29 Jul 2013 09:54:52 +0200
> From: martin rudalics <address@hidden>
> CC: address@hidden, address@hidden
>  >> I still wonder whether a user can have her desktop link to
>  >> runemacs.exe have it run in a maximized window.  Here on Windows XP
>  >> this seems (no longer?) possible.
>  >
>  > How about using -mm or -fs option in the Target property of the
>  > Shortcut Properties of the desktop icon?
> -mm is only an approximation of maximizing since it doesn't hide the
> window borders.

It should do exactly what (fullscreen . maximized) frame parameter
does, so I guess you are already used to the above issue?

>  > You cannot do this via the "Run: Maximized" property, since emacs.exe
>  > is a console program, and therefore its only window runemacs can
>  > control is the console window (which it hides, that being the very
>  > purpose of runemacs's existence).
> So it apparently never worked and that's why I used the
> `w32-send-sys-command' solution.  Seems the correct solution is to have
> runemacs pass the size of the console window to emacs.

You mean, the solution is for emacs to _take_ the dimensions of its
frame from its console window, yes?  Because without that, runemacs
can pass whatever it wants, and no one will notice.

Assuming the above is possible (having the window both hidden _and_
maximized), patches are welcome.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]