Steve Hall wrote: > Multiple sessions were eliminated in the previous versions to speed > start-up, eliminate window flutter, and fix all the bugs associated > with sessions over-writing each other's preferences (Settings, Recent > File menu, etc.). [Although I notice that we missed removing the > option from the Settings menu.] >
OK ... > Just to confirm: they prefer multiple Vim *sessions* as opposed to > multiple windows/tabs? Tabs give you the same interface as having > multiple sessions but without the extra overhead/bugs. I'd like to > understand what makes individual sessions more compelling than tabs. > I don't think they care how Cream/Vim manages it behind the scenes. All one session would be fine if every file would open in a separate window on the desktop so they can be individually resized and repositioned to suit their tastes. > You could just revert back to the pre-0.39 way of handling this, > nothing else has fundamentally changed. (Although it re-introduces the > bugs that single-session solves.) Perhaps there's something about your > wrapper that makes keeping individual sessions important? > I'd like to diverge as little as possible from the way you do things. Every change I make costs us to support. I'd rather convince you there is a legitimate case for users preferring multiple windows and then have it supported upstream. Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ cream-general mailing list cream-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cream-general
