RE: [bdbxml] history and line editing in dbxml shell.

On Thu, 2005-07-14 at 21:29 -0400, Ron Cohen wrote:
> Bas,
>  
> >To get the command back, the only way I can do this is to use
> copy/paste, rather than using the "cursor up/down" buttons to quickly
> step >through a list of previous executed commands. If I then paste a
> command on the prompt line, I can not use the "cursor left/right"
> buttons to 
> >position the cursor somewhere on that line and make a change. I can
> only use the backspace button removing everything up to the point 
> >where I want to make a change. This all is a bit painful.
> 
>  
> Here is one suggestion and that is to use script files.
>  
> If you want to save what you typed, I'd recommend creating a script
> file.  You keep your 
> 
> favorite editor open to type in the script and then run it.  If you
> have any errors,
> then you can edit the file and run the script again.
>  
> Here is a simple script I created:
>  
> opencontainer test.dbxml
> putdocument adocument {<phonebook>
> <name>
>  <first>Ron</first>
>  <last>Cohen</last>
> </name>
> </phonebook> }
>  
> The file is named ron.script. 
>  
> dbxml> run ron.script
> Document added, name = adocument
>  
> Again if I had any errors I would edit the script above. 
>  
> 
> 

Thanks Ron, yes that will make life a little bit easier. I assume I can
run

$ dbxml -s ron.script

from my bash command line.

Still it would be nice to have the dbxml shell more consistent with
other shells. Compare it to a FTP utility for instance. If you quickly
want to download a file, you are not going to first write a FTP-script.
You just enter the ftp shell and enter the commands as you need them and
using cursor keys if you need a (similar) previous command. It would be
nice if the dbxml shell would behave in similar fashion.

Don't get me wrong, I am not knocking the dbxml shell utility, as said
it is great, but with a little bit more user friendliness it would be
perfect.

Thanks for your prompt response.

Regards,

Bas.