Setting Window title and initial position Ubuntu Hardy Heron 8.04 with Compiz Fusion

Programmatically setting window titles, see forum entry.

Using Escape Sequences To Set Gnome Terminal Options

1. Edit the Terminal Profile (Edit - Profiles - Title and Command Tab), change dynamically-set title option to "replaces initial title".
2. Edit a script file or run on the command line and change the PROMPT_COMMAND line to

PROMPT_COMMAND='echo -ne "\033]0;"myWindowTitle"\007"'

where (in octal) \033 =>
0 => Ps = 0 (use string as a new icon name and title)
; => non-digit character
string => "myWindowTitle"
\007 => (non-printing character)

The escape sequence I've employed is :-

ESC ] Ps ND string NP OSC Mode
ND can be any non-digit Character (it's discarded)
NP can be any non-printing Character (it's discarded)
string can be any ASCII printable string (max 511 characters)
Ps = 0 -> use string as a new icon name and title
Ps = 1 -> use string is a new icon name only
Ps = 2 -> use string is a new title only
Ps = 46 -> use string as a new log file name

* The escape sequences are listed here



To specify launch position (placement)

System : Preferences : Advanced Desktop Effects Settings

Windows Management : Place Windows plugin

Fixed Window Placement tab

Windows with fixed positions

add new entry and position by window title

Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more