Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#50 closed enhancement

Make barnowl unsuspendable

Reported by: kchen@MIT.EDU Owned by: nelhage@mit.edu
Priority: minor Milestone:
Component: internals Keywords:
Cc:

Description

Users not infrequently suspend barnowl and then later find they lose subs. Pine seems to have a good model for this -- by default, you can't suspend pine, and if you enable the setting that lets you suspend pine, pine prints a warning message when you do suspend it. The alping warning message is:

Alpine suspended. Give the "fg" command to come back. Warning: Your IMAP connection will be closed if Alpine is suspended for more than 30 minutes

I don't know how accurate the 30 minute guideline is, but I've heard of people's (barn)owls losing subs before that long, I assume because the protocol is different.

Change History (4)

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

  • Resolution set to fixed
  • Status changed from new to closed

So far as I can tell, BarnOwl is no longer suspendable.

comment:2 Changed 11 years ago by adehnert@mit.edu

  • Resolution fixed deleted
  • Status changed from closed to reopened

Um, okay. So, I have a BarnOwl 1.2.1 that won't suspend. Nobody else seems to have unsuspendable BarnOwls of any form, rerunning 1.2.1 doesn't give me an unsuspendable BarnOwl, and my other BarnOwls are suspendable...

So... false alarm. Sorry, folks.

comment:3 Changed 11 years ago by nelhage@mit.edu

  • Status changed from reopened to closed

comment:4 Changed 11 years ago by nelhage@mit.edu

I believe this should be fixed on master. 'Z' prints a (hopefully)helpful error, and points at the ':suspend' command, which you can use to suspend if you really want.

Note: See TracTickets for help on using tickets.