>> making this change is going to be a high bar to get over. Yes, I agree.
>> Most of the screen usage is in the set of functions that handle >> process start and stop in functions-common. This is exactly what I am saying. It's already abstracted up to some extent. May be we can leverage it. >> If we did move from screen to tmux. We aren't moving away... I have emphasized this enough. One should be able just "choose" tmux explicitly otherwise things will run in screen by default, as usual. On Thu, Jul 3, 2014 at 11:24 AM, James Polley <j...@jamezpolley.com> wrote: > > > > On Thu, Jul 3, 2014 at 12:55 AM, Anita Kuno <ante...@anteaya.info> wrote: > >> On 07/01/2014 08:52 AM, CARVER, PAUL wrote: >> > Anant Patil wrote: >> >> I use tmux (an alternative to screen) a lot and I believe lot of other >> developers use it. >> >> I have been using devstack for some time now and would like to add the >> option of >> >> using tmux instead of screen for creating sessions for openstack >> services. >> >> I couldn't find a way to do that in current implementation of devstack. >> > >> > Is it just for familiarity or are there specific features lacking in >> screen that you think >> > would benefit devstack? I’ve tried tmux a couple of times but didn’t >> find any >> > compelling reason to switch from screen. I wouldn’t argue against >> anyone who >> > wants to use it for their day to day needs. But don’t just change >> devstack on a whim, >> > list out the objective benefits. >> > >> > Having a configuration option to switch between devstack-screen and >> devstack-tmux >> > seems like it would probably add more complexity than benefit, >> especially if there >> > are any functional differences. If there are functional differences it >> would be better >> > to decide which one is best (for devstack, not necessarily best for >> everyone in the world) >> > and go with that one only. >> > >> > >> > >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > OpenStack-dev@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> Actually as a tmux user I really like that devstack uses screen, that >> way when I have screen running in tmux, I can decide (since they have >> different default key combinations, Control+A for screen and Control+B >> for tmux) which utility I am talking to, screen or tmux. >> >> Thanks, >> Anita. >> > > As a long-time nested-screen user I've run into this a lot. I've always > run a local screen session on my desktop/laptop; and then another session > on the machine I use to do real work. > > When I used screen I always used to use "escape ^ee" on my local session > (as I used it less) and left the remote at the default, so that I could > choose which session I was controlling. > > Now that I've switched to tmux, I do the same - but with tmux the command > is "set prefix C-e". I find tmux easier to get set up than screen because I > can have a simple shell script on my local machine that sets it up as a > "master" session. > > If we did move from screen to tmux (it sounds like we have a long way to > go before we're convinced it's worth the effort), I don't think the key > bindings will be something that should sway the decision one way or the > other - they're very easy to change. > > >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
