Re: Are we ready for a release ?



tpgww@xxxxxxxxxxx wrote:

On Fri, 17 Oct 2008 14:17:01 -0500
Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:


I think it looks great and is ready for a release.


Almost. Waiting on svn permission for our new(ish) polish translator.


Great.



That or we could talk about other things...
Colored output - egrep can produce colored output (uses ANSI escape sequences that xterm understands.) 
Unlikely. Checking each byte of printed content is slow.
I know - I wish gtk would have something that translated ANSI sequences (for color at least.)
Button/command to lock the command pane to the first pane instead of the active pane 
The active pane is (very nearly) always the same as the filesystem CWD. In the 
absence of a full path, that's where commands would expect to be.
What I've found to be quick is to set the left pane to the main directory and run commands from the command line. Then if there's a problem (error, etc.), use the second pane to navigate to the proper directory to edit a file or so. If I could lock the command line to the left pane, then I could fix the problem and rerun the command without having to switch back to pane1. 
I guess I could add to F10='redo command' the 'pane.activate 1' action.

Ability to use !$, !:1, in a command.
Prepend ">" to send command to external shell 

What I'm trying to do is something like:

% some command file1
% another command !$

Which doesn't work as the shell doesn't know what the prior command was.
Lastly, do you let GTK code control the selection of text when double clicking button 1? 
(If output.activate is not used?)



--
   Soli Deo Gloria
   Adam Krolnik
   Director of Design Verification
   VeriSilicon Inc.
   Plano TX. 75074
   Co-author "Assertion-Based Design", "Creating Assertion-Based IP"

Other related posts: