For those of us with "fat fingers" this would be a blessing. I can not tell you how many times I fail to simply type v$istnance, v$instnace, v$instance! And often...and I mean often, I will run this little select in a spool and to eye-ball that I'm in the right place before rolling out some DDL... And about those debug sessions with your developers when you might select from dba_tab_privs, dba_sys_privs, and dba_role_privs, over, and over again to verify grants and privs... To bad it is only for Linux. Chris Marquez Oracle DBA HEYMONitor(tm) - heymonitor.com "Oracle Monitoring & Alerting Solution" -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Egor Starostin Sent: Tuesday, January 11, 2005 3:53 PM To: jkstill@xxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Yet another tool for Command_line_history for Linux DBA > Doing so on a SQL*Plus command line is less so. SQL statements are=20 > often more than one line, so it is necessary to up arrow to each line=20 > in succession, making sure it is the correct line, and then hit enter. > Do this for each line in the statement. Agree. I use rlwrap abilities to edit command line only for one-liners. For the others I use vim. > It is simply to easy in SQL*Plus to save the buffer to a file via the=20 > 'save' command, or simply 'get afiedt.buf' and 'ed'. What I like in rlwrap is it's ability for word completion. I.e. I created sql.dict file with sql keywords and words like dba_role_privs, etc. and run 'rlwrap -f sql.dict sqlplus'. After that, I type 'dba_ro' and press <tab> to complete it to dba_role_privs (the same way as in my vim editor). --=20 Egor http://www.oracledba.ru/orasrp/ Free Oracle Session Resource Profiler -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l