Hi, I fully agree to all of Martin's listed points. There are just things where an application has better knowledge of tabs or whatever it might be and how it should get arranged.
I can understand that some people would rather have their WM do that job, probably mostly to have coherent key bindings, but with Vimperator's powerful mapping support that is easily doable. I try do get all my applications that I use a lot to have similar (in my case, vim style) key bindings. But back on topic, I still let the WM handle multiple browser windows in one specific situation: to view to web pages side by side. I have tried some "split" add-on for Firefox to do this, there was even a Vimperator plugin for better keyboard control somewhere, but it still sucked hard. Now I just do :tabdetach and use awesome for this. The only thing that is a bit ugly is to get the tab back to the first browser window. I can't see how having all tabs in separate windows could work. The WM would not have the URLs / page titles (well, the later maybe through the client name) so one would miss a quick tab navigation like :b aw<TAB> you have in Vimperator to jump the open awesome tab. Going through 10-20 windows in the WM would just take longer, no matter how good they are arranged. On Mon 2009-06-01 14:16, Martin Stubenschrott <[email protected]> proclaimed: > On 06/01/2009 03:04 AM, Josh Rickmar wrote: > 6.) Google chrome opens new tabs next to the originator of where this tab was > opened. > And when you close it, it switches back to the originator. Nifty feature > which > firefox should really also have but, again, impossible when just using WM > tabs. Try the "Tabs Open Relative" add-on: https://addons.mozilla.org/de/firefox/addon/1956 Greetings, Frank -- Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A
signature.asc
Description: Digital signature
