🚀 go-pugleaf

In article <9209060053.AA02428@arissoft.com> john@arissoft.COM writes:
>I use GNU Bash, version 1.12.9, and the terminal program I use is Stuart
>2.4 on a NeXT, which has title-bar-setting escape sequences that are a
>superset of those understood by Xterm.  A problem I was experiencing was
>that the Readline library used by Bash doesn't know what part of the prompt
>is actually visible.  So, if I have a big, nasty PS1 variable that puts
>lots of things in the title bar, Readline decides I've hit the 80th column
>and breaks the line way too early.

In <1992Sep10.174049.2127@tc.cornell.edu> riley@theory.tc.cornell.edu (Daniel S. Riley) writes:
> For title bar escape sequences, why not use PROMPT_COMMAND?  For instance,
> my .bashrc has
[...neat workaround deleted...]

Also this works for title strings, it is no solution for those of
us, who want to include escape sequences _INTO_ the prompt.  
I like to have the host name included into the prompt string
and highlighted by inverse video.  So my prompt is defined as:

    ME=`logname`
    if [ -w /etc/passwd ]
    then PCH="#"
    else PCH=">"
    fi
    SMSO=`tput smso` 
    RMSO=`tput rmso`
    PS1="$ME@$SMSO\h$RMSO:$TERMLINE \w \!$PCH "

I have omitted the code to determine $TERMLINE (which will be
usually something like 'tty05'), because it is somewhat nasty 
and has nothing to do with problem here.

Regards, Peter
Note: The usual "english_is_not_my_native_language"-disclaimer applies
      to this "kraut"-babble.
-=-=-
Peter Funk \\ ArtCom GmbH, Schwachhauser Heerstr. 78, D-2800 Bremen 1
Work at home: Oldenburger Str.86, D-2875 Ganderkesee 1 / voice : top secret