Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

window resized during startup are missed #368

Closed
mc-butler opened this issue May 23, 2009 · 7 comments
Closed

window resized during startup are missed #368

mc-butler opened this issue May 23, 2009 · 7 comments
Labels
area: core Issues not related to a specific subsystem prio: low Minor problem or easily worked around

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/368
Reporter ossi (@ossilator)
Mentions yury@….com (@zyv)

if you start mc in an xterm and resize the terminal before mc shows the panels, it will not be adjusted to the terminal's size until you resize again once the panels are there.

@mc-butler
Copy link
Author

Changed by ZYV on May 24, 2009 at 9:48 UTC (comment 1)

  • Cc set to yury@….com

I can confirm this. But I think this one was present at least in 4.6.1 from Ubuntu's stock repos. Not that it does not need to be fixed though.

@mc-butler
Copy link
Author

Changed by angel_il (@ilia-maslakov) on Jun 17, 2009 at 14:49 UTC (comment 2)

  • Milestone changed from 4.7 to future releases

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jun 21, 2009 at 16:03 UTC (comment 3)

  • Version changed from master to pre4.6.1

yes, of course. i'm a bit careless with the extra fields. :}

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jul 4, 2009 at 8:27 UTC (comment 4)

  • Status changed from new to closed
  • Resolution set to duplicate
  • Severity set to no branch

Actually duplicate of #117.

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Aug 25, 2009 at 8:16 UTC (comment 5)

  • Milestone future releases deleted

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jul 11, 2010 at 9:48 UTC (comment 6)

  • Resolution duplicate deleted
  • Status changed from closed to reopened

while this *may* turn out to be a dupe at the code level, i'm pretty sure you do no know that at this point. the last comment from pavel in the original submission is also pretty explicit ...

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jul 11, 2010 at 13:15 UTC (comment 7)

  • Version changed from pre4.6.1 to master
  • Status changed from reopened to closed
  • Resolution set to duplicate

What's the point of keeping two separate reports for the issues that have to be solved together? I moved the text from this report to another one so that I won't get forgotten in any case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: low Minor problem or easily worked around
Development

No branches or pull requests

1 participant