> >And the most basic/essential operation: 'find a text string in ved'
> >I don't see how to do !!
Steve wrote:
> ENTER /<string>
OK, like in unix's man. But idealy nothing should be 'remembered'.
> >Please just, tell how/if I can simply just 'include' the sources
> >in the various <structures>.p, in do_ved_add.
> If you don't want all the little ved_add_XXX.p files lying around,
> I suggest you just edit your vedinit.p as follows (vedinit.p is
> loaded when Ved runs for the first time).
>
> 1. Insert the definition of do_ved_add, which is a trivial helper
> routine, at the head of vedinit.p.
>
> 2. Include the contents of all the ved_add_XXX.p files one after
> the other below that. As I remember, these are all standalone
> so the order doesn't matter.
>
> 3. Add a "vedset keys" statement to bind these to sensible
> shortcuts that you find mnemonic. You can follow the pattern
> I started earlier.
>
> Here's a uuencoded, gzip'd file that puts these steps together.
> Extract with uudecode, decompress with gzip -d, you'll get
> ved_add.p which can be included into your $poplib/vedinit.p
> file.
Yes it all runs OK, including indenting the structures !
I'm a bit taken-aback. Need to get my breath before I start using it.
What I additionally had in mind but didn't want to mention -- to
avoid extra confusion, is that one can easily edit new 'templates'
and use them for other languages. Then this becomes a poplog
based tool for your other language(s) - in another linux terminal(s).
Although I 'got stuck' after the 'river' tutorial, it was obvious to
me that poplog could hack-up such tools easier than any other
language that I could dream of.
Thanks,
-- Chris Glur.
|