You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 
Author Message
25 new of 224 responses total.
goose
response 200 of 224: Mark Unseen   Jun 17 15:26 UTC 2003

Thanks David, I thought I had set it to accept v1 connections but I'll double
check.

I know about /#197, but r 4.197 is more efficient and shoudl be trivial to
implement.
davel
response 201 of 224: Mark Unseen   Jun 18 14:33 UTC 2003

Even if you're not using a pager, you can do
r 4 nor      ... and then
197
janc
response 202 of 224: Mark Unseen   Jun 19 03:16 UTC 2003

I've put "r 4.197" on my TODO list for Fronttalk ... which doesn't mean that
it will get implemented soon.  The main problem with it is that that syntax
is kind of tricky to merge into the general item selector syntax.  Do we also
allow:
   r 4.197,7.10,15.0  (that's clear enough)
   r 1-3.197          (what does that mean?)
   r 4.197-11.18      (uh)
   r 4.197-198        (is that a response range or a bad dream?)
   r 4.197 new        (does that show new responses after 197?)
   r 4.197 nor        (could differ from 'r 4 nor' in setting current resp)
Does this make any sense on any of the other commands that take item ranges?
Browse, forget?  Probably not.  Fix?  Perhaps.
davel
response 203 of 224: Mark Unseen   Jun 19 12:12 UTC 2003

There's also the issue of whether "r 4.197" means to read only that response,
or to read starting with that response.  (Personally, I'd argue for "only",
with the syntax "r 4.197-" to mean "starting with".  But this just expands
the issues Jan raised.  And note that in Picospan, at the respond-or-pass
prompt, "197" means "starting with 197"; you must say "only 197" to read only
that one.)
remmers
response 204 of 224: Mark Unseen   Jun 19 15:07 UTC 2003

Nonsense.  The proper syntax for "starting with 197" should be "197+".  :)
janc
response 205 of 224: Mark Unseen   Jun 19 17:20 UTC 2003

Isn't it amazing how corrosive a simple little idea gets?

Luckily (for me), the user interface portion of fronttalk is just a perl
program.  Anyone who wants a particular syntax, need only make a copy and
modify it to fit their tastes.
davel
response 206 of 224: Mark Unseen   Jun 20 13:10 UTC 2003

So "197-" should cause responses to be displayed in reverse order, John?
8-{)]
jor
response 207 of 224: Mark Unseen   Jun 20 13:11 UTC 2003

        you laugh, but it makes sense to me
janc
response 208 of 224: Mark Unseen   Jun 20 19:33 UTC 2003

Actually, I think that's a current front talk bug.  197- gets interpreted as
197-0 and show displays thinsg in reverse order.
remmers
response 209 of 224: Mark Unseen   Jun 21 11:54 UTC 2003

Are you sure that's a bug and not a feature?
jmsaul
response 210 of 224: Mark Unseen   Jun 21 12:28 UTC 2003

If your password expires, and you use SSH to log in to Grex, you don't get
prompted to choose a new password -- you just get told that you've failed
authentication.  Not ideal.

(Personally, I don't think Grex is important enough that it should be
 forcing regular password changes anyway.  I'm aware that this is a minority
 opinion around here, though.)
janc
response 211 of 224: Mark Unseen   Jun 21 13:50 UTC 2003

(I agree - actually staff is exempt from the regular password changes thing,
which is probably backwards.)
jmsaul
response 212 of 224: Mark Unseen   Jun 21 14:05 UTC 2003

s/probably backwards/completely moronic/p

Can you turn password changes off for the rest of us?  Or do we need a
referendum?  ;-)
tod
response 213 of 224: Mark Unseen   Jun 21 21:53 UTC 2003

This response has been erased.

jmsaul
response 214 of 224: Mark Unseen   Jun 22 06:48 UTC 2003

If you like changing your password regularly, nobody's stopping you.
tsty
response 215 of 224: Mark Unseen   Jun 22 07:22 UTC 2003

i thik int's been abot two years dicen there was a forced
passwd change ... abut the right amount of time.
  
s/dicen/since/  (zoundz!)
  
as infrequent as that, it's just a good systme policy, imo.
tod
response 216 of 224: Mark Unseen   Jun 22 07:51 UTC 2003

This response has been erased.

russ
response 217 of 224: Mark Unseen   Jun 22 13:11 UTC 2003

It took 3 minutes to get a login prompt this morning.
jmsaul
response 218 of 224: Mark Unseen   Jun 22 15:07 UTC 2003

Re #215:  If it's such a good policy, why isn't it applied to the staff?

Re #216:  What's the problem?
cross
response 219 of 224: Mark Unseen   Jun 22 15:31 UTC 2003

This response has been erased.

tpryan
response 220 of 224: Mark Unseen   Jun 22 16:06 UTC 2003

        Aren't we gonna be on NewGrex is less than a month?
cross
response 221 of 224: Mark Unseen   Jun 22 16:18 UTC 2003

This response has been erased.

gull
response 222 of 224: Mark Unseen   Jun 23 14:47 UTC 2003

I've noticed that the "View Responses" box in Backtalk doesn't work like
I'd expect.  For example, if I enter something like "200-202" and click
the arrow, I get a lot more than just those three responses.
gelinas
response 223 of 224: Mark Unseen   Jun 24 02:31 UTC 2003

Which interface, gull?  I don't know which one I used (it had a light blue
background), but its "View Responses" box worked for me.  I tested one, two,
three, and 20-plus responses at a time (the last used a closing number larger
than the number of responses in the item).
gull
response 224 of 224: Mark Unseen   Jun 24 13:52 UTC 2003

I'm using the one with the light yellow background and the green
buttons. Pistachio, I think?
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss