If there's one thing that makes navigating a UNIX command line or tool console more efficient, it's tab completion. We've been improving Encounter's support for tab completion over the past few releases, and in 10.1 Encounter's dbGet command received tab completion support for the first time. Have a look at the screencast embedded below -- I think the way it's been implemented is really nice. And smarter than you might realize at first glance.
In its simplest sense tab completion works like this:
encounter 1> dbGet top.<tab>
...returns a list of all the attributes associated with the "top" cell in the design. If I provide a portion of an attribute it auto-completes and inserts a trailing ".":
encounter 2> dbGet top.i<tab>
encounter 2> dbGet top.insts.
If you continue on and ask it to complete when there are no remaining attributes associated with the last field, notice how <tab> inserts a trailing space:
encounter 3> dbGet top.insts.n<tab>
encounter 3> dbGet top.insts.name <-and inserts a trailing space
dbGet's tab completion is smart enough to recognize whether there are remaining fields available for traversal and either inserts a trailing "." -or- a trailing space which makes for very efficient command line navigation of the database.
It's also smart enough to return a varying list of attributes depnding on what you have selected. For example you'll see a different list of attributes revealed when you tab complete the selected keyword depending on what you currently have selected in the tool:
encounter 4> dbGet selected.<tab>
Similarly, if you task it with tab completing a variable. It's smart enough to examine the contents of the variable and tab complete accordingly:
encounter 5> set nets [dbGet top.nets.name *clk* -p]
encounter 6> dbGet $nets.<tab>
These examples are demonstrated in the screencast embedded below:
(if you have trouble viewing the video try this link instead)
Check it out next time you're using dbGet in 10.1 or newer releases. I hope you find it useful.