This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Slight issue in base-files-4.0-6


2011/3/22, Bravery, Gavin S wrote:
>>>> Basically, the escapes aren't working right (in XWindows at the very
>>>> least).
>>>>
>>>> So I have now changed it to say:
>>>>   case "${KSH_VERSION}" in
>>>>   *MIRBSD*KSH* )
>>>>     PS1=$(print '^[]0;${PWD}\n^[[32m${USER}@${HOSTNAME}
>>>> ^[[33m${PWD/${HOME}/~}^[[0m\n$ ')
>>>>     ;;
>>>>   *PD*KSH* )
>>>>     PS1=$(print '^[]0;${PWD}\n^[[32m${USER}@${HOSTNAME}
>>>> ^[[33m${PWD}^[[0m\n$
>>>> ')
>>>>     ;;
>>>>   esac
>>>> Please note, ^[ means I have done CTRL-V + ESC.
>>>> Also, MKSH and PDKSH need different settings, as PDKSH doesn't seem
>>>> to have the ${name/pattern/replacement} syntax.
>>> Although pdksh is still installable using setup.exe, it is officially
>>> orphaned and upstream development ceased a long ago (5.2.14 is from
>>> Jul '99, and cygwin's
>>> 5.2.14-3 is from Dec '03).
>>> If you want to use a ksh derivative, you are probably better switching
>>> to mksh, which is actively mantained.
>>> IOW, /etc/profile no longer supports pdksh. If you want to keep using
>>> it, you'll need to explicitely add support for it (as you've done
>>> already).
>>Agreed, however, the point about properly escaping the PS1 fields still
>> holds for mksh.  I hadn't noticed because I have my own custom .mshrc that
>> sets PS1.

WJFFM with the PS1 setting included in 4.0-6 for mksh.

> Don't really mind. Just felt that whilst people could still install pdksh it
> should work for that too.
> Then when pdksh gets pulled off the install list properly, it could go from
> profile file then (it's only a case tweak in the mean time anyway).

Maybe it should be considered to drop pdksh from the distro, being
mksh a mantained replacement and pdksh orphaned and upstream
unmantained.

> BTW, I have a side issue which is when mksh installs it doesn't make a ksh
> link, which means scripts with #!/usr/bin/ksh stop working.
> That said, to be honest, I'm trying to move things to bash anyway :-)

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]