Is there a way, using trn, to rearrange my newsgroups so I get the "good"
ones first?  I've noted that when a new newsgroup arrives I can put it
whereever i like in the list...

12 responses total.

Next question is, can I switch between using rn and trn without fouling
up thr works or are they a "pick once" binary decision?

#1: I don't know about doing it within trn.  The easiest way to do this
is to edit your .newsrc file with a text editor.  If you can't use one
of the editors here on Grex, you can download the file and do it on
your home computer and then upload it and replace the current .newsrc
with it.

#2: trn is just a front end for rn, so you should be able to use them
interchangeably and not lose track of the articles you've read.

What he said.  I just keep them in alphabetical order and skip around
with the / and ? commands, but any editor can rearrange the groups in
your .newsrc file.

The "m" command, from the newsgroup selection prompt, will let you move
a newsgroup.  However, unless you only read a few groups, it's probably
easier to just edit your .newsrc as others have suggested.

Also, while it's true that you can switch back and forth between trn
and rn without problems, it's not really true to say that trn is a
"front end" to rn.  That implies that trn is actually running rn in the
background and talking to it behind the scenes, which isn't true.
It's more correct to say that trn is a superset of rn, and includes all
of the functionality of rn.  (And, if you look closely, you'll notice
that /usr/local/bin/rn is linked to /usr/local/bin/trn, so they're
really the same program.  You can make trn look like rn by running it
with the +X and +x flags, and similarly you can make rn look like trn
by running it with -X and -x.)

I have a question :) I got a call while in TRN and Got booted now i get
an error along the lines of You seem to have left a [t]rn prossece running
you can not have two proccesses running at once Goodbye.
and it discunnects how do i get around that? any ideas I would appreciate it
thanks ! :):):)

First, do a !ps command.  This will list all your current
processes that are active, the the process id numbers that
go with them, like so:

  PID TT STAT  TIME COMMAND
 1064 h2 S     0:00 vi /u/robh/cf.buffer
 1092 h2 Z     0:00 <defunct>
 1093 h2 S     0:00 sh -c ps
 1094 h2 R     0:00 ps

The PID is the number of the process.  Whichever one has the
command as trn, you can zap it with the kill comand, like this:

        kill -9 1093

That would send an uniterruptable kill signal (the -9) to that
process.  You could then load trn up again.

There's probably a way to resume that process so you don't
have to load trn up again, but I don't remember it.  >8(

Well unfortunatly that did not work i show no process as trn.
and the exact message i get is .............
 You seem to have left a trn running, process 0
 You may not have two copies of [t]rn running,   Goodby.

Okay, ya got me.  Anyone on the staff know what's going on here?

This response has been erased.

Well i will try anything i guess thasnk for your info :)

Yes, the .rnlock file is the culprit.  If it tells you a PID that is
obviously wrong (i.e., 0) or does not exist, you can just remove the
.rnlock file.  However, don't do this without trying to kill the
other trn process, since if you *do* manage to run two trn's at
the same time you can screw up your .newsrc.

Response not possible - You must register and login before posting.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss