[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Feb 11 19:18:50 2001 
Subject:ved key-mapping ? 
From:cglur 
Volume-ID:1010211.02 

My xved operates OK.
And under X-windows, ved gives a 'split screen',
but keys are wrongly mapped.

Out of X-windows, ved has bad keys and bad layout.
Advice please.
-------------
poplog system installation and familiarisation via inet download is
a multistep process, with many stages that can fail.

More importantly is that failure is not detected due to the lack of
'test points'.

This is NOT a plug-n-play system.
Greatly increased numbers of test points need to be provided.

The AI approach of: we don't know all possibilities that could cause 
errors, but we provide heuristics, to greatly increase the chance of
success; is appropriate.

Here are some novel bugs, which I really didn't want to meet:
1. Unix, MSDOS and my 'proper' OS (oberon) use different line
terminator combinations (CR,CR/LF,LF).
  Many editors provide a visual line break, for all cases without indicating
any difference.
The first line of #!/bin/csh   or  #!/bin/bash   scripts  fail (with out
indicating where the error lies) when the (invisible) line terminator
is not ) 0Dhex.    
2. Linux documentation refers to 'enviroment variables',
eg. $PATH, $EDITOR. These can be set and exported by a script; to be
confirmed on exit from the script.
$poplocal ... are confirmed as set inside the script, but not after exit.

Poplog's offer of multi:
  platforms, http or ftp, csh or bash, ved or xved ....has great advantages,
but massively adds to the 'decision load' of the first time installer.

The complications of Unix's multi-user/tasking further adds to the
points of possible error.

One (of several needed) test points would be the ability to 
read/confirm the current set of enviroment variables, needed
by poplog.

The 'normal' enviroment variables are seen by: printenv
or save to file for later viewing by: printenv >  <fileName>.

Thanks,
  Chris Glur.