|
Grex > Helpers > #137: Grex System Announcements - Winter 2004/2005 |  |
|
| Author |
Message |
| 25 new of 219 responses total. |
mooncat
|
|
response 167 of 219:
| 
Jan 26 16:34 UTC 2005 |
(Yeah, I noticed that too. ;) )
|
remmers
|
|
response 168 of 219:
|
Jan 26 16:44 UTC 2005 |
Re #164, #165: Can you point to some specific items where the '
problem occurs?
|
janc
|
|
response 169 of 219:
|
Jan 26 16:48 UTC 2005 |
resp:163 (keesan):
I would guess that your termcaps are set wrong. Do your arrow keys work
in anything else?
resp:164: (mooncat)
IE doesn't do ' ? Yuck. I guess I should take that out.
|
janc
|
|
response 170 of 219:
|
Jan 26 16:50 UTC 2005 |
Backtalk changes lots of symbols into responses into other things, like <
becomes < and & becomes &. The browsers change them back. The new
backtalk also changes ' into '. Evidently IE does not change it back.
|
janc
|
|
response 171 of 219:
|
Jan 26 17:14 UTC 2005 |
OK, I've fixed Backtalk to turn quotes into ' which IE apparantly does
understand.
|
remmers
|
|
response 172 of 219:
|
Jan 26 17:18 UTC 2005 |
Right - I suspected it was IE lameness. Seems to me I had a problem once
with IE not recognizing ''' despite every other modern browser doing
so.
|
janc
|
|
response 173 of 219:
|
Jan 26 17:19 UTC 2005 |
To state the obvious, IE is not a modern browser.
|
remmers
|
|
response 174 of 219:
|
Jan 26 17:20 UTC 2005 |
Yeah - scratch the word 'other' from my response #172.
|
keesan
|
|
response 175 of 219:
|
Jan 26 18:05 UTC 2005 |
My left arrow acts the same on my 101-key keyboard - BOTH left arrows.
Terminal type is vt100. I am telnetted from linux. Perhaps I should choose
linux instead.
|
tod
|
|
response 176 of 219:
|
Jan 26 18:15 UTC 2005 |
Have you tried vt52 or vt102 or vt220?
|
jep
|
|
response 177 of 219:
|
Jan 26 18:33 UTC 2005 |
The problem with the ' characters is fixed. Thanks, Jan!
Unfortunately I am limited to IE at work. As IE was one of the first
browsers with the capability to display XML, I am surprised it doesn't
handle the ' character entity. I wonder why it doesn't?
|
mooncat
|
|
response 178 of 219:
|
Jan 26 19:33 UTC 2005 |
All better now! Thanks!!
|
keesan
|
|
response 179 of 219:
|
Jan 26 19:49 UTC 2005 |
I think VT320 is the same as VT200 or VT102 with more features.
|
naftee
|
|
response 180 of 219:
|
Jan 26 19:53 UTC 2005 |
re 173 How so ?
|
janc
|
|
response 181 of 219:
|
Jan 26 20:39 UTC 2005 |
Sindi: In the old days "vt100" refered to an actual terminal you could put
on your desk rather than a protocol. People would use these extremely dumb
computers to connect to servers, and what codes were sent to the server when
they hit and arrow key were different depending on what make and model of
terminal you had. A DEC VT100 would send different codes than an IBM 3101
(I miss my trusty IBM 3101 - that thing could really hold a desk down).
Whatever software you use to connect to Grex (or under Unix, the terminal
window it runs in) pretends to be one or another of these fine old historical
monsters. Usually either VT100 if the programmers were lazy, or a much
extended version of VT100 called ANSI if they were more ambitious. So the
codes sent depend on the software on your computer, not on the actual keyboard
you are using. You mention Linux. Are you running xwindows? If so, you
probably want 'xterm'. If not, I guess probably 'ansi'.
However, I could be wrong about this. Maybe your TERM setting is fine. If
the arrow keys work for you in lynx, it is probably right.
Fronttalk doesn't actually do any of this logic itself. It uses a library
module called "readline" that is also used by many of the shells on Grex, like
tcsh. It would be very odd if your arrow keys worked in any of those, but
not in Fronttalk.
One thing just barely worth checking: Type "display readline" in fronttalk.
It should say that readline is turned on and mention "Gnu" (since we are using
the Gnu readline library).
|
remmers
|
|
response 182 of 219:
|
Jan 27 01:53 UTC 2005 |
Re #177: Microsoft decided to stop all development on IE a few years ago.
I guess they figured IE was so well entrenched as the leading browser that
they could rest on their laurels. Unfortunately that left their support
for XML and CSS in an incomplete state. Meanwhile, web standards have
been evolving and other browsers (Mozilla, Firefox, Opera) have been
keeping up, but not IE. Web designers are not pleased with IE these
days.
|
keesan
|
|
response 183 of 219:
|
Jan 27 13:37 UTC 2005 |
I have typed 'tset ansi' (which gave me the usual login messages for some
reason) and then ft and will now test arrow keys. I still get [D. My
terminal setting on my linux computer is 'linux'. Then I choose vt100 at grex
(I also tried linux here with no better results). Where do I type display
readline, at line start in fronttalk?
display readline
I just typed it and got nothing back. I am not using X.
Lynx and links work (offline anyway) as expected here.
|
naftee
|
|
response 184 of 219:
|
Jan 27 20:18 UTC 2005 |
re 182 Oh. Is this related to the fact that Microsoft stopped working on
their own virtual machine for Internet Explorer, and told peole to use Sun's
instead? This being for java.
|
cross
|
|
response 185 of 219:
|
Jan 27 20:43 UTC 2005 |
This response has been erased.
|
keesan
|
|
response 186 of 219:
|
Jan 28 00:52 UTC 2005 |
I am trying out ft with linux, vt100, or ansi terminal type, sshed or
telnetted from linux.
|
gull
|
|
response 187 of 219:
|
Jan 29 04:29 UTC 2005 |
Re resp:182: That's what happens when one company dominates the market
and manages to push everyone else out. Innovation comes to a halt.
Re resp:184: Not exactly. They lost a lawsuit with Sun, and aren't
allowed to distribute their VM anymore. I don't understand the
details, but I think it had to do with them creating an incompatible
version of Java by "embracing and extending" Sun's API.
|
naftee
|
|
response 188 of 219:
|
Jan 29 06:50 UTC 2005 |
http://java.sun.com/lawsuit/
heh. very interesting.
|
gelinas
|
|
response 189 of 219:
|
Jan 30 06:43 UTC 2005 |
OK. This time, I really think I've fixed the terminal server. I had to
reconfigure each port, individually.
Dial-in *should* be working again. Finally.
|
mary
|
|
response 190 of 219:
|
Jan 30 13:10 UTC 2005 |
Thanks, Joe. Must be frustrating.
|
keesan
|
|
response 191 of 219:
|
Jan 30 13:56 UTC 2005 |
I tried to dial in ten minutes ago and got three lines of garbage
followed by a hangup, so I telnetted but the load average was 89 with
ggg running 90 or more copies of the same process for the past 4 hours
(minutes?) or so. It was too slow to figure out if this is a dial-in
vandal.
|