Re: xterm & colored Mutt
On Wed, 18 Jul 2001, Andre Wyrwa wrote: > Hello, > > I have the problem of having a non-colored mutt, when starting it in > xterm. $TERM is "xterm". > When I change $TERM to "linux" or "xterm-color" mutt will start with > colors. > So I guess it has something to do with terminfo. Unfortunately I don't > know a lot about it. On my SuSE-System mutt starts colored within a good place to start is www.google.com (search for "xterm") as I point out 2-3 times a week, "xterm-color" is incorrect for XFree86 xterm, ditto "linux". > xterm even with $TERM=xterm, so I guess they changed properties of the > xterm-terminfo-file or mutt is looking for something else to determine > if it should use colors or not. > > So, can someone help me with this? > How can I tell xterm to use xterm-color instead of xterm terminfo > without having to set $TERM manually? see the man-page. -- T.E.Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
* Thomas E. Dickey <[EMAIL PROTECTED]> [21:42 18/07/01]: > > a good place to start is www.google.com (search for "xterm") > > as I point out 2-3 times a week, "xterm-color" is incorrect for XFree86 > xterm, ditto "linux". i am new to this list. what will be the right setting fot xf86 if it is not xterm-color? it seems to be working fine for me.. ankit
Re: xterm & colored Mutt
On Wed, 18 Jul 2001, Fox Mulder wrote: > * Thomas E. Dickey <[EMAIL PROTECTED]> [21:42 18/07/01]: > > > > a good place to start is www.google.com (search for "xterm") > > > > as I point out 2-3 times a week, "xterm-color" is incorrect for XFree86 > > xterm, ditto "linux". > i am new to this list. what will be the right setting fot xf86 if it is not > xterm-color? it seems to be working fine for me.. "xterm-xfree86" -- T.E.Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
Well, I'm afraid I don't have any such entry in my termcap file. I do, however, have this one: xterm-color|xterm-co|xterm with ANSI colors:\ :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=xterm: This implies to me that xterm-color _is_ a valid setting. When I try setting TERM="xterm-xfree86" or just xterm-xfree86, I get the following: Error opening terminal: xterm-xfree86. Which implies that xterm-xfree86 is an invalid setting for the TERM variable. To quote the man xterm: Termcap(5) entries that work with xterm include ``xterm,'' ``vt102,'' ``vt100'' and ``ansi,'' and xterm automatically searches the termcap file in this order for these entries and then sets the ``TERM'' and the ``TERM- CAP'' environment variables. and: -tn name This option specifies the name of the terminal type to be set in the TERM environment variable. This terminal type must exist in the termcap(5) database and should have li# and co# entries. So . . . What am I to do? If xterm-color works and xterm-xfree86 does not, why shouldn't I use xterm-color? I know why I shouldn't use xterm-xfree86 - it just won't work :) BTW, the info I have included here applies to my FreeBSD system. I still get color with TERM=xterm on Mandrake - which does have the xterm-xfree86 entry. I suspect this whole thing really just boils down to whats in the termcap. In search of enlightenment . . . On 07/18/01 12:32 PM, Thomas E. Dickey sat at the `puter and typed: > On Wed, 18 Jul 2001, Fox Mulder wrote: > > i am new to this list. what will be the right setting fot xf86 if it is not > > xterm-color? it seems to be working fine for me.. > > "xterm-xfree86" -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://acadia.ne.mediaone.net ԿԬ Matz's Law: A conclusion is the place where you got tired of thinking.
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 03:44:51PM -0400, Louis LeBlanc wrote:
> Well, I'm afraid I don't have any such entry in my termcap file. I do,
> however, have this one:
sigh - xterm's distribution includes a termcap which can be added (up front)
to the /etc/termcap file.
> xterm-color|xterm-co|xterm with ANSI colors:\
> :pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:tc=xterm:
>
> This implies to me that xterm-color _is_ a valid setting. When I try
> setting TERM="xterm-xfree86" or just xterm-xfree86, I get the
> following:
>
> Error opening terminal: xterm-xfree86.
>
> Which implies that xterm-xfree86 is an invalid setting for the TERM
> variable.
>
> To quote the man xterm:
yes (I note that ``xterm-color'' is not mentioned either)
The real answer is this:
infocmp xterm-xfree86 xterm-color
comparing xterm-xfree86 to xterm-color.
comparing booleans.
OTbs: F:T.
bce: T:F.
mc5i: T:F.
npc: T:F.
comparing numbers.
comparing strings.
blink: '\E[5m', NULL.
cbt: '\E[Z', NULL.
civis: '\E[?25l', NULL.
cnorm: '\E[?25h', NULL.
ech: '\E[%p1%dX', NULL.
el1: '\E[1K', NULL.
enacs: '\E(B\E)0', '\E)0'.
flash: '\E[?5h$<100/>\E[?5l', NULL.
hpa: '\E[%i%p1%dG', NULL.
ich: '\E[%p1%d@', NULL.
invis: '\E[8m', NULL.
is2: '\E[!p\E[?3;4l\E[4l\E>', '\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E>'.
kDC: '\E[3;2~', NULL.
kEND: '\EO2F', NULL.
kHOM: '\EO2H', NULL.
kIC: '\E[2;2~', NULL.
kLFT: '\EO2D', NULL.
kNXT: '\E[6;2~', NULL.
kPRV: '\E[5;2~', NULL.
kRIT: '\EO2C', NULL.
kb2: '\EOE', NULL.
kcbt: '\E[Z', NULL.
kend: '\EOF', NULL.
kent: '\EOM', NULL.
kf1: '\EOP', '\E[11~'.
kf13: '\EO2P', '\E[25~'.
kf14: '\EO2Q', '\E[26~'.
kf15: '\EO2R', '\E[28~'.
kf16: '\EO2S', '\E[29~'.
kf17: '\E[15;2~', '\E[31~'.
kf18: '\E[17;2~', '\E[32~'.
kf19: '\E[18;2~', '\E[33~'.
kf2: '\EOQ', '\E[12~'.
kf20: '\E[19;2~', '\E[34~'.
kf21: '\E[20;2~', NULL.
kf22: '\E[21;2~', NULL.
kf23: '\E[23;2~', NULL.
kf24: '\E[24;2~', NULL.
kf25: '\EO5P', NULL.
kf26: '\EO5Q', NULL.
kf27: '\EO5R', NULL.
kf28: '\EO5S', NULL.
kf29: '\E[15;5~', NULL.
kf3: '\EOR', '\E[13~'.
kf30: '\E[17;5~', NULL.
kf31: '\E[18;5~', NULL.
kf32: '\E[19;5~', NULL.
kf33: '\E[20;5~', NULL.
kf34: '\E[21;5~', NULL.
kf35: '\E[23;5~', NULL.
kf36: '\E[24;5~', NULL.
kf37: '\EO6P', NULL.
kf38: '\EO6Q', NULL.
kf39: '\EO6R', NULL.
kf4: '\EOS', '\E[14~'.
kf40: '\EO6S', NULL.
kf41: '\E[15;6~', NULL.
kf42: '\E[17;6~', NULL.
kf43: '\E[18;6~', NULL.
kf44: '\E[19;6~', NULL.
kf45: '\E[20;6~', NULL.
kf46: '\E[21;6~', NULL.
kf47: '\E[23;6~', NULL.
kf48: '\E[24;6~', NULL.
kfnd: NULL, '\E[1~'.
khome: '\EOH', NULL.
kslt: NULL, '\E[4~'.
mc0: '\E[i', NULL.
mc4: '\E[4i', NULL.
mc5: '\E[5i', NULL.
op: '\E[39;49m', '\E[m'.
rmam: '\E[?7l', NULL.
rmcup: '\E[?1049l', '\E[2J\E[?47l\E8'.
rmso: '\E[27m', '\E[m'.
rmul: '\E[24m', '\E[m'.
rs1: '\Ec', NULL.
rs2: '\E[!p\E[?3;4l\E[4l\E>', '\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E>'.
setb:
'\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m', NULL.
setf:
'\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m', NULL.
sgr:
'\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\016%e\017%;',
NULL.
sgr0: '\E[m\017', '\E[m'.
smam: '\E[?7h', NULL.
smcup: '\E[?1049h', '\E7\E[?47h'.
vpa: '\E[%i%p1%dd', NULL.
>Termcap(5) entries that work with xterm include
>``xterm,'' ``vt102,'' ``vt100'' and ``ansi,'' and xterm
>automatically searches the termcap file in this order for
>these entries and then sets the ``TERM'' and the ``TERM-
>CAP'' environment variables.
>
> and:
>
> -tn name
>This option specifies the name of the terminal
>type to be set in the TERM environment variable.
>This terminal type must exist in the termcap(5)
>database and should have li# and co# entries.
>
> So . . .
>
> What am I to do? If xterm-color works and xterm-xfree86 does not, why
> shouldn't I use xterm-color? I know why I shouldn't use xterm-xfree86
> - it just won't work :)
>
> BTW, the info I have included here applies to my FreeBSD system.
> I still get color with TERM=xterm on Mandrake - which does have the
> xterm-xfree86 entry. I suspect this whole thing really just boils
> down to whats in the termcap.
>
> In search of enlighte
Re: xterm & colored Mutt
In order to turn on color in xterm enter the following line in ~/.Xdefaults *customization: -color This will turn on color in all apps that use color in an xterm window. Ed -- _ Linux, the choice | One difference between a man and a machine of a GNU generation -o) | is that a machine is quiet when well oiled. /\ | _\_v | | -
Re: xterm & colored Mutt
Ed Robitaille wrote> > In order to turn on color in xterm enter the > following line in ~/.Xdefaults > > *customization: -color > > This will turn on color in all apps that use color in an xterm window. Oops ! You'll have to re-start 'X' or or enter the command that re-init's 'X' to see this go into effect. Ed -- _ Linux, the choice | Wiker's Law: Government expands to absorb of a GNU generation -o) | revenue and then some. /\ | _\_v | | -
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 09:21:24PM -0400, Ed Robitaille wrote: > Ed Robitaille wrote> > > In order to turn on color in xterm enter the > > following line in ~/.Xdefaults > > > > *customization: -color > > > > This will turn on color in all apps that use color in an xterm window. However I'm pretty sure that color ls in freebsd only works with xterm-color (as far as the various xterm termcaps go). I am pretty sure the person who sent the original message was using freebsd. I use xterm as my termcap on Linux machines (even if I'm connecting from my workstations which are both freebsd) but i use xterm-color in freebsd. does anyone know for sure that you can get the xterm-xfree86 termcap working on *bsd and that color ls still works with it? w
Re: xterm & colored Mutt
On 2001.07.18, in <[EMAIL PROTECTED]>, "Ed Robitaille" <[EMAIL PROTECTED]> wrote: > Ed Robitaille wrote> > > In order to turn on color in xterm enter the > > following line in ~/.Xdefaults > > > > *customization: -color > > > > This will turn on color in all apps that use color in an xterm window. > > Oops ! You'll have to re-start 'X' or or enter the command > that re-init's 'X' to see this go into effect. Or: % xrdb -merge <~/.Xdefaults -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: xterm & colored Mutt
On Wed, 18. Jul 2001 um 06:30:06PM -0700, Will Yardley wrote: > > > In order to turn on color in xterm enter the > > > following line in ~/.Xdefaults > > > > > > *customization: -color > > > > > > This will turn on color in all apps that use color in an xterm window. I did this, but it's not enough. Yes, ls --color does work then but mutt still opens black/white. > However I'm pretty sure that color ls in freebsd only works with xterm-color > (as far as the various xterm termcaps go). Well, I'm sorry, but I am this person and I don't use freebsd, but linux. I now temporarily solved the problem by changing the TERM-variable within my .bashrc. But I don't like to do it that way, so maybe later I'll find a better solution. André.
Re: xterm & colored Mutt
On 18, Jul, 2001 at 11:03:01AM +0200, Andre Wyrwa wrote: > How can I tell xterm to use xterm-color instead of xterm terminfo > without having to set $TERM manually? In your ~/.Xdefaults put this (from my own ~/.Xdefaults, tweaking might be needed: ! $HOME/.Xdefaults ! ! To reload it: ! ! xrdb -load ~/.Xdefaults ! mangling xterm XTerm*termName: xterm-color<<< this is where you set $TERM !! XTerm.VT100*color0: black XTerm.VT100*color1: red XTerm.VT100*color2: green XTerm.VT100*color3: yellow XTerm.VT100*color4: blue XTerm.VT100*color5: magenta XTerm.VT100*color6: cyan XTerm.VT100*color7: white XTerm.VT100*color8: black XTerm.VT100*color9: red XTerm.VT100*color10: green XTerm.VT100*color11: yellow XTerm.VT100*color12: blue XTerm.VT100*color13: magenta XTerm.VT100*color14: cyan XTerm.VT100*color15: white XTerm.VT100*colorAttrMode: true XTerm.VT100*colorMode: on XTerm.VT100*colorBDMode: on XTerm.VT100*colorBD: white XTerm.VT100*colorBLMode: on XTerm.VT100*colorBL: yellow XTerm.VT100*colorRVMode: on XTerm.VT100*colorRV: cyan XTerm.VT100*colorULMode: on XTerm.VT100*colorUL: cyan XTerm.VT100*boldFont: -jmk-neep-bold-r-normal-*-*-100-100-100-*-*-iso8859-1 XTerm.VT100*highlightColor: blue4 XTerm.VT100*geometry: 80x25 XTerm.VT100*pointerColor: white XTerm.VT100*pointerColorBackground: black XTerm.VT100*pointerShape: xterm XTerm.VT100*curses: true XTerm.VT100*saveLines: 1500 XTerm.VT100*underLine: off XTerm.VT100*cursorColor: magenta XTerm.VT100*cursorBlink: on XTerm.VT100*cursorOffTime: 500 XTerm.VT100*cursorOnTime: 500 XTerm.VT100*font: -jmk-neep-bold-r-normal-*-*-100-100-100-*-*-iso8859-1 XTerm.VT100*font1: -jmk-neep-bold-r-normal-*-*-70-100-100-*-*-iso8859-1 XTerm.VT100*font2: -jmk-neep-bold-r-normal-*-*-80-100-100-*-*-iso8859-1 XTerm.VT100*font3: -jmk-neep-bold-r-normal-*-*-90-100-100-*-*-iso8859-1 XTerm.VT100*font4: -jmk-neep-bold-r-normal-*-*-100-100-100-*-*-iso8859-1 XTerm.VT100*font5: -jmk-neep-bold-r-normal-*-*-120-100-100-*-*-iso8859-1 XTerm.VT100*font6: -jmk-neep-bold-r-normal-*-*-160-100-100-*-*-iso8859-1 XTerm.VT100*foreground: lightgrey XTerm.VT100*background: black XTerm.VT100*backarrowKeyIsErase: true XTerm.VT100*scrollBar: off The explicit color declarations probably isn't needed, and the font isn't a standard X font, so beware. My machine runs OpenBSD current, but I can see no good reason that it shouldn't work everywhere else. HTH M -- ×·.¸¸.·´¨)¸. ·´ ¸.·´¨) OMorten Liebach <[EMAIL PROTECTED]> (_¸.·´ (¸.·´ ¸.·× 0http://home1.stofanet.dk/liebach/ (_¸.·´ohttp://pc89225.stofanet.dk/ .
Re: xterm & colored Mutt
Hi, I had the same problem: ls and vim had colors but mutt did not. Changing the TERM env did not help. I rebuilt mutt with slang lib (instead of curses) and everything worked fine. Use 'configure --with-slang=dir' to tell configure where to find slang lib. Hope it helps -- Dominique On Thu, Jul 19, 2001 at 09:34:42AM +0200, Andre Wyrwa ([EMAIL PROTECTED]) wrote: > On Wed, 18. Jul 2001 um 06:30:06PM -0700, Will Yardley wrote: > > > > In order to turn on color in xterm enter the > > > > following line in ~/.Xdefaults > > > > > > > > *customization: -color > > > > > > > > This will turn on color in all apps that use color in an xterm window. > > I did this, but it's not enough. > Yes, ls --color does work then but mutt still opens black/white. > > > However I'm pretty sure that color ls in freebsd only works with xterm-color > > (as far as the various xterm termcaps go). > > Well, I'm sorry, but I am this person and I don't use freebsd, but > linux. > > I now temporarily solved the problem by changing the TERM-variable > within my .bashrc. But I don't like to do it that way, so maybe later > I'll find a better solution. > > André.
Re: xterm & colored Mutt
On Wed, 18. Jul 2001 um 04:53:05PM +0200, Morten Liebach wrote: > XTerm*termName: xterm-color<<< this is where you set $TERM !! Ahh...this is wonderful. Thx a lot. André.
Re: xterm & colored Mutt
On Thu, 19. Jul 2001 um 09:18:24AM -0700, Dominique Pelle wrote: > I had the same problem: ls and vim had colors but mutt > did not. Changing the TERM env did not help. Changing the TERM env helps for me, I just don't like it. But maybe it's the only way. I was simply wondering why it works in SuSE without changing the TERM variable. But maybe they compiled it with slang, too. > I rebuilt mutt with slang lib (instead of curses) and > everything worked fine. > Use 'configure --with-slang=dir' to tell configure > where to find slang lib. Thx a lot, but I'm building an lfs-system and up to this point no other program needs slang. So I'll stay away from installing slang as long as possible. André.
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 04:53:05PM +0200, Morten Liebach wrote: > The explicit color declarations probably isn't needed, and the font > isn't a standard X font, so beware. the color resources aren't needed (but it's worth noting that as you have listed them, the bold-colors are suppressed) -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 09:15:26PM -0400, Ed Robitaille wrote: > In order to turn on color in xterm enter the > following line in ~/.Xdefaults > > *customization: -color > > This will turn on color in all apps that use color in an xterm window. not exactly. It tells the X library to look for a resource file such as XTerm-color, but the content of that file was merged into XTerm a few years ago. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 06:30:06PM -0700, Will Yardley wrote: > On Wed, Jul 18, 2001 at 09:21:24PM -0400, Ed Robitaille wrote: > > Ed Robitaille wrote> > > > In order to turn on color in xterm enter the > > > following line in ~/.Xdefaults > > > > > > *customization: -color > > > > > > This will turn on color in all apps that use color in an xterm window. > > However I'm pretty sure that color ls in freebsd only works with xterm-color > (as far as the various xterm termcaps go). I am pretty sure the person who > sent the original message was using freebsd. I use xterm as my termcap on > Linux machines (even if I'm connecting from my workstations which are both > freebsd) but i use xterm-color in freebsd. does anyone know for sure that > you can get the xterm-xfree86 termcap working on *bsd and that color ls still > works with it? unless there's a FreeBSD-specific patch for it, color ls is hardcoded and ignores the contents of the termcap file. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
On Thu, Jul 19, 2001 at 06:56:51PM +0200, Andre Wyrwa wrote: > On Thu, 19. Jul 2001 um 09:18:24AM -0700, Dominique Pelle wrote: > > I had the same problem: ls and vim had colors but mutt > > did not. Changing the TERM env did not help. > > Changing the TERM env helps for me, I just don't like it. > But maybe it's the only way. > I was simply wondering why it works in SuSE without changing the TERM > variable. But maybe they compiled it with slang, too. or (more likely) they installed the 'xterm' terminfo to match xterm-xfree86. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: xterm & colored Mutt
On Wed, Jul 18, 2001 at 06:30:06PM -0700, Will Yardley wrote: > On Wed, Jul 18, 2001 at 09:21:24PM -0400, Ed Robitaille wrote: > > Ed Robitaille wrote> > > > In order to turn on color in xterm enter the > > > following line in ~/.Xdefaults > > > > > > *customization: -color > > > > > > This will turn on color in all apps that use color in an xterm window. > > However I'm pretty sure that color ls in freebsd only works with xterm-color > (as far as the various xterm termcaps go). I am pretty sure the person who > sent the original message was using freebsd. I use xterm as my termcap on xterm-xf86-v32 is in their termcap (but ncurses 5.0 is in freebsd-current, and that has a more recent version of terminfo from which the termcap entry for xterm-xfree86 should be obtainable). For whatever reason, the FreeBSD people don't seem inclined to maintain their termcap file (it's one of those things I see on the longstanding bugs/issues lists). it also contains "xterm-color", but it neither matches the one in ncurses, nor is it complete or correct (it uses SGR 39 for 'op' without using 'ut'). the best I could say of that, is that it "happens to work" if you don't look too closely. > Linux machines (even if I'm connecting from my workstations which are both > freebsd) but i use xterm-color in freebsd. does anyone know for sure that > you can get the xterm-xfree86 termcap working on *bsd and that color ls still > works with it? > > w -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
