These 2 keymappings from my last post are apparently for xved.
For ved (which I much prefer) I use:
vedsetkey('\^[Ow', vedtextleft);
vedsetkey('\^[Oq', vedtextright);
to use the <home> and <end> keys on the numeric pad of the pc keyboard.
$usepop/pop/help/vedkeys lists the key names and action-descriptions.
eg: ....
^P Move up one line CHARUP
^N Move down one line CHARDOWN
^B Move left one character CHARLEFT
^H Move left one character CHARLEFT
^F Move right one character CHARRIGHT
In my opinion ved sufferes from feature bloat. I guess it's difficult to resist.
But the new user CAN customise a minimum set of keys for 'familiarity'.
---------------
> > It would have been good if you listed the size.
>
> The current size is 2'815'730 bytes. As I said, my goal was to make it
> fit on two 1.44Mb floppies.
That makes it very do-able for potential new users to 'first just taste'.
> > ...Once the new user has it installed and the keys 'tuned per
> > personal preference', the progress depends on the tutorials. And
> > especially the route which one navigates through the tutorial set.
>
> You have to remember that these materials were developed in a
> teaching/learning environment where the students did their work in a
> common "terminal room", where they could talk to each other and to
> experienced users who were available most of the time. That put less of
> a premium on spelling everything out to the last detail. There will
> have to be considerable adaptation for a setup in which people learn
> essentially on their own, getting help from newsgroups like this. I
> would hope that a big contribution would come from people like yourself,
> who have learned that way, writing the materials that they wish they had
> had when they started. (I realise there will have to be some initial
> delay :-) )
>
> On the other hand, the users for whom the materials were originally
> intended had often quite literally never been in the presence of a
> computer terminal before. It ought to simplify things somewhat to be
> able to assume a bit more sophistication than that in today's new user.
It's good to know the history, to plan a strategy for greater usability
with the new conditions: internet and remote collaboration.
Vesa A Norrman wrote:
> (1) How do I make ved start in full window mode instead of half
> window mode?
No, let it start as is. Then:
<esc> w = zoom/toggle between 2 halves or 1 whole.
Having 2 windows is often very usefull.
With the often used immediate compile/run ability, you need to see your
output in it's own separate window.
<esc> x toggles the cursor to the alternate window.
Besides having 2 poplog active windows open, you will want
at least one virtual-terminal for your notes.
As you collect several files of notes, you will want more VTs, especially
as the hypertext 'branches out'.
Sometimes even a second poplog terminal is usefull.
You just cut-and-paste between VTs. Or are you using xved ?
---------------
Stephen Isard wrote:
> zcat is just gunzip -c, which doesn't delete the original file
>....ztf file.tar.gz
> will send the directory listing of the tar achive to standard output,
> and you can divert it to a file in the usual way with ">".
Yes, but it lists without size, date, permission.
A file with a full listing of the original download, has great diagnostic value.
This format:
drwxr-xr-x axs/90 0 2000-02-21 12:44:56 linuxterm/
-rw-r--r-- axs/90 582 2000-02-21 12:11:40 linuxterm/vedlinux.p
-rw-r--r-- axs/90 515 2000-02-21 12:40:51 linuxterm/vedlinuxkeys.p
-rw-r--r-- axs/90 480 2000-02-21 12:14:25 linuxterm/vedlinuxscreen.p
-rw-r--r-- axs/90 1567 2000-02-21 12:44:47 linuxterm/README
I only know how to get this format from *.tar.
And the way I get from *.tar.gz to *.tar deletes the *.tar.gz (hence must
first backup).
Clearly multi-stage piping can extract the full-format-directory from the
*.tar.gz, to a file, without deliting *.tar.gz.
I haven't yet found how to do it with one command.
Chris Glur.
|