Re: Bashrc distinguish between mintty and x-windows xterm

Re: Bashrc distinguish between mintty and x-windows xterm

[Andrew Hancock]

Buchbinder, Barry (NIH/NIAID) [E] <BBuchbinder <at> niaid.nih.gov> writes:
>
> # Only set ThisTerm if not set.
> if [ -z "${ThisTerm}" ]
> then
>   if [ ${PPID} = 1 ]
>   then
>     ThisTerm=cmd
>   else
>     if [ "$(cat /proc/${PPID}/exename)" = '/usr/bin/mintty' ]
>     then
>       ThisTerm=mintty
>     else
>       # not minty, not cmd, so xterm
>       ThisTerm=xterm
>     fi
>   fi
> fi
>
> Then set colors by the value of ThisTerm.

Barry, it works flawlessly.  Thanks immensely!

--
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

RE: Bashrc distinguish between mintty and x-windows xterm

[Buchbinder, Barry (NIH/NIAID) [E]]

Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM
>Barry, it works flawlessly. Thanks immensely!

You are very welcome.

But I forgot to export ThisTerm, otherwise it is always unset when
a subshell is launched.

# Only set ThisTerm if not set.
if [ -z "${ThisTerm}" ]
then
  if [ ${PPID} = 1 ]
  then
    ThisTerm=cmd
  else
    if [ "$(cat /proc/${PPID}/exename)" = '/usr/bin/mintty' ]
    then
      ThisTerm=mintty
    else
      # not minty, not cmd, so xterm
      ThisTerm=xterm
    fi
  fi
  export ThisTerm
fi

One could test exename for /usr/bin/xterm instead of assigning by
the process of elimination.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
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

Re: Bashrc distinguish between mintty and x-windows xterm

[Ken Jackson]

==== Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM
> >Barry, it works flawlessly. Thanks immensely!
> 
> But I forgot to export ThisTerm, otherwise it is always unset when
> a subshell is launched.

Access to the /proc file system is fast, so you could forgo the
variable and access it directly:

case "$(< /proc/$PPID/exename)" in
    */xterm)  echo "This is an xterm" ;;
    */mintty) echo "This is a mintty" ;;
esac

I don't have a need for this, but I had wondered how I would do it
if I did.  So I'm glad you posted this.

-Ken Jackson

--
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

Re: Bashrc distinguish between mintty and x-windows xterm

[Andy]

Ken Jackson <cygwin <at> jackson.io> writes:
> ==== Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry
> (NIH/NIAID) [E] wrote:
>> Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM
>>>Barry, it works flawlessly. Thanks immensely!
>> 
>> But I forgot to export ThisTerm, otherwise it is always unset when
>> a subshell is launched.
> 
> Access to the /proc file system is fast, so you could forgo the
> variable and access it directly:
> 
> case "$(< /proc/$PPID/exename)" in
>     */xterm)  echo "This is an xterm" ;;
>     */mintty) echo "This is a mintty" ;;
> esac

Barry, Ken,

Thanks for your valuable scripting examples.  It sent me scurrying back to the
man page to figure out case/esac and command substitution.  It's also a good
reminder of the wealth of detail available in /proc.


--
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

Bashrc distinguish between mintty and x-windows xterm

[Andy]

My bashrc sets the color of the prompt depending on $TERM.  My x-windows xterm
has a white background and the cygwin default terminal, which has a black
background, use to not have $TERM=xterm.  I could distinguish between them in
the bashrc script, and set the prompt colours accordingly.  Now with mintty
emulating an xterm, $TERM takes on the string "xterm" (but it has a black
background).  I would like to find a simple bash script way to tell the
difference between when bashrc is being called from a mintty versus an actual
x-windows xterm.  Can anyone suggest a way?


--
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

RE: Bashrc distinguish between mintty and x-windows xterm

[Buchbinder, Barry (NIH/NIAID) [E]]

Andy sent the following at Monday, May 21, 2012 8:39 PM
>My bashrc sets the color of the prompt depending on $TERM. My x-windows
>xterm has a white background and the cygwin default terminal, which has
>a black background, use to not have $TERM=xterm. I could distinguish
>between them in the bashrc script, and set the prompt colours
>accordingly. Now with mintty emulating an xterm, $TERM takes on the
>string "xterm" (but it has a black background). I would like to find a
>simple bash script way to tell the difference between when bashrc is
>being called from a mintty versus an actual x-windows xterm. Can anyone
>suggest a way?

(Not totally tested.  YMMV.)

# Only set ThisTerm if not set.
if [ -z "${ThisTerm}" ]
then
  if [ ${PPID} = 1 ]
  then
    ThisTerm=cmd
  else
    if [ "$(cat /proc/${PPID}/exename)" = '/usr/bin/mintty' ]
    then
      ThisTerm=mintty
    else
      # not minty, not cmd, so xterm
      ThisTerm=xterm
    fi
  fi
fi

Then set colors by the value of ThisTerm.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

--
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

Re: Bashrc distinguish between mintty and x-windows xterm

[Andy]

Andy wrote:
| Ken Jackson <cygwin <at> jackson.io> writes:
|> ==== Fri, May 25, 2012 at 09:32AM -0400 Buchbinder, Barry
|> (NIH/NIAID) [E] wrote:
|>> Andrew Hancock sent the following at Friday, May 25, 2012 12:42 AM
|>>>Barry, it works flawlessly. Thanks immensely!
|>> 
|>> But I forgot to export ThisTerm, otherwise it is always unset when
|>> a subshell is launched.
|> 
|> Access to the /proc file system is fast, so you could forgo the
|> variable and access it directly:
|> 
|> case "$(< /proc/$PPID/exename)" in
|>     */xterm)  echo "This is an xterm" ;;
|>     */mintty) echo "This is a mintty" ;;
|> esac
|
|Barry, Ken,
|
|Thanks for your valuable scripting examples.  It sent me scurrying back to the
|man page to figure out case/esac and command substitution.  It's also a good
|reminder of the wealth of detail available in /proc.

For the record, this in .bashrc seems to work well in xterm's white background
and mintty's black background.

case "$(< /proc/$PPID/exename)" in
   */xterm) function setPS1() {
      PS1="\[\033]0;\w\007\033[32m\]\u@\h \[\033[35m\w\033[0m\]\n$" ;
      echo xterm
   } ;;
   */mintty) function setPS1() {
      PS1="\[\e]0;\w\a\]\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$" ;
      echo mintty
   } ;;
esac


--
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

Re: Bashrc distinguish between mintty and x-windows xterm

[Andy]

Andy <AndyMHancock <at> gmail.com> writes:
> For the record, this in .bashrc seems to work well in xterm's white
> background > and mintty's black background.
> 
> case "$(< /proc/$PPID/exename)" in
>    */xterm) function setPS1() {
>       PS1="\[\033]0;\w\007\033[32m\]\u@\h \[\033[35m\w\033[0m\]\n$" ;
>       echo xterm
>    } ;;
>    */mintty) function setPS1() {
>       PS1="\[\e]0;\w\a\]\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$" ;
>       echo mintty
>    } ;;
> esac

Actually, the above fails if bash is invoked from a process for which
/proc/$PPID/exename doesn't exist.  For example, if I shell out of Windows-based
gvim, $PPID is 1.  I found that the following works for this case too.

function setPS1() \
   { PS1="\[\e]0;\w\a\]\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$" ; }
if [ -a /proc/$PPID/exename ]; then
   case "$(< /proc/$PPID/exename)" in
      */xterm) function setPS1() {
         PS1="\[\033]0;\w\007\033[32m\]\u@\h \[\033[35m\w\033[0m\]\n$" ;
      } ;;
   esac
fi


--
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