Change title of a thread after it is created Post: 303014739

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Change Console Title

Hello. I am trying to figure out how to change the title of my console window. I don't need it to dynamically change with my current directory. I just want to be able to change the name of it, so when I minimize the window I can see which windows are for what purpose. I've tried using the...

2. Solaris

Change Terminal Title

Is it possible to change the title of a Terminal window on Solaris? For example, for a MS Windows command window, one can simply type "title NameofWindow" to change the title for a command window. I was looking for similar functionality for terminal windows. Thanks.

3. UNIX for Advanced & Expert Users

Change putty title window?

Is it possible to change the putty window title from a Unix command line?

4. AIX

How to change cronjob title?

Once I type "mail" command, I got to see the mail like below: > 1 daemon Thu Aug 12 17:31 31/938 "Output from cron job " My question is, how to do change the default title "Output from cron job " to be more customized title? Thanks.

5. UNIX for Dummies Questions & Answers

Change putty title name

Hello all, I have a not so unix question for you guys(or maybe it is). I use PUTTY to login to serverA (my putty title shows as serverA.domainname.com) Now from ServerA i do ssh user@ServerB (i have ssh public private key setup)... now my question is when i do ssh and logon to...

LEARN ABOUT OSX

svk::command::info

SVK::Command::Info(3)					User Contributed Perl Documentation				     SVK::Command::Info(3)

NAME

       SVK::Command::Info - Display information about a file or directory

SYNOPSIS

	info [PATH | DEPOTPATH]...

OPTIONS

	-R [--recursive]       : descend recursively

DESCRIPTION

       For example, here's the way to display the info of a checkout path:

	% svk info ~/dev/svk
	Checkout Path: /Users/gugod/dev/svk
	Depot Path: //svk/local
	Revision: 447
	Last Changed Rev.: 447
	Last Changed Date: 2006-11-28
	Copied From: /svk/trunk, Rev. 434
	Merged From: /svk/trunk, Rev. 445

       You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy
       and merge source for this depot path.

       The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not
       referring to a checkout path.

       Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path
       (//svk/local).  The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from
       the revision 445 of //svk/trunk.  Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at
       revision 434.

       So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge.

       If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this
       command will look like this:

	% svk info //svk/trunk
	Depot Path: //svk/trunk
	Revision: 447
	Last Changed Rev.: 445
	Mirrored From: svn://svn.clkao.org/svk, Rev. 1744

       So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744.

perl v5.10.0							    2008-08-04						     SVK::Command::Info(3)