|
Grex > Info > #2: Intro to using trn to read Usenet News |  |
|
| Author |
Message |
| 25 new of 78 responses total. |
cwb
|
|
response 50 of 78:
| 
Dec 20 00:36 UTC 1993 |
Curiouser and curiouser. It seems that Jove only acts funny when I use the
^-k edit local kill-file command. When I'm posting or replying via Email
from within TRN, all is well. And it appears to be only my arrow keys.
Control and escape sequences appear to function correctly.
Chris
|
kentn
|
|
response 51 of 78:
|
Dec 20 03:28 UTC 1993 |
Well then, don't use the ^-k local kill-file command...<grin>
(I hate it when stuff like this happens with one's favorite program).
|
remmers
|
|
response 52 of 78:
|
Dec 20 13:32 UTC 1993 |
This may be what's going on: The host computer can set the cursor keys
on your terminal to one of two possible modes, "cursor key mode" or
"application key mode". The mode affects what sequence of characters
is sent to the host when the key is struck. Applications like jove, vi
etc. consult your termcap to determine which mode to set for your
cursor keys on startup. If the special trn command that you mention is
messing up mode-setting for the cursor keys so that they're not
sending the sequences that jove expects, then jove won't respond
properly to them.
If that's actually the problem, it's probably a bug in trn and not
easily fixable, unfortunately.
|
tsty
|
|
response 53 of 78:
|
Dec 20 23:27 UTC 1993 |
Hmmm, a work-around, which I personally prefer and recommend for (now)
apparent reasons is to do all your file editing right from the shell
prompt. It's warm-n-fuzzy to have applications which handle "stuff"
right there and then, however, as described by remmers, not all the
bugs are worked out.
Further in that vein, various configurations of various systems have
some basic, stable applications/processes +from which+ all the other
stuff is built. As the building gets piled higher, some additions
develop little gotcha's. If you become proficient with some standard
version of something, it will work more often as a native process
rather than as an incorporated part of something larger.
So I stayed in ex as my standard editor long after having the
capability to move to vi . I can +always+ go back to ex if something
screws up in vi . Vi is getting more standard ( ?? is the standard ??)
and I don't anticipate +having+ to regress to ex , but I can.
So do your kill-file editing (and .newsrc for that matter) as a simple
file edit separate from any other overhead messiness.
Fwiw, I have tried Jove a few times just for kixx-n-grinzz and it seems
to be ok. I don't have all +my+ bugs worked out there yet, either.
Oh, btw, I REALLY like running vi on my Apple //e, Microsoft Word 5.x
and WordPerfect 4.x and Messy-DOS-edit notwithstanding.
|
bartlett
|
|
response 54 of 78:
|
Dec 30 21:23 UTC 1993 |
In my ongoing efforts to plumb the depths of my own silliness re: TRN, I
know the command to condemn threads to a local kill-file from the pager
level. Is there an analogous command from the thread-selector? the `K'
command that works at the pager level, does not do so at the thread-selector
level, and the help text is uninformative. One can edit the kill-fle
manually, but that's not what I want in this case.
Thanks in advance,
Chris the TRN gnome-wannabe.
|
vidar
|
|
response 55 of 78:
|
Apr 1 21:20 UTC 1994 |
|
drogers
|
|
response 56 of 78:
|
May 19 14:38 UTC 1994 |
Why does trn take so long to set up? I have waited from 5 to 20 minutes with
only one newsgroup listed in my .newsrc file. Maybe its because I'm fairly
new to grex, but I would like to know if there is a way to speed up the process
or not. Please help
|
robh
|
|
response 57 of 78:
|
May 19 21:01 UTC 1994 |
It's because we are getting our news from a remote server,
instead of keeping the articles here on Grex. Each article,
and the files trn needs to handle the articles, has to
go through our Internet link. There's nothing we can do about
it until we begin keeping the news on-line again.
My advice is to read a book while trn is loading. Seriously.
You wouldn't believe how much reading I've done that way.
|
mju
|
|
response 58 of 78:
|
May 19 22:01 UTC 1994 |
You'll be glad to know that, now that /grexold has been backed up, we
should have local Usenet news on-line within a week or so.
|
davel
|
|
response 59 of 78:
|
May 20 02:14 UTC 1994 |
This should make news itself a lot faster. What's the likely effect on
other internet operations? I presume that keeping our news files up to date
is likely to put a lot of stress on the link, but how much? Like all the
time?
|
mju
|
|
response 60 of 78:
|
May 20 03:35 UTC 1994 |
The news will be compressed prior to transit and will only have to be
sent once, so it shouldn't be too bad. We'll have to play it by
ear and see how bandwidth-intensive things are.
|
albaugh
|
|
response 61 of 78:
|
Jun 8 02:46 UTC 1994 |
OK, now that Grex has its own [t]rn news[groups] volume, some of the
newsgroups previously available thru "remote" trn are declared "bogus".
What I'd like to do is start with a .newsrc that has *every* valid newsgroup
in it (supported by Grex), and just unsubscribe and catch up as I see fit.
I tried "more /news/lib/active" and was told the file doesn't exist. So
either things have changed, or I don't have read permission on the file.
So how do I go about getting a copy of the master "all-newsgroups" .newsrc
file to work from?
|
kaplan
|
|
response 62 of 78:
|
Jun 8 07:43 UTC 1994 |
This response has been erased.
|
kaplan
|
|
response 63 of 78:
|
Jun 8 07:46 UTC 1994 |
try /var/spool/newsctl/active
|
mju
|
|
response 64 of 78:
|
Jun 8 14:59 UTC 1994 |
The active file has moved to /usr/netnews/ctl/active. However,
you shouldn't depend on that path, since it might change (and
only reflects the groups on the local server, anyway). To
get the active file from the default NNTP server, you can run
/usr/local/lib/trn/getactive active filename, where filename is
the name of the file to store the active file in.
|
mju
|
|
response 65 of 78:
|
Jun 8 15:00 UTC 1994 |
(Jeff slipped in. The /var/spool/newsctl path is where it really lives
for now, but not even the news software knows about that path, so
you should probably forget that it exists.)
|
chi1taxi
|
|
response 66 of 78:
|
Oct 5 01:49 UTC 1994 |
How do you post to Usenet News?
|
popcorn
|
|
response 67 of 78:
|
Oct 5 11:53 UTC 1994 |
This response has been erased.
|
davel
|
|
response 68 of 78:
|
Oct 5 12:04 UTC 1994 |
F includes the text of the article. If you don't include a *lot* more
original text than quoted text (which it recognizes by symbols in the
left margin, I think), it tells you so and aborts the whole process, not
giving you another chance to edit again. (This is really irritating;
context is important.)
|
tsty
|
|
response 69 of 78:
|
Oct 10 05:31 UTC 1994 |
First thing to do is to change all those left-margin characters. It's been
sooooooo long since Pnews has worked that I forget what the specific
character is - - however, the situation describedin #67 is accurate.
|
curby
|
|
response 70 of 78:
|
Oct 12 09:19 UTC 1994 |
If vi, the command to change the left margin character is:
[esc]:%s/^>//[ret]
|
srw
|
|
response 71 of 78:
|
Oct 13 06:44 UTC 1994 |
A new internet policy was passed by the membership which will permit
posting to usenet by verified users, regardless of membership.
This policy has not yet been implemented, and may take a while to achieve,
but we are committed to it nonetheless.
|
tsty
|
|
response 72 of 78:
|
Oct 13 09:26 UTC 1994 |
re #70 - if > is the default left-margin-character, yes
that is the correct substitution in either vi or ex (maybe the
ed and/or es editors, but I'm not that good in the
last two)
|
woody
|
|
response 73 of 78:
|
Oct 17 04:48 UTC 1994 |
I'm interested in searching the "Comp.sources" newsgroups for software, but I
don't know how to search and download from the Usenet. Can someone
gividiot-proof directions? Thanks!
|
popcorn
|
|
response 74 of 78:
|
Oct 19 12:23 UTC 1994 |
This response has been erased.
|