|
Grex > Info > #86: Chat, Talk, Write, etc. problem (messages off). | |
|
| Author |
Message |
scg
|
|
Chat, Talk, Write, etc. problem (messages off).
| 
Dec 26 04:30 UTC 1993 |
I've been having a problem where people who try to talk, write, or chat to me
are sometimes told that I am refusing messages. I have never typed "mesg n"
on grex, and when I type "mesg y" it only solves the problem temporarily.
Somebody was recently unable to "talk" to me even though I had already typed
"mesg y" once during that grex session. What can I do to correct the problem?
|
| 31 responses total. |
bartlett
|
|
response 1 of 31:
|
Dec 26 06:32 UTC 1993 |
You might look in your .profile or .cshrc file (whichever is appropriate)
for a mesg n line. When I shamelessly stole Remmers' .cshrc file, his had
that in it. Maybe yours does too. In which,, just remove that line.
|
remmers
|
|
response 2 of 31:
|
Dec 26 08:56 UTC 1993 |
I looked at those files, and that doesn't seem to be the problem.
I notice that you have a .screen directory. Do you use the "screen"
program regularly? Is it possible that the write refusals occur
when you're running "screen"?
|
scg
|
|
response 3 of 31:
|
Dec 26 17:58 UTC 1993 |
I use screen very occasionally, and I've haven't used it on the days in
question. I can't figure out what I've been doing differently when the
problem has occurred, and it seems almost random. I don't think putting
a mesg y line in the .login or .tcshrc would help any, since it seems to
happen sometimes even after I've already typed "mesg y" once.
|
tsty
|
|
response 4 of 31:
|
Dec 28 21:11 UTC 1993 |
The redundance my help, can't hure, stick 'em in both files.
|
popcorn
|
|
response 5 of 31:
|
Dec 30 04:45 UTC 1993 |
This response has been erased.
|
srw
|
|
response 6 of 31:
|
Dec 30 07:24 UTC 1993 |
I don't know much about scg's question, but Valerie, I think tcsh is
a lot more like csh than it is like sh. I'm no expert here,
but I thought "export" was a 'sh' thing, and not a feature of csh or tcsh.
|
mju
|
|
response 7 of 31:
|
Dec 30 12:23 UTC 1993 |
Steve is correct; tcsh is a superset of csh, and doesn't really
resemble sh at all. So it uses .login/.cshrc instead of .profile,
and setenv VAR value rather than VAR=value;export VAR.
|
srw
|
|
response 8 of 31:
|
Dec 30 17:17 UTC 1993 |
Actually, it uses .tcshrc rather than .cshrc, a minor quibble.
(or does it alos look for .cshrc? I never tried that.)
|
remmers
|
|
response 9 of 31:
|
Dec 31 00:22 UTC 1993 |
(Yes it does. tcsh is my login shell and it sources my .cshrc file.)
|
popcorn
|
|
response 10 of 31:
|
Dec 31 07:19 UTC 1993 |
This response has been erased.
|
srw
|
|
response 11 of 31:
|
Dec 31 07:50 UTC 1993 |
Re 9: Yeah after I entered the first line of #8 I realized it could
possibly be versatile in that respect. Cool.
|
scg
|
|
response 12 of 31:
|
Jan 6 04:05 UTC 1994 |
The .profile file is left over from when I was a new user and used the bbs
shell. I just never bothered to delete it when I switched shells. As for
the having "mesg y" in the .login file, I have tried typing it manually after
logging in sometimes and have still had the problem after that, although not
right away. There must have been something else that was doing it. It
doesn't seem to be a problem right now, and I'm hoping it might be something
that will go away with the new grex. Are we still running the same OS?
|
jared
|
|
response 13 of 31:
|
Jan 6 04:22 UTC 1994 |
create a file called .mesgn
|
scg
|
|
response 14 of 31:
|
Jan 6 04:34 UTC 1994 |
What would that do?
|
jared
|
|
response 15 of 31:
|
Jan 6 20:12 UTC 1994 |
login automatically will turn your messages off as you login.
Then someone can't get you before
the mesg n hits in your .login file
|
scg
|
|
response 16 of 31:
|
Jan 7 02:50 UTC 1994 |
So, if I put in a .mesgy file, it would automatically turn my messages on?
|
mju
|
|
response 17 of 31:
|
Jan 7 04:30 UTC 1994 |
I'm fairly sure that the .mesgn stuff was a feature of login on
M-Net. I don't think it has ever worked on Grex, but if it did
it certainly doesn't work on the new system.
|
scg
|
|
response 18 of 31:
|
Jan 18 21:20 UTC 1994 |
The problem actually doesn't seem to have gone away with the new system. It
seems to be related to either talk or trn. I'll do some more checking on that
and try to figure out which one of those it is.
|
popcorn
|
|
response 19 of 31:
|
Jan 18 23:43 UTC 1994 |
This response has been erased.
|
scg
|
|
response 20 of 31:
|
Jan 19 03:41 UTC 1994 |
I've done that, and it seems to be somehow related to both chat and talk. Is
there some way of correcting that (maybe somer rc file for them?)
|
popcorn
|
|
response 21 of 31:
|
Jan 22 14:01 UTC 1994 |
This response has been erased.
|
scg
|
|
response 22 of 31:
|
Jan 22 14:37 UTC 1994 |
My messages seem to turn off when I go into those programs.
|
popcorn
|
|
response 23 of 31:
|
Jan 22 19:41 UTC 1994 |
This response has been erased.
|
davel
|
|
response 24 of 31:
|
Jan 22 21:14 UTC 1994 |
What are the functional differences, Valerie? I would have expected mesg
to produce the same results whichever version was used - but this sounds
like the most promising idea I've heard on what Steve's problem could be.
Hm.
Especially when I try it & observe the following sequence:
> $ /usr/bin/mesg
> is n
> $ /usr/local/bin/mesg
> is y
This is certainly strange!
|