#417 Window shrinks at startup or when opening a new tab

closed-accepted
nobody
None
3
2014-08-02
2012-08-04
Dawid Ferenczy
No

Console is a great application, I'm using it for a long time. Thank you for it :) But I'm experiencing very confusing bug, for a long time too. Often, when I open a new tab or at application startup, the Console window shrinks so much, that it's smaller, than window buttons (minimize, maximize, close) itself. Then, it's impossible to resize the window any way and I must restart the application. Sometimes it happens about 8 times from 10 attemps.

I'm using the 64bit Console 2.00.148 on 64bit Windows 7. Inside Console I'm using especially Cygwin and Git bash. There is my console.xml configuration file in the attachement.

It's very very confusing because Console is great application anyways and I'm using it on daily basis. Thank you for your interest.

Discussion

  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-04

    console.xml configuration file

     
    Attachments
  • Kirill
    Kirill
    2012-08-04

    Unfortunately, it's a known bug - using 32-bit shells in 64-bit console has this strange effect sometimes. About the only new info is it does not happen all the time.

    Workaround: use 32-bit version (side effect: you'll lose telnet).
    Another possible workaround: try to use 64-bit cmd as a wrapper around your bash. Kind of reverse from what you did for git.

     
  • Kirill
    Kirill
    2012-08-04

    • priority: 5 --> 3
    • status: open --> pending
     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-04

    Known bug? :) Could you provide me a reference to any related bug report, please? I couldn't find anything (using Google), before I wrote this bug report here.

    Yes, it doesn't happen all the time for me. Somethimes it happens 9 times in 10 attempts, sometimes it doesn't happen 9 times in 10 attemps. I didn't find out what it depends on.

    What does it mean "you will lose telnet"? What telnet do you mean? Native Windows telnet, Cygwin telnet, Cygwin netcat? And what do you mean "lose"?

    Thanks for workarround with using 64bit cmd as wrapper, I'm going to try that.

     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-04

    Is there any other consequence when using 32bit Console on 64bit system? I'm not using telnet, instead I'm always using netcat from Cygwin, so it will not affect me.

     
  • Kirill
    Kirill
    2012-08-04

    I guess the bug is not filed, but I do know about it (that's actually why my unofficial builds on http://kirill.ca have that feature disabled).

    32-bit Console uses redirected system32 (physically at SysWow64) which does not contain telnet.exe. Hence when you run 32-bit Console on 64-bit Windows, you'd get "'telnet' is not recognized as an internal or external command".

     
  • Kirill
    Kirill
    2012-08-04

    Sorry forgot some other side effect: environment variables don't match those from cmd. In other words, if you run cmd.exe, the environment variables will clearly indicate that it's 64-bit system (e.g. PROCESSOR_ARCHITECTURE); when you look at them in Console, they will be different. The explanation is again that you're running two different cmd's.

     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-05

    Great, thank you for your time and patience. I decided to use that workarround with using a 64bit cmd.exe as a wrapper for a 32bit shells. I don't see any consequence there. Is there any difference in using directly a 32bit shell and using a 64bit cmd.exe that runs a 32bit shell? (Except the bug with shrinking window? :)

    I wrote small scripts like "cygwin.cmd", "git_bash.cmd" and so on. Then I used that scripts as shells ("Shell" option on the "Tabs" settings page), so the 64bit Console runs the 64bit cmd.exe that interprets my script, which runs a 32bit shell, I guess. Am I right?

    For example, "cygwin.cmd" looks like this (some unimportand commands was ommited):

    "bash --login -i"

    Before, I used straight "bash --login -i" as my shell, so the 64bit Console runs directly a 32bit shell and it caused this bug. Right?

    Once more, thank you for your time.

     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-05

    • status: pending --> open
     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-08-05

    BTW what the status of development of the Console? Do you actively develop it or it's frozen?

    Once more, it's great application, common on Linux environments, but on Windows, I don't know better. Thank you :)

     
  • Kirill
    Kirill
    2012-08-05

    RE: Is there any difference in using directly a 32bit shell and using a 64bit cmd.exe that runs a 32bit shell?
    The main difference is that Console needs to do some tricks when running shells of "wrong bittness" (as you did when you had "bash --login -i" in your Tab > Shell), and the shrinking windows happens when the trick fails :) The only other differences are those environment variables and "disappearing" applications (like telnet.exe). So, if shell scripts are written carefully - e.g. don't try to distinguish 32-bit and 64-bit OS, the rest should just work. If something does not, maybe 64-bit cmd doesn't behave either.

    RE: using .cmd scripts
    Yes, you're right. If you didn't need those "unimportant commands", you probably could just use %COMSPEC% /c (or /k) to run your shells. For example, %COMSPEC% /c "bash --login -i" would be your Shell.

    RE: status of development
    I can't honestly say "It's under active development", but it's definitely not frozen.

     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-09-27

    Thank you for your support. I'm using the 32bit version now and I'm much happier :) I experienced some window-shrinks with the 32bit version too, but I have been able to enlarge the window with mouse.

    I'm using Console mainly for Cygwin, so I don't need clasic telnet, I have been never using it, because Cygwin's Netcat is much better.

     
  • Dawid Ferenczy
    Dawid Ferenczy
    2012-09-27

    • status: open --> closed-accepted
     
  • Drew Noakes
    Drew Noakes
    2013-01-02

    I see what I believe to be the same issue (Win 8 x65).

    You mentioned that the 32/64-bit trickery sometimes fails. Would it be possible to save the window state (pos/size/is-ma/min-inimized) before trying this trick, and re-applying the values afterwards? Even if the window flickered, it would be better than when it leaps across the screen and shrinks in size.

    I love this application and this is my one frustration with it. It's be great to see it solved!