|
|
| Author |
Message |
| 25 new of 263 responses total. |
mcnally
|
|
response 50 of 263:
| 
Jan 9 00:58 UTC 1998 |
either surround the name with quotes, which will cause the shell to
treat it as one argument with a space in it rather than two arguments
seperated by a space, or use a backslash to cancel out the special
meaning that the space character has to the shell.. so:
rm "delete me"
rm delete\ me
|
dang
|
|
response 51 of 263:
|
Jan 9 03:08 UTC 1998 |
And if it has a quote in it, you need to escape (meaning precede with a
backslash) the qutoe too. so:
rm thisisaaquote\"
and if there's a backslash, you need to escape the backslash, as in:
rm backslash\\
Fun, isn't it?
|
mcnally
|
|
response 52 of 263:
|
Jan 9 06:37 UTC 1998 |
It doesn't get really complicated until you start mixing things.
Actually, I'm going to amend my recommendation to favor single quotes
( ' ) instead of double quotes ( " )
Single quotes are preferable in some of the more complicated cases
because they signify that the shell should not do any further processing
of what's contained within. Things Can Happen to stuff inside double
quotes..
|
valerie
|
|
response 53 of 263:
|
Jan 9 07:00 UTC 1998 |
This response has been erased.
|
davel
|
|
response 54 of 263:
|
Jan 9 11:16 UTC 1998 |
(s/yes/y and s/no/n ?)
|
valerie
|
|
response 55 of 263:
|
Jan 9 15:41 UTC 1998 |
This response has been erased.
|
senna
|
|
response 56 of 263:
|
Jan 10 18:15 UTC 1998 |
Wow, this sounds like it could be in garage
|
davel
|
|
response 57 of 263:
|
Jan 14 02:09 UTC 1998 |
I had a problem with the idle zapper. I was in picospan, & I did a "find"
looking for something in a conference. 15 minutes later, it hadn't found
anything, & the idle zapper told me I'd been idle for 15 minutes & had 5
minutes to mend my ways. I typed some newlines (thinking that would be
activity), but after 5 more minutes in which find didn't find anything I was
unceremoniously dumped.
(Maybe I should call this a picospan problem, instead. I logged back
in, and did a grep on the conference files instead. It found what I
was looking for and a lot more within about a minute ...)
|
cmcgee
|
|
response 58 of 263:
|
Jan 14 05:10 UTC 1998 |
I'd like to enter my vote for putting the countdown back on the queue. I
dialed in on 4931, and was told I'd have to wait a bit for a connection. I'd
really rather have the queue countdown.
|
mdw
|
|
response 59 of 263:
|
Jan 14 18:06 UTC 1998 |
The delay you see there has nothing to do with the queue; it involves
tcp wrapper overhead and happens before the queue on remote telnet
sessions as well.
|
valerie
|
|
response 60 of 263:
|
Jan 14 18:36 UTC 1998 |
This response has been erased.
|
cmcgee
|
|
response 61 of 263:
|
Jan 14 19:31 UTC 1998 |
Ok, thanks Marcus and Val. I thought it was just a polite way to tell me I
was in the telnet queue without scaring me off with a big number.
|
wolfg676
|
|
response 62 of 263:
|
Jan 15 08:57 UTC 1998 |
Well, this isn't really a problem, so I'll call it an "un-problem". No trouble
with the queue here, thw "waitng..." screen came up with a count of 8, then
counted down, skipping 6, 4, and 2. Guess it's not liking even numbers today.
this is the first time I've logged in via telnet from my dial-up ISP, and Grex
is blasting right along! The ISDN link is cool!
|
valerie
|
|
response 63 of 263:
|
Jan 16 00:45 UTC 1998 |
This response has been erased.
|
valerie
|
|
response 64 of 263:
|
Jan 16 08:40 UTC 1998 |
This response has been erased.
|
mdw
|
|
response 65 of 263:
|
Jan 16 17:24 UTC 1998 |
telnetd checks every 5 seconds. Still, it is possible for the queue to
occasionally move pretty fast.
|
gibson
|
|
response 66 of 263:
|
Jan 18 08:11 UTC 1998 |
The last few days i've been getting sections of text in inverse. Any
ideas why?
|
terry
|
|
response 67 of 263:
|
Jan 18 12:02 UTC 1998 |
Are you using vt100 or ansi emulation?
Anyone know how you turn off the pager in picospan?
|
remmers
|
|
response 68 of 263:
|
Jan 18 22:41 UTC 1998 |
undefine pager
|
valerie
|
|
response 69 of 263:
|
Jan 19 05:31 UTC 1998 |
This response has been erased.
|
senna
|
|
response 70 of 263:
|
Jan 19 05:35 UTC 1998 |
Grex seems very, very slow to me. I believe it is due to the processor being
bogged down, as this has happened before.
Ever since the modems made the permanent jump to the terminal server, I've
had a serious problem with random pieces of text being deleted before reaching
my screen. This is very, very, annoying. Any idea what's going on?
|
terry
|
|
response 71 of 263:
|
Jan 19 07:23 UTC 1998 |
I want to get rid of the pauses.
|
scott
|
|
response 72 of 263:
|
Jan 19 12:07 UTC 1998 |
Re: 70: Sounds like a flow control problem. Do you have flow control turned
on on your PC's terminal software?
|
janc
|
|
response 73 of 263:
|
Jan 19 15:03 UTC 1998 |
I haven't seen chunks of data getting lost on the dial-in lines, but they
often seem quite laggy and seem to hang for minutes without an echo. Telnet
connections seem smoother than dial-up connections right now (though 14.4 is
nice).
|
dpc
|
|
response 74 of 263:
|
Jan 19 16:18 UTC 1998 |
I'm also getting a huge lag on the local dialins.
|
