Re: Color problem
- To: mutt-users@xxxxxxxx
- Subject: Re: Color problem
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Wed, 3 Jun 2009 10:28:28 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=h6cBlI23MCMb+lwR0fISb+Qowsw=; b=kIUS ez+0Keu/ztnADqLTho1pRnQlGP8Nf2+2Q1jzLIZLI7cBbpbYMf0zuHRoYy0FY1kx lCppzT/xEdBOcWLRCgb/JIb36VJmig+SteolZJU+/RNAgZ534+s1XnQ7w/LLiDFq gw72/qlvGfTGGqhlELtV8V63Q1ztpm+T1GLO2D8=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=jUTBY9jgLF52jlnLH+rAGoslnDkMQLHyBHbMmIIGWCOXgbdDTL10cp59odE4fap6A9cvs8BXdIPAogZkjZmCtqtl7x0rJOzHeFVXWa6tEFZ+T2wnyb/I7dEK969g0XONUQ0rZM+iPwXxYqFnmP19KGUhq5hC9myssz+ZQrpuJyI=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090603151845.GA14847@xxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090603000831.GA10262@xxxxxxxxx> <20090603150802.GE214@xxxxxxxxxxxxxxxxx> <20090603151845.GA14847@xxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-06-01)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wednesday, June 3 at 11:18 AM, quoth Ken Weingold:
>> Do you mean that they're un-bolded while the indicator is
>> highlighting them? Or do you mean that they're un-bolded only if
>> the indicator is higher up on the list than they are and that when
>> the indicator is lower in the list they become bolded again?
>
> It's actually when I move the indicator bar over them. If I jump
> straight to the top of the index, the boldness doesn't get affected.
> I do know it's compiling with the correct version of ncurses from
> 'mutt -v's output. Or could that not be correct?
What it's compiling against and what it's linking against could be two
different things. Mutt gets the version number from the ncurses header
files; but it's quite possible that those headers are mis-matched to
the library that was actually used to link against.
Assuming you don't know: compiling most large software (like mutt) is
a two-step process. First, each source file (e.g. a ".c" file) is
compiled into an object file (a ".o" file), then the object files are
linked together along with any libraries that are needed to create an
executable binary (the program itself). People who have multiple
versions of any given library often get themselves into trouble by
compiling with headers that don't match the libraries. For example,
you could compile against version 2.6 and then link against 2.4. The
program would think it was using 2.6, but since it was linked against
2.4, would run into weirdness.
This isn't a problem for people who only ever have a single version of
any given library available.
~Kyle
- --
I would therefore like to posit that computing's central challenge,
how not to make a mess of it, has not yet been met.
-- Edsger Dijkstra
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJKJpacAAoJECuveozR/AWeBpIP/RNnEWwgmnfnk76xncqTWxsH
v8r2bj9GhTPP2sOoCmTspjl2PuPBp36LmkMuowZeXu2otEUsSNNtinvAeo2GV8Ev
+UWW3kdPr8fOnSLK6veeumpa/u1aVuYshGGxrq37sQnMEvssN72kkLPOHAd5CaxD
uprnqdDeFyMzkkIsp5kd3bkrvM9Knr1TcaRFp1RAgCCQeEbQR1ZrPKZZqWjBdgub
7VQhKo6AUdvyfssiSlb2zPXSqcSXPgPpVzBbjEPRSC1IH3M3Xoh2Qf8czHNJxQ4P
uhy0saW9fAkeKinUL2XpcWiNsCV3NOPIpE1Op2mRSz5GkptIHnteCRkhzU9Rw3Hb
6RvtJsvm5/yYwNZGDJ6EG+co/wo5+x1jt0KT1UkQLjooltOUPRLyETRKKc3dDtrx
6JbI/qncG9Ga9LoaeCbbTtSSiA95xp1EyvqsaApyGp7DjbQpcnpxlKvf8u78TcLD
N/G7UuczfYjIpkZvdrLJ/PntW0/6Sgbf1uqD+1TYo4dNc78/YyDHcxVaZTSjTiCe
yGxfyFpjgvcaHkK87N1w6i94YPohd4wQ9n+wy3fHASnjZu3hc/nvEb56Qes77ben
3CVh119/mtkA2a+S9+nciDhaX1ZwuBLsvDw6N8IA6RdQpTeNlOp0oFaFwjXuMrYu
uX1jBBzHS0mC3QY6gSUm
=sH9V
-----END PGP SIGNATURE-----