Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Tue, Mar 19, 2002 at 09:46:08PM -0600, Jeremy Blosser wrote: $COLORFGBG is marked as an experimental feature. I've gotten 2-3 reports of this particular problem - but only months after I stumbled on it myself. Apparently one or more of the rpm's last year turned that feature on, though it was in the code almost a year. Well, I think it was more the other bug where it would get turned on if other development features like hard-tabs were turned on. It was apparently a combination of these two. I suppose so - though both features are in the same category (not part of the default options): Development Code: --with-develop enable all development options --enable-colorfgbg compile with $COLORFGBG code --enable-hard-tabs compile with hard-tabs code --disable-root-environ limit environment when running as root --enable-xmc-glitch compile with limited support for xmc (noting now that colorfgbg is development rather than experimental, I guess my reasoning at the time was that it was a small feature that wouldn't break much ;-). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Mar 18, Thomas E. Dickey [[EMAIL PROTECTED]] wrote: On Mon, 18 Mar 2002, Pavel Roskin wrote: I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. ... Unsetting COLORFGBG fixes the problem. that's a bug that I fixed in September. The problem was that when I coded the $COLORFGBG logic (which btw is under-documented in rxvt - you have to read the C code to see it), it didn't occur to me that its format might change. It happens that the format depends on whether xpm is linked in - 2 or 3 fields. The background color is the last field. Indeed; Pavel, please see http://bugs.guug.de/db/10/1011.html for this bug and the resolution, and ignore the mails from Cindy. $COLORFGBG is marked as an experimental feature. I've gotten 2-3 reports of this particular problem - but only months after I stumbled on it myself. Apparently one or more of the rpm's last year turned that feature on, though it was in the code almost a year. Well, I think it was more the other bug where it would get turned on if other development features like hard-tabs were turned on. It was apparently a combination of these two. msg25752/pgp0.pgp Description: PGP signature
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Mar 19, Jeremy Blosser [[EMAIL PROTECTED]] wrote: Well, I think it was more the other bug where it would get turned on if other development features like hard-tabs were turned on. It was apparently a combination of these two. Sorry, I mean a combination of the colorfgbg bug, and the bug where colorfgbg was enabled when unrelated dev features were enabled. msg25753/pgp0.pgp Description: PGP signature
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Mon, 18 Mar 2002, Pavel Roskin wrote: Hi, Thomas! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. what $TERM value? xterm both under xterm and rxvt. I forgot to mention that I was running xterm from rxvt. I have found that if I run xterm from the window manager the problem goes away! When I run rxvt, it sets the following environment variables beginning with COLOR: COLORFGBG=default;0 COLORTERM=rxvt Both xterm and rxvt are using black background. From .Xdefaults: XTerm*background: black XTerm*foreground: gray85 Unsetting COLORFGBG fixes the problem. that's a bug that I fixed in September. The problem was that when I coded the $COLORFGBG logic (which btw is under-documented in rxvt - you have to read the C code to see it), it didn't occur to me that its format might change. It happens that the format depends on whether xpm is linked in - 2 or 3 fields. The background color is the last field. (Since it's under-documented, it's also possible that in the future anything that relies upon that format will be broken ;-). My interpretation is that mutt uses black text on black background. Probably ncurses interprets default in COLORFGBG as black whereas S-Lang uses the foreground from the X resources. Shouldn't ncurses ignore COLORFGBG if it has unsupported keywords (let's move this discussion elsewhere if you want to continue). $COLORFGBG is marked as an experimental feature. I've gotten 2-3 reports of this particular problem - but only months after I stumbled on it myself. Apparently one or more of the rpm's last year turned that feature on, though it was in the code almost a year. Not exactly mutt problem, but may be useful thing to know if other people ask. -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Mon, 18 Mar 2002, Pavel Roskin wrote: Hi, Thomas! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. the term 'blank screen' was misleading (to me). Totally black might have jogged my memory regarding $COLORFGBG (though the unrelated report of the pager which does not display anything was what I was thinking about). It's not a mutt problem, though as you noted. When I first saw it (early September or late August), it was from running the ncurses test program. -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
Hi, Thomas! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. what $TERM value? xterm both under xterm and rxvt. I forgot to mention that I was running xterm from rxvt. I have found that if I run xterm from the window manager the problem goes away! When I run rxvt, it sets the following environment variables beginning with COLOR: COLORFGBG=default;0 COLORTERM=rxvt Both xterm and rxvt are using black background. From .Xdefaults: XTerm*background: black XTerm*foreground: gray85 Unsetting COLORFGBG fixes the problem. My interpretation is that mutt uses black text on black background. Probably ncurses interprets default in COLORFGBG as black whereas S-Lang uses the foreground from the X resources. Shouldn't ncurses ignore COLORFGBG if it has unsupported keywords (let's move this discussion elsewhere if you want to continue). Not exactly mutt problem, but may be useful thing to know if other people ask. -- Regards, Pavel Roskin
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Fri, Mar 15, 2002 at 03:40:57PM -0500, Pavel Roskin wrote: Hello! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. what $TERM value? It turns out that the default configuration uses ncurses-5.2. I tried configuring Mutt with slang-1.4.4. It works fine. My guess is that Mutt does something with page switching that the newer versions of ncurses don't like. I believe it's a major bug that will be a frequently asked question as soon as mutt-1.4 is released. I checked the lists to see if it's not already a frequently asked question. There is a very similar description of the problem, except that it's not specific about software versions: http://marc.theaimsgroup.com/?l=mutt-usersm=101062129425997w=2 That doesn't sound the same. The closest I can recall from this list is one that says the pager comes up blank - both ncurses and slang. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: Mutt 1.3.28 + ncurses 5.2 + xterm = blank screen
On Fri, Mar 15, 2002 at 03:40:57PM -0500, Pavel Roskin wrote: Hello! I've compiled mutt-1.3.28i in the default configuration on RedHat Linux 7.2 (i386) with all updates. If I run it in xterm (from XFree86-4.1.0) or in rxvt-2.7.6, it shows a blank screen. I can quit by pressing Ctrl-C and Enter. The same executable runs on the Linux console just fine. It turns out that the default configuration uses ncurses-5.2. I tried configuring Mutt with slang-1.4.4. It works fine. My guess is that Mutt does something with page switching that the newer versions of ncurses don't like. I believe it's a major bug that will be a frequently asked question as soon as mutt-1.4 is released. I checked the lists to see if it's not already a frequently asked question. There is a very similar description of the problem, except that it's not specific about software versions: http://marc.theaimsgroup.com/?l=mutt-usersm=101062129425997w=2 I compiled 1.3.28 on RH 7.2 with ncurses-5.2.12 and XFree86-4.1.0-3 and mutt works fine in xterm, gnome-terminal and Konsole. My $TERM is set to xterm. My compile options are: Mutt 1.3.28i (2002-03-13) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.9-31 (i586) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/spool/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/etc EXECSHELL=/bin/sh MIXMASTER=/home/ken/Mix -- Ken Wahl [EMAIL PROTECTED] http://www.kenwahl.org/ PGP/GPG Public Key at http://www.kenwahl.org/pubkey.gpg Meme Propagation Engine (MindSec) [NSA] version 7.34-12i Weaponized Linux Kernel 2.4.9-31 Uptime Is 8 days 17:39
Re: mutt and ncurses
On Wed, 13 Mar 2002, Ken Weingold wrote: On Wed, Mar 13, 2002, David Champion wrote: Run ldd mutt. This will tell you what shared dependencies the binary has (including whether it used the shared or static libs from your ncurses build). Oh, cool. So the following means that mutt doesn't need any of the ncurses libraries at all after the binary is built? ./mutt: -lintl.1 = /usr/local/lib/libintl.so.1 -liconv.2 = /usr/local/lib/libiconv.so.2 -lc.12 = /usr/lib/libc.so.12 You have to do something about the terminfo database, if there is no /usr/local/share/terminfo (ncurses normally doesn't default to looking at /usr/share/misc/terminfo, for instance unless you have set $TERMINFO or $TERMINFO_DIRS). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt and ncurses
On Wed, 13 Mar 2002, David Champion wrote: On 2002.03.13, in [EMAIL PROTECTED], Ken Weingold [EMAIL PROTECTED] wrote: Oh, cool. So the following means that mutt doesn't need any of the ncurses libraries at all after the binary is built? ./mutt: -lintl.1 = /usr/local/lib/libintl.so.1 -liconv.2 = /usr/local/lib/libiconv.so.2 -lc.12 = /usr/lib/libc.so.12 Yep. If it were depending on your ncurses build, you'd see another line like -lncurses = /home/hazmat/ncurses-5.2/libncurses.so or something. if it were - but by default ncurses doesn't build shared libraries. (On some systems such as FreeBSD which have poor linker semantics combined with a lagging-edge version of ncurses, that results in linking with the system's copy of ncurses - but ldd shows that, too ;-). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: mutt and ncurses
On 2002.03.13, in [EMAIL PROTECTED], Ken Weingold [EMAIL PROTECTED] wrote: Thanks again for all the help and suggestions. The problem was indeed ncurses. I installed it into my home dir and mutt built perfectly. But I can't keep it, since it takes up a good percentage of my quota. So here's my question. Once mutt is built, does it build the ncurses info it needs into the binary, or does it still need the ncurses install? Run ldd mutt. This will tell you what shared dependencies the binary has (including whether it used the shared or static libs from your ncurses build). Alternatively, you can assure yourself of the situation by removing the ncurses*.so files from the ncurses tree, removing your mutt binary, and rerunning make in the mutt tree to force it to link with the static libraries. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: mutt and ncurses
On Wed, Mar 13, 2002, David Champion wrote: Run ldd mutt. This will tell you what shared dependencies the binary has (including whether it used the shared or static libs from your ncurses build). Oh, cool. So the following means that mutt doesn't need any of the ncurses libraries at all after the binary is built? ./mutt: -lintl.1 = /usr/local/lib/libintl.so.1 -liconv.2 = /usr/local/lib/libiconv.so.2 -lc.12 = /usr/lib/libc.so.12 -Ken
Re: mutt and ncurses
On 2002.03.13, in [EMAIL PROTECTED], Ken Weingold [EMAIL PROTECTED] wrote: Oh, cool. So the following means that mutt doesn't need any of the ncurses libraries at all after the binary is built? ./mutt: -lintl.1 = /usr/local/lib/libintl.so.1 -liconv.2 = /usr/local/lib/libiconv.so.2 -lc.12 = /usr/lib/libc.so.12 Yep. If it were depending on your ncurses build, you'd see another line like -lncurses = /home/hazmat/ncurses-5.2/libncurses.so or something. You should be free to delete the directory. To verify that before committing to it, just rename the ncurses directory and try to run mutt. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
