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

Bug: macOS tabs forgotten on when reopening app #450

Open
onecrayon opened this issue Mar 31, 2019 · 4 comments
Open

Bug: macOS tabs forgotten on when reopening app #450

onecrayon opened this issue Mar 31, 2019 · 4 comments

Comments

@onecrayon
Copy link

Version info

  • OS: macOS 10.14.3
  • Build: 1107

Description

After opening one (or more) tabs in Merge on macOS, quitting the program, and reopening all of the tabs are loaded as separate windows.

Steps to reproduce

Steps to reproduce the behavior:

  1. Open Merge
  2. Use Window => New Tab to create a new tab, and load a repo in the tab
  3. Quit Merge
  4. Relaunch Merge
  5. Check the Window menu and note that the tab has been separated into its own window

Expected behavior

I expected that on relaunching Merge the window would load tabbed as it was when I quit.

@srbs
Copy link

srbs commented Apr 1, 2019

Sublime * products only have basic support for macOS native/window tabs. As far as SM knows, they are all separate windows & not actual tabs. See also my comment on #451 for future native tabs support.

@voltechs
Copy link

voltechs commented Apr 19, 2019

Sublime * products only have basic support for macOS native/window tabs. As far as SM knows, they are all separate windows & not actual tabs. See also my comment on #451 for future native tabs support.

While I can't directly refute your statement, I can say with certainty that SublimeText (3) does not behave this way. It remembers[1] all the tabs and fullscreen status.

1. SublimeText3 does not remember separate windows and tabs; if I have two windows each with different sets of tabs, ST3 will combine them upon relaunch into one window, and (if I was in fullscreen mode) fullscreen those.

@onecrayon
Copy link
Author

If they don't want to receive bug reports for poorly implemented features, then they shouldn't poorly implement features. Future plans don't matter; tabs on macOS are broken now and are negatively impacting my workflow just about daily.

It is of course the dev team's prerogative to ignore this bug report for whatever reason; but please don't try to excuse away or discourage bug reporting simply because they have good intentions for the future.

@srbs
Copy link

srbs commented Apr 29, 2019

See also #466. I'm thinking the integration with macOS native/window tabs might, in some way, depend on the existence of native tabs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants