X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-Authority-Analysis: v=1.0 c=1 a=t3fcCvqvVmAA:10 a=8nJEP1OIZ-IA:10 a=w_pzkKWiAAAA:8 a=B_7_GmZEMu2M8WJM43YA:9 a=uBHZEvIF-lK1pXeC4rQA:7 a=kwAx9bc-YB2FLx85X0XHtZQyxp8A:4 a=wPNLvfGTeEIA:10 a=buB1NfXUTBUA:10 a=IfQ-iFkkCvMA:10
Message-ID: <4CA164CC.1060507@charter.net>
Date: Mon, 27 Sep 2010 23:45:16 -0400
From: SJ Wright <sjwright68 AT charter DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Cygwin User Mailing List <cygwin AT cygwin DOT com>
Subject: Re: Have idea for titlebar tweak -- need help with syntax
References: <4C9C6C3A DOT 9020805 AT charter DOT net> <4CA0E317 DOT 6050701 AT veritech DOT com>
In-Reply-To: <4CA0E317.6050701@veritech.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Lee Rothstein wrote:
>  On 9/24/2010 5:15 AM, SJ Wright wrote:
>> I'd like my terminal title bar to show my current working directory, 
>> the running process (with a fall-back to the active shell when idle) 
>> and the word "Cygwin."
>>
>> I have an old .bashrc file in which I collected code for the middle 
>> bit (running process), but putting the three together and making them 
>> work regardless of $TERM type is a challenge that's more than a 
>> little 'beyond my ken.' Nevertheless, as I think it would look great 
>> and be sufficiently informative at the same time, I'd like to pursue it.
>>
>> I haven't given up totally on rxvt: mintty has more than a few 
>> shortcomings imo, but I suspect a large part of that is that I'm not 
>> used to using an xterm variant outside of X or GNOME. Anyway, all of 
>> that is for another email.
>>
>> Where it meets at odd angles with this idea, is in that I suspect if 
>> I start with "tweaked" xterm settings that check out in rxvt, the 
>> strictly X syntax will work in mintty. In a sense, by going that 
>> route, I'll be 'ahead of the game' instead of 'trying to catch up.'
>>
>> Any help in this regard would be much appreciated.
>
> See attachment. Invoke in your profile as:
> . set_prompt.s
>
> ------------------------------------------------------------------------
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Save as an occasional change to my 'ls' command, or to distinguish a 
positive from a negative return in a script's stdout, I find color in 
terminals very tacky and distracting. And as I thought I made clear, I 
was quite satisfied with the prompt I had. It was only the title-bar I 
wanted to 'fancy up' .

To be fair, I'll go over the script attachment with a fine-tooth comb 
and see where or if there are other options pertaining to Title Bar 
customization. From what I've read so far, though, it appears that with 
bash I've backed the wrong horse, so far as getting the running process 
name  in the title bar goes. The name of the shell is called by /s, I 
found out. I still wonder why Bourne (or his 'successors') didn't think 
a blind 'ps  -head1' was worth setting an escape character for?

As you might be able to tell, I've looked into this just a bit since 
posting the request for help on the 24th.

Steve W


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple