From: Ben Armstrong, Wed, August 29, 2007 2:58 pm > > My wrapper for cream, which relies on being able to pass messages to > the vim server to open files properly, used to support opening each > new file in a new window by changing the servername to CREAM_## but > I see things have changed since then (probably several versions > back, now) so this no longer works. If I try to start cream with any > servername other than CREAM, I get these errors: > > Error detected while processing function Cream_singleserver: > line 129: > E241: Unable to send to CREAM
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.] > I'm wondering now how to continue to support those of my users who > prefer this arrangement. 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. > The wrapper has changed somewhat since that time. Now, for the > *initial* call to cream, I set a variable to pass to the cream-user, > which in turn calls Cream_file_open after Cream has finished > loading. But that still doesn't change the fact that everything is > forced into a single session now, so if I click on the Cream icon on > the user's desktop a second time, instead of getting a new icon, the > window just flashes and nothing happens. Any suggestions? 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? -- Steve Hall [ digitect dancingpaper com ] :: Cream... usability for Vim :: http://cream.sourceforge.net ------------------------------------------------------------------------- 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
