in reply to Help for managing your threads && Editing nodes offline

The first point has already been addressed by the /msg option in user settings.

WRT the second point: I'm using konqueror (on solaris), and it's kinda slow at keyboard reponse in form fields (I don't know why: it's fine on my linux box). So I frequently want to type stuff in a more responsive editor.

So, if I want to edit a node offline, I simply do so in an emacs window, and then cut'n'paste. It requires hopping between processes, but that should only be a problem for DOS users...

The assumption here, is that you're logging in to PM, reading stuff, and responding meaningfully. I don't see why that should be an issue, unless, of course, there's a reason you want to be able to post nodes without requiring any human intervention at all...

  • Comment on Re: Help for managing your threads && Editing nodes offline

Replies are listed 'Best First'.
Re: Re: Help for managing your threads && Editing nodes offline
by C-Keen (Monk) on Sep 30, 2001 at 18:26 UTC
    My intention with this is to keep online time as short as possible. I am using a dial up connection with little bandwith and I'd like to edit the node offline to keep the phone company from emptying my wallet :-)

    So long,
    C-Keen

[reply]

      Hmmm... I'm dubious. In that case, I'd suggest you want to attempt a larger approach to the problem:

      • Dial up.
      • log on.
      • Dispatch previously prepared nodes
      • Grab the list of newest nodes
      • Download said nodes
      • Update the newest nodes flag
      • Drop phone line
      • Edit responses off-line
      Presumably, this is mutch the same way you handle your email? Or, a more accurate analogy: usenet?

      While laudable, there are two problems with my above description:

      • it's going to consume disk space like nobody's business. That's assuming you keep a certain quantity of nodes, for context, which isn't essential, but I suspect it'll rapidly become a requirement, even if it doesn't start as one.
      • If you automate the procedure, then by the time your new nodes are posted (at, say, midnight your time), they may have been superceeded by on-line posters. Which isn't a problem <it>per se</it>, but may make your posts redundant

      Sorry, this probably sounds more negative that I mean it to be: I actually think this is an interesting idea. I just think it might turn out to be somewhat bigger than you originally expect...

      <bold>Update:</bold>Synchronously, blakem's just posted bivnn.cgi -- an alternate interface to newest nodes, which is probably worth taking a look at.

[reply]

In Section Perl Monks Discussion