Date: Tue, 4 May 2004 00:04:16 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 368 ************************************************** Monday 03 May 2004 Number 368 ************************************************** Subjects for today 1 Re: termcap colours : Andreas Buening 2 Porting MAN : John Poltorak 3 Xemacs : John Poltorak 4 OpenOffice : John Poltorak 5 Re: termcap colours : John Poltorak 6 OpenOffice : Andrea Venturoli 7 Re: termcap colours : Thomas Dickey 8 Re: OpenOffice : John Poltorak 9 Re: termcap colours : John Poltorak 10 Re: termcap colours : Thomas Dickey **= Email 1 ==========================** Date: Sun, 02 May 2004 15:59:37 +0200 From: Andreas Buening Subject: Re: termcap colours Thomas Dickey wrote: [termcap] > Then (as I understand the entry), you have blue background when running > vi, less and info, but white-on-black when doing ls and other ordinary > shell commands. My impression of John Polterak's question was that he > wanted a colored background all the time (which is harder to guarantee). Hmm, for this he could set his preferred colors in %PROMPT%. > which uses \0Q (null followed by Q) and \0I (null followed by I). > terminfo stores those nulls internally as \200. I'm not sure what > the termcap functions on OS/2 EMX do. The comments in my termcap.dat say: # PageDown |\E[3 |Next page # PageUp |\E[9 |Previous page Neither do I know what key \E[3 nor \0Q is supposed to be. Bye, Andreas **= Email 2 ==========================** Date: Sun, 2 May 2004 18:51:59 +0100 From: John Poltorak Subject: Porting MAN Has anyone had a look at porting the configure script for MAN? These is an older version here:- ftp://ftp.win.tue.nl/pub/linux-local/utils/man/man-1.5g.tar.gz for which I have a patch consisting of:- diff -NurwbB -X x-tar.dat man-1.5g/configure man-1.5g-os2/configure --- man-1.5g/configure Wed Apr 7 11:16:04 1999 +++ man-1.5g-os2/configure Tue May 11 01:07:28 1999 at at -1,4 +1,4 at at -#!/bin/sh +#!sh # # Guess values for system-dependant variables and create `Makefile'. # Copyright (C) 1991 Free Software Foundation, Inc. at at -112,7 +112,7 at at CC=${CC-cc} INSTALL=${INSTALL-install} -INCLUDEDIR=${INCLUDEDIR-/usr/include} +INCLUDEDIR=${INCLUDEDIR-g:/emx/include} rm -f conftest conftest.c compile="$CC $DEFS conftest.c -o conftest $LIBS >/dev/null 2>&1" at at -253,9 +253,9 at at # Ask the installer where various things are located. -IFS0="$IFS" -IFS=":$IFS" -for i in /bin:/usr/bin:/usr/ucb:/usr/local/bin:$PATH +IFS0=";" +IFS=";" +for i in $PATH do case $i in /*) at at -522,9 +522,9 at at # prefix="/usr/local" # Note: some distributions put man.conf in /etc # Maybe fhs wants it in /usr/share/misc -prefix="/usr" +prefix="g:/emx" bindir="bin" -sbindir="sbin" +sbindir="bin" mandir="man" confdir="lib" if [ x"$fhs" = x ]; then at at -697,7 +697,7 at at fi done if [ x$deflocale = x ]; then - deflocale="/usr/lib/locale/%N/%L" + deflocale="g:/emx/lib/locale/%N/%L" fi if [ x$default = x ]; then echo "" at at -851,7 +851,7 at at then DO_COMPRESSION=true compress= - for i in gzip bzip2 pack compress freeze yabba + for i in gzip.exe bzip2.exe pack.exe compress.exe freeze.exe yabba.exe do eval F$i=missing for j in $DEFPATH at at -943,7 +943,7 at at fi # unconditionally handle uncompression -UNCOMPRESSORS="gunzip bzip2 pcat zcat fcat unyabba" +UNCOMPRESSORS="gunzip.exe bzip2.exe pcat.exe zcat.exe fcat.exe unyabba.exe" for i in $UNCOMPRESSORS do eval F$i=missing at at -1090,7 +1090,7 at at # contains a comma. cat > conf_script << EOS -#!/bin/sh +#!sh infiles=$allargs trap 'rm -f $infiles; exit 1' 1 3 15 Does this patch look OK? Personally, I'm not too keen on including hardcoded paths like g:/emx. Also I'm not aware of the existant of locale. Is that something which is normally defined on Unix? If so, should we define it too? -- John **= Email 3 ==========================** Date: Mon, 3 May 2004 12:04:26 +0100 From: John Poltorak Subject: Xemacs Is it possible to run emacs as an X app using specific cmd line options, or does it have to be built as such? -- John **= Email 4 ==========================** Date: Mon, 3 May 2004 11:55:15 +0100 From: John Poltorak Subject: OpenOffice Does anyone know of anyone looking at getting the source for OpenOffice compiled on OS/2? -- John **= Email 5 ==========================** Date: Mon, 3 May 2004 12:17:17 +0100 From: John Poltorak Subject: Re: termcap colours On Sun, May 02, 2004 at 08:55:32AM -0400, Thomas Dickey wrote: > On Sun, 2 May 2004, Andreas Buening wrote: > > > Thomas Dickey wrote: > > > > > > On Sat, 1 May 2004, Andreas Buening wrote: > > > > :ti=\E[0;37;44m\E[=7l:te=\E[0m\E[=7h\E[1B\E[K\E[1A:\ > > > ^^^^^^^^^^^ (white-on-blue) > > > > That's true. I prefer blue background. > > > > > ^^^^^ (may reset colors to white-on-black) > > > > Yes, it does. > > Then (as I understand the entry), you have blue background when running > vi, less and info, but white-on-black when doing ls and other ordinary > shell commands. My impression of John Polterak's question was that he > wanted a colored background all the time (which is harder to guarantee). No - not necessarily. I just wondered if there was a simply utility for amending colours for a particular term type without being exposed to the arcane termcap configuration. ie something which could be used to translate those entries into a human readable form. > > > > ti and te are normally sent by vi when beginning/ending the screen mode. > > > > Also by less and info, I guess. > > > > > > > > :kE=\E[K:kN=\E]3:kP=\E]9:kF=\E]c2:kR=\E]c8:\ > > > ^^^^^^^^^^^^^^^ (my keyboard doesn't send these for > > > pageup/pagedown). > > > > No idea. What would be the correct keys? > > I have this (from entries I built/tested): > > emx-base|DOS special keys:\ > :am:bw:mi:ms:xo:\ > :co#80:it#8:li#25:\ > :K1=\0G:K2=\0L:K3=\0I:K4=\0O:K5=\0Q:ae=\E[10m:as=\E[11m:\ > :bl=^G:ce=\E[K:cl=\E[2J:cm=\E[%i%d;%dH:do=\E[B:ho=\E[H:\ > :is=\E[m\E[?7h:k1=\0;:k2=\0<:k3=\0=:k4=\0>:k5=\0?:k6=\0 at :\ > :k7=\0A:k8=\0B:k9=\0C:kD=\0S:kI=\0R:kN=\0Q:kP=\0I:kb=^H:\ > :kd=\0P:kh=\0G:kl=\0K:kr=\0M:ku=\0H:le=^H:mb=\E[5m:md=\E[1m:\ > :me=\E[0;10m:mr=\E[7m:nd=\E[C:rc=\E[u:sc=\E[s:se=\E[m:\ > :so=\E[7m:ue=\E[m:up=\E[A:us=\E[4m: > > which uses \0Q (null followed by Q) and \0I (null followed by I). > terminfo stores those nulls internally as \200. I'm not sure what > the termcap functions on OS/2 EMX do. I'm not sure if anyone else does either. I was just wondering if other platforms have the same awful colours for ANSI as we do on OS/2... I would like to extract a standard termcap file from termcap v1.3.1 but am unsure about how to do this. Is it simply a matter of running make from that archive? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 6 ==========================** Date: Mon, 3 May 2004 13:44:02 EST From: Andrea Venturoli Subject: OpenOffice ** Reply to note from John Poltorak Mon, 3 May 2004 11:55:15 +0100 > Does anyone know of anyone looking at getting the source for OpenOffice > compiled on OS/2? Like Innotek? They've released a couple of betas? Or do you mean something different? bye av. **= Email 7 ==========================** Date: Mon, 3 May 2004 07:55:27 -0400 (EDT) From: Thomas Dickey Subject: Re: termcap colours On Mon, 3 May 2004, John Poltorak wrote: > I'm not sure if anyone else does either. I was just wondering if other > platforms have the same awful colours for ANSI as we do on OS/2... The default console window for cygwin on M$ uses dull foreground on black. But on that platform I set the default palette to use white background, which is more readable. After my previous response I checked the OS/2 windows, don't see an obvious place to apply any color palette changes - so perhaps tinkering with the termcap is the only way to do this. I put on my to-do list an item to make nicer versions of some of the EMX terminfo entries). > I would like to extract a standard termcap file from termcap v1.3.1 but am > unsure about how to do this. Is it simply a matter of running make from > that archive? That doesn't contain any of the EMX types that you're discussing. There's an emx.src in ncurses which contains the (some corrections) terminfo version of the termcap.dat that you're using. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 8 ==========================** Date: Mon, 3 May 2004 13:51:14 +0100 From: John Poltorak Subject: Re: OpenOffice On Mon, May 03, 2004 at 01:44:02PM -0500, Andrea Venturoli wrote: > ** Reply to note from John Poltorak Mon, 3 May 2004 11:55:15 +0100 > > > > Does anyone know of anyone looking at getting the source for OpenOffice > > compiled on OS/2? > > Like Innotek? > They've released a couple of betas? Or do you mean something different? What Innotek have done is provide a way of running the Windows port of OpenOffice on OS/2. What I would like to see is a native port which is not dependent on some middleware like Odin. > bye > av. -- John **= Email 9 ==========================** Date: Mon, 3 May 2004 14:06:25 +0100 From: John Poltorak Subject: Re: termcap colours On Mon, May 03, 2004 at 07:55:27AM -0400, Thomas Dickey wrote: > On Mon, 3 May 2004, John Poltorak wrote: > > > I'm not sure if anyone else does either. I was just wondering if other > > platforms have the same awful colours for ANSI as we do on OS/2... > > The default console window for cygwin on M$ uses dull foreground on black. > But on that platform I set the default palette to use white background, > which is more readable. How would I go about using the term used by cygwin? > After my previous response I checked the OS/2 windows, don't see an > obvious place to apply any color palette changes - so perhaps tinkering > with the termcap is the only way to do this. I put on my to-do list an > item to make nicer versions of some of the EMX terminfo entries). > > > I would like to extract a standard termcap file from termcap v1.3.1 but am > > unsure about how to do this. Is it simply a matter of running make from > > that archive? > > That doesn't contain any of the EMX types that you're discussing. I have no real idea what is special about any of the EMX types. Do we need any of them. Isn't is possible to use a standard ANSI term on OS/2? > There's an emx.src in ncurses which contains the (some corrections) > terminfo version of the termcap.dat that you're using. Yes, I've often wondered what that was for. Is there any documentation on what it provides or what uses it? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 10 ==========================** Date: Mon, 3 May 2004 09:29:23 -0400 (EDT) From: Thomas Dickey Subject: Re: termcap colours On Mon, 3 May 2004, John Poltorak wrote: > On Mon, May 03, 2004 at 07:55:27AM -0400, Thomas Dickey wrote: > > On Mon, 3 May 2004, John Poltorak wrote: > > > > > I'm not sure if anyone else does either. I was just wondering if other > > > platforms have the same awful colours for ANSI as we do on OS/2... > > > > The default console window for cygwin on M$ uses dull foreground on black. > > But on that platform I set the default palette to use white background, > > which is more readable. > > How would I go about using the term used by cygwin? The console window itself is win32-specific. To set the $TERM value, you only need an appropriate termcap. You can generate a termcap from terminfo using ncurses, e.g., infocmp -Cr cygwin >foo > I have no real idea what is special about any of the EMX types. Do we need > any of them. Isn't is possible to use a standard ANSI term on OS/2? You "could". But "ansi" applies to a number of different terminal types. The entries in EMX's termcap.dat don't exactly match the usage from other systems. Aside from (a few years ago) updating the entries in ncurses' terminfo.src that refer to "emx", I don't recall anything else that can be done. When I'm using OS/2, I don't often use the termcap.dat > > There's an emx.src in ncurses which contains the (some corrections) > > terminfo version of the termcap.dat that you're using. > > Yes, I've often wondered what that was for. Is there any documentation on > what it provides or what uses it? not really - I started with a copy of termcap.dat, added missing definitions (wrote some comments, but not anything extensive). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net