Clicking on file tab causes file to disappear and reappear on a new instantiation (window) of Sublime Text.
Description of the bug
This happens on Ubuntu. I have multiple files open in Sublime Text represented by the same number of tabs across my window. I click on a tab to go to the indicated file and the tab disappears and the file opens in a new instantiation (window) of Sublime Text.
I have received feedback from other correspondents who believe that this behavior has something to do with moving the mouse slightly while clicking the tab. I think they believe that Sublime Text is trying to drag and drop and for some reason.
As you can see, this bug or something similar was reported as early as 2021-10-04.
NOTE: As I have worked through this bug report, I have become convinced that this has something to do with drag and drop on tags. Opening a new Sublime Text window if there isn't a satisfactory drop target might be considered a "feature" by some (not me). If this is the case, I would be minimally satisfied if you gave me a way to disable the tag drag and drop feature. I must have a usable text editor for linux. Sublime is the only candidate. I will be reasonable on this. If you think that opening a new window for a tag "drop" is a good idea, then just let me disable the whole feature.
Steps to reproduce
I have tried multiple times to click the mouse and then move it a little. I failed to cause the file to appear in a new window until I clicked the tab and then pulled it down into the displayed file. Bango! The tab disappears and reappears in a new window.
Expected behavior
I would not expect the tab to be relocated until I released the mouse in a VALID position, that is somewhere inside the tab bar.
Actual behavior
A new window is opened containing the clicked tab.
Sublime Text build number
4169
Operating system & version
Ubuntu 22.04.4 LTS
(Linux) Desktop environment and/or window manager
Gnome
Additional information
No response
OpenGL context information
No response
Are you using X11 or Wayland?
I am using Wayland. Should I switch? Thanks!
On Sunday, March 24, 2024 at 09:47:06 PM EDT, Benjamin Schaaf ***@***.***> wrote:
Are you using X11 or Wayland?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Related (to be able to find those quickly): #4895 #6179
FWIW: For me, it does happen sometimes too in ST. Where it happes quite often is in SM.
It's also my impression that it started after switching to Wayland.
You can temporarily launch ST in XWayland using GDK_BACKEND=x11 subl in order to confirm if this is a wayland specific issue.
Hi Benjamin, I proceeded as follows: exit sublime text @.:~/projects/c-compiler/library$ GDK_BACKEND=x11 @.:~/projects/c-compiler/library$ echo "$GDK_BACKEND" x11 restart sublime text The problem is still there. I haven't been on linux for 12 years. Did I get the syntax right? Did I set the correct environment variable? Are you the person at world HQ who is looking at this bug? I am programming 7 days a week (I am retired) and this problem is eating me alive. It seems almost continuous. Regards, John
On Tuesday, March 26, 2024 at 09:41:09 PM EDT, Benjamin Schaaf ***@***.***> wrote:
You can temporarily launch ST in XWayland using GDK_BACKEND=x11 subl in order to confirm if this is a wayland specific issue.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Yes I work for Sublime. The correct way of temporarily launching Sublime Text using x11 is exiting sublime text and running GDK_BACKEND=x11 subl as stated in my previous message.
I executed the following from the command line: @.:~/projects/c-compiler/library$ GDK_BACKEND=x11 @.:~/projects/c-compiler/library$
The problem is still happening.
On Wednesday, March 27, 2024 at 09:00:55 AM EDT, Benjamin Schaaf ***@***.***> wrote:
Yes I work for Sublime. The correct way of temporarily launching Sublime Text using x11 is exiting sublime text and running GDK_BACKEND=x11 subl as stated in my previous message.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
You dropped the "subl" from the command, perhaps that's not showing in your email viewer. Please run:
$ GDK_BACKEND=x11 subl
I followed your instructions. The bug has not reappeared for several hours.
On Wednesday, March 27, 2024 at 09:10:58 PM EDT, Benjamin Schaaf ***@***.***> wrote:
You dropped the "subl" from the command, perhaps that's not showing in your email viewer. Please run: $ GDK_BACKEND=x11 subl — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
I could not capture a video (for whatever reasons on my setup) with the GDK_BACKEND environment, but that definitely changed the way tabs were moving, it was more sane. With 4174 dragging tabs feels much better on Wayland.
I get this issue on OS X Tahoe, but only seems to happen whe in Full Screen mode and I have sublime split with another app on full screen. Very annoying.