[277] in Tooltime
Re: Scopus 1.0b6 testing comments
daemon@ATHENA.MIT.EDU (Rob Smyser)
Fri Oct 4 12:23:22 1996
To: bdrosen@MIT.EDU
Cc: tooltime@MIT.EDU, tooltime-bugs@MIT.EDU
Date: Fri, 04 Oct 1996 12:22:47 EDT
From: Rob Smyser <smyser@MIT.EDU>
{dear me, what to use an indenting delimiter.... ah -- '
' |> 4) Problems with searching (Productivity loss)
' ...
'
' |>
' |> c) With History and Summary Find, putting an carriage return at
' |> the end of the search string and clicking on Find results in
' |> search failure. This is easy to do, and mysterious to
' |> figure out why search failed.
'
' I am not sure why this is a problem. The search is on the search
' string. If the search string contains a carriage return, then the search
' is going to look for a carriage return. Would you rather have the search
' ignore all carriage returns (or other commonly used non alphanumeric
' characters) ?
'
I'd say the user is expecting the equivalent of a C compiler ignoring
whitespace. That would include non-printing space-like characters but retain
numbers and perhaps punctuation.
'
'
' I would like to add a "bug report" of my own at this point. When
' I started up the Solaris client, I noticed that the helpdesk screen
' still has the overlapping fields that have been reported as well. I
' realize that the unix client has the least priority of the three
' clients, However I think that completely ignoring its problems is
' wrong. Are you really sure that nobody is going to want to use it?
I would like to be able to use it myself, perhaps in a cluster somewhere
if the mood suits me.
We need to know what to put on the command-line of start_scopus to be able to
specify a font, such as fixed, which would be readable on unix using the
settings developed for DOS and Mac. I don't think anyone has pursued
the equivalent of Edit...Preferences...Fonts on the unix side.
Does the standard X-style "-font fixed" somewhere have the right effect?
Brett might have the answer faster than I could by experimenting here...
- Rob
