Opened 4 years ago

Last modified 4 years ago

#290 new enhancement

:suspend is dubious and should be documented as such

Reported by: adehnert@mit.edu Owned by:
Priority: major Milestone:
Component: ui Keywords:
Cc:

Description

:suspend is a little dubious, because if you leave it suspended for too long your connections to servers might break and if barnowl's parent isn't a shell (eg, directly run from screen) it can't(?) be resumed. Also, most people run barnowl in screen anyway, so creating a new window is easy, and certain commands can be run reasonably with :exec or :pexec instead of suspending.

:help suspend currently says (basically) just "suspend - suspend BarnOwl" -- perhaps it should document this as a bad idea and suggest some of the alternatives.

Change History (4)

comment:1 Changed 4 years ago by adehnert@mit.edu

^Z's message should perhaps also be modified to reference the new help text / include a warning.

Last edited 4 years ago by adehnert@mit.edu (previous) (diff)

comment:2 Changed 4 years ago by kchen@mit.edu

This seems like a reasonable idea, but I just wanted to add some background:

Ctrl-Z used to suspend barnowl, but that was disabled and :suspend added because of the reasons specified in the ticket. (But I think screen usage was less common at the time.)

comment:3 in reply to: ↑ description ; follow-up: Changed 4 years ago by kchen@mit.edu

Replying to adehnert@…:

if barnowl's parent isn't a shell (eg, directly run from screen) it can't(?) be resumed.

screen will resume barnowl automatically.

comment:4 in reply to: ↑ 3 Changed 4 years ago by kchen@mit.edu

Replying to kchen@…:

Replying to adehnert@…:

if barnowl's parent isn't a shell (eg, directly run from screen) it can't(?) be resumed.

screen will resume barnowl automatically.

This seems to only happen once -- the first time, screen says "Child has been stopped, restarting." But after the first time, it no longer does so. "kill -CONT pid" will resume, though.

Last edited 4 years ago by kchen@mit.edu (previous) (diff)
Note: See TracTickets for help on using tickets.