db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1447) add command line history to ij
Date Fri, 30 Jun 2006 13:02:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1447?page=comments#action_12418637 ] 

John H. Embretsen commented on DERBY-1447:

This would be a nice feature to add to ij. However...

I know that emacs users already have a work-around for this, and I consider using JLine to
be another work-around, being an extension/wrapper around Derby/ij. I think it would be better
to have some command line history functionality in ij itself, than to include an external
jar in the derby repository. IMHO, we should rather document this work-around somewhere (wiki
/ manuals), along with the emacs work-around and possibly others. 

I know that implementing this functionality in ij requires some more work, but just adding
a command line history should be easier than implementing all the features provided by JLine
(such as tab completion, line editing, custom keybindings, character masking), while adding
great value to ij.

Besides, JLine is not 100% Java...

> add command line history to ij
> ------------------------------
>          Key: DERBY-1447
>          URL: http://issues.apache.org/jira/browse/DERBY-1447
>      Project: Derby
>         Type: Improvement

>   Components: Tools
>     Reporter: Gary Orser
>     Priority: Minor
>  Attachments: jline-0_9_5.jar, jline.diff
> Using the command line tool 
> org.apache.derby.tools.ij
> is user unfriendly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message