name new byobu sessions, only select byobu sessions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
byobu |
Fix Released
|
Wishlist
|
Unassigned | ||
byobu (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
I'm currently using byobu on launch on my home Atom system. I want to set up a separate screen session using crontab @reboot for running irssi, but while this works fine and connects me to IRC on reboot, when I try login to the system's CLI, byobu just reconnects me to the screen/IRC session.
Would it be easy/more sensible to make byobu only work with its own named sessions (byobu, byobu_1, byobu_2 etc) so that I can have separate "long-lived" sessions established automatically on a reboot, as opposed to byobu which will only launch the first time I login to the CLI after a reboot. This could also avoid the prompt asking me which screen session I want to connect to when I SSH in with both screen/IRC and byobu running.
Alternatively, can I run byobu on @reboot so that byobu is launched straightaway and make irssi a subwindow of byobu? I'd prefer to keep the separate screen session however as I like to have the CLI and IRC open in separate windows and this wouldn't be possible with IRC running in byobu...
Changed in byobu: | |
status: | Fix Committed → Fix Released |
Changed in byobu (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Wishlist |
Changed in byobu: | |
status: | Fix Committed → Fix Released |
Thanks for the question. I have converted this to a bug report.
I think it would be a good idea to name byobu sessions accordingly, and only select against byobu-named sessions. This would allow byobu to run beside screen a little cleaner. Committing a fix to this effect now.