Your comments

Ok this is totally fsck0red. Ctrl+Tab does actually cycle back through the history, but you have to keep holding Ctrl down for it to work, which means you can't bind it to the back button of a mouse and have it work in any sensible manner.

It's also totally backward in that adding the Shift key makes it go forward. Some people may be familiar with this, but I recommend binding the historical back (currently Ctrl+Tab) to Super+[ and forward (currently Ctrl+Shift+Tab) to Super+], and (most importantly) get rid of the resetting that happens when you let go of the modifier key.

Use something else to "reset" the stack, such as manually navigating to a new document.
The Window menu should also be hierarchical and show all open tabs for each window in a second level.
While having a menu that lists all open tabs in and of itself is not a bad idea, please don't replace the tabs with such a menu.

Frankly, multiple rows (wrapping) tabs is the best way I can think of to handle this.
Ctrl+Tab should imo cycle through the tabs in the order they appear in the window, and Ctrl+Shift+Tab goes backwards.

What Nicolay is asking for (and I totally agree with) is a history-based command that goes to the *previously-viewed* tab or file, like the Back button of a browser.

I'm totally used to this in Visual Studio and it feels odd not having the ability to navigate historically to what I was just looking at 5 seconds ago. What made it really great in VS is that it would even work *within* a file, so if you navigate to a function (by going to its definition) it would add that navigation to the history stack as well.
Is tab still usable to pick an item from the autocomplete popup? I don't like it completing words for me without a dialog because I have no indication that it's going to happen.
Same for go to definition.
Wow somebody downvoted this? Odd.

"I actually prefer to be less productive, thank you." :)
Maybe the logo should be a submarine with a lime on it. ;)