|
|
| Author |
Message |
| 25 new of 227 responses total. |
keesan
|
|
response 25 of 227:
| 
Jan 6 21:12 UTC 2000 |
Pine almost invariably disconnects me while I am typing. Is it necessary to
have flow control? For some reason Jim removed it from Procomm. I also
get disconnected in bbs while typing.
|
mcnally
|
|
response 26 of 227:
|
Jan 6 23:21 UTC 2000 |
There's nothing in the Pine program that could possibly disconnect you
(unless you are specifically "exec"ing it from your login shell and it
is executing prematurely for some reason.)
Unless you're doing something odd *AND* there's a very strange problem
with Pine, then the odds are very good (100:1 at least) that the source
of your disconnect is not related to Pine at all..
|
other
|
|
response 27 of 227:
|
Jan 6 23:58 UTC 2000 |
6:58pm up 15 days, 3:52, 48 users, load average: 2.22, 1.70, 1.95
and seriously lagging...
|
mdw
|
|
response 28 of 227:
|
Jan 7 02:21 UTC 2000 |
There's something between UM & grex that is dropping packets. I don't
think it's anything near grex; it appears to be either inside mich.net
or possibly verio.net.
|
spooked
|
|
response 29 of 227:
|
Jan 7 03:00 UTC 2000 |
There was also a problem earlier with a mail bomb, which STeve fixed.
|
drew
|
|
response 30 of 227:
|
Jan 7 22:41 UTC 2000 |
The contents of my .cfonce are as follows:
# here is where you can put PicoSpan customization
set nosource
set edalways
define editor "gate"
# This line defines your pager. Delete it if you want your text to scroll
# continuously; then use control-S and control-Q to pause and resume
scrolling.
define pager "more"
# This line defines an extended Ok: prompt. Delete it for just Ok:
define prompt "\nOk: "
set autosave
Yet when I enter a response andtype ':' for the editor, I do *not* get the
gate program, but instead the old line editor. Why, and what should be done
to fix it? (I'm thinking of making it "amin -n gate", so I would now like this
to work.)
|
don
|
|
response 31 of 227:
|
Jan 8 01:02 UTC 2000 |
When you enter a response, you're already *in* gate. When you use :, it loads
up the default from (I think) your .profile, which would be the line editor.
|
janc
|
|
response 32 of 227:
|
Jan 8 03:07 UTC 2000 |
If you want to do "amin -n gate" change the line
define editor "gate"
to
define editor "amin -n gate"
If you want some editor other than the old line editor, say "pico",
then, do in your .login
setenv EDITOR "pico"
or if you have a .profile instead of a .login, do
EDITOR=pico; export EDITOR
|
drew
|
|
response 33 of 227:
|
Jan 8 03:39 UTC 2000 |
Okay, I see what's going on now. There seem to be two different back-wrap
capable editors. There's the one that you get immediately on entering "r" at
respond or pass, and there's another one with a bunch of options at the bottom
of the screen. What's the other editor called? (Pine uses it on grex.)
|
gull
|
|
response 34 of 227:
|
Jan 8 05:17 UTC 2000 |
The one Pine uses is called Pico. Pine uses it everywhere; it and Pine are
dependent on each other, much like QBASIC and EDIT are in MS-DOS.
|
krj
|
|
response 35 of 227:
|
Jan 8 06:07 UTC 2000 |
My participation file was destroyed because /a was full.
|
jazz
|
|
response 36 of 227:
|
Jan 8 15:07 UTC 2000 |
Discovered an unusual (bug?) bit about the way input to party is
handled. I can't think of a reason for it offhand, but it only affects very
fast typers. When a stream of characters is sent to party before a prompt
with :nofirstchar set, the first character consistently shows up as the
*fifth* character, and all of the first four characters are shifted forward
one place.
So, if you typed:
Testing!
You'd get:
estiTng!
|
don
|
|
response 37 of 227:
|
Jan 8 15:19 UTC 2000 |
That happens to me too, anytime there's a huge amount of lag and I type in
more than one line before it gets in.
|
pfv
|
|
response 38 of 227:
|
Jan 8 16:21 UTC 2000 |
11:20am up 16 days, 20:15, 54 users, load average: 2.57, 3.84, 3.86
User tty login@ idle JCPU PCPU what
nemoc ttyp7 31Dec99 8days 1 pine
"Idle-Reaper"?
|
don
|
|
response 39 of 227:
|
Jan 8 20:01 UTC 2000 |
Good question about that. I know that staff are immune from the idled, but
he's not in group 10. Interesting name, though. "Nemo omnae" is latin for
"nobody everyone".
|
keesan
|
|
response 40 of 227:
|
Jan 8 20:07 UTC 2000 |
Whenever I use Pine I get disconnectd while replying, oftening after hitting
backspace. I have not bothered attempting to answer e-mail for three days
now because it is impossible to stay connected. Could this be a problem with
this particular modem? Jim insists he has the same problems at Kiwanis and
on another modem at his house.
|
keesan
|
|
response 41 of 227:
|
Jan 8 20:10 UTC 2000 |
Did it again. I have tried to answer one person at least six times.
I cannot test out other modems right now because I am home with flu.
|
mcnally
|
|
response 42 of 227:
|
Jan 8 20:25 UTC 2000 |
1) you reported that it also happened to you in bbs.. were the symptoms
the same?
2) what mechanism do you use to invoke Pine? in other words, what is your
default login shell, and what do you do type to run pine?
3) what ASCII code does your "backspace" key send? backspace or delete?
(this is a configurable option in most communication software.)
4) have you changed your startup files to change the "susp" or "intr"
characters to anything non-standard?
|
pfv
|
|
response 43 of 227:
|
Jan 9 02:05 UTC 2000 |
9:04pm up 17 days, 5:58, 36 users, load average: 1.06, 1.05, 1.18
User tty login@ idle JCPU PCPU what
nemoc ttyp7 31Dec99 8days 1 pine
paladina ttypf Fri 9am 35:28 9 2 -bin/csh
|
don
|
|
response 44 of 227:
|
Jan 9 02:29 UTC 2000 |
At least the load average is down.
|
pfv
|
|
response 45 of 227:
|
Jan 9 02:37 UTC 2000 |
Yeah, that happens when most "people" are idling out in lynx or at
the shell <shrug>
|
don
|
|
response 46 of 227:
|
Jan 9 02:42 UTC 2000 |
Don't know if this is a "system problem" or just a nitpick, but the extract
program's errors don't go to stderr; they go to stdout.
|
don
|
|
response 47 of 227:
|
Jan 9 03:54 UTC 2000 |
It seems like just the "No item xxx" message goes to stdout. "Item file in
weird format" goes to stderr. Now to figure out what's wrong with the item
(it's somewhere in agora23)
|
cmcgee
|
|
response 48 of 227:
|
Jan 9 05:27 UTC 2000 |
I'm using pine on dial ins, several different ones, with several different
modems, and haven't had any trouble. I'm on 5-10 times a day.
|
mdw
|
|
response 49 of 227:
|
Jan 9 06:05 UTC 2000 |
Re #36 - there's a race condition in what party does - that's why party
didn't originally run in the mode that "nofirstchar" does. The race
condition is because there is no clean way to handle that first
character. I don't know what Jan does (and don't have time to look
tonight), but the obvious way is to use TIOCSTI to stuff the first
character back into the input buffer. This allows line/kill processing
to work right, but means that if you type "too fast", the next few
characters get into the queue before the first one gets back into the
queue, and they wind up out of order. The way to "fix" this is to use
something like the readline logic that bash uses (that is, do all the
line editting kill/erase processing in user mode), but that results in
another whole set of weirdnesses (on the 4/260 with 28.8K ppp, this
commonly resulted in complaints that line input didn't work, but only
for bash users.)
|
