I'd like to bring the current behaviour of the file tabs to discussion, as the corresponding issue on github has been closed. My problem is that switching between files with cmd-T or clicking on files in the file browser reorders the tabs, moving the current file's tab to the right of the old file's tab. This behaviour is, so I'm told, to make sure that closing the open file will result in going back to the previous file. How is it then that changing files by clicking on the tab does not change the order?
To me it seems this behaviour is quite odd, and it's not standard UI (or is there another app that moves tabs around like this?).
In my mind, tabs also serve the purpose of organising, and people may want to have tabs in a logical order (e.g. chapters in a LaTeX project). The fact that tabs can be manually dragged around suggests that this is something the user can set and which should not be changed by the program.
In order to keep the intended function of returning to the previous file when the current one is closed, why not simply keep a history list of tabs per window?
Jonas