On Tue, Aug 31, 2010 at 01:57:39PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7
Quoth Brian Cuttler on Wednesday, 01 September 2010:
On Tue, Aug 31, 2010 at 01:57:39PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is
Chip,
curie's mutt is built with slang, nnewton's is built with ncurses. That
probably accounts for the difference.
I finally got a download of a newer mutt version from sunfreeware
and will install it on the Solaris x86 platform.
Assuming that its also built with slang - do you know what I
Quoth Brian Cuttler on Wednesday, 01 September 2010:
Chip,
curie's mutt is built with slang, nnewton's is built with ncurses. That
probably accounts for the difference.
I finally got a download of a newer mutt version from sunfreeware
and will install it on the Solaris x86 platform.
Chip,
I installed mutt 1.5.20 from sunfreeware and found that we
where missing several required packages, including slang.
I installed and mutt seems to open my outbox ok, That is
the index displays correctly with header and footer inverse
and the index bar being visible.
Typically the outbox
Quoth Brian Cuttler on Wednesday, 01 September 2010:
Chip,
I installed mutt 1.5.20 from sunfreeware and found that we
where missing several required packages, including slang.
I installed and mutt seems to open my outbox ok, That is
the index displays correctly with header and footer
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Hate ask, but I think I've tried the obvious...
Moving from a Solaris 9/sparc box with mutt Mutt 1.4.1i (2003-03-19)
to Solaris 10x86 with Mutt 1.5.17 (2007-11-01) and I'm finding that
my colors and highlighting don't work at all.
Checked
Chip,
No, mutt is not producing any errors, its just failing, not only
to set colors but even to highlight (or is it simply reverse)
the black and white header and footer or provide inverse for the
message I'm currently pointing to in the index.
With mutt not complaining I'm guessing it is a
On Tue, Aug 31, 2010 at 01:56:01PM -0400, Brian Cuttler wrote:
Hate ask, but I think I've tried the obvious...
Moving from a Solaris 9/sparc box with mutt Mutt 1.4.1i (2003-03-19)
to Solaris 10x86 with Mutt 1.5.17 (2007-11-01) and I'm finding that
my colors and highlighting don't work at
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Chip,
No, mutt is not producing any errors, its just failing, not only
to set colors but even to highlight (or is it simply reverse)
the black and white header and footer or provide inverse for the
message I'm currently pointing to in the
Will,
I'd tried term vt100 and dtterm, setting both xterm and xterm-color
env vars I now get a black block cursor in the last column of the
index as I move up and down the message index.
looking more and more like a termcap issue... I'll see if there are
other vt100 or dtterm color settings as
Will,
Here is a crazy test. from the system I'd ssh'd into, I ssh'd
to a linux box where, the # ls command there has an option to
display different types of files in different colors. That worked
perfectly.
Term there was xterm and there was also the addtional env var
of COLORTERM set to 1.
By
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that the errors will tells someone who
is not me where the
Quoth Brian Cuttler on Tuesday, 31 August 2010:
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that
Chip,
This works a little better
# echo `tput setaf 1`hello`tput me`
tput: unknown terminfo capability 'me'
hello
Where we are in red from hello onwards.
So there are some colors available.
On Tue, Aug 31, 2010 at 11:46:57AM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Chip,
This works a little better
# echo `tput setaf 1`hello`tput me`
tput: unknown terminfo capability 'me'
hello
Where we are in red from hello onwards.
So there are some colors available.
On Tue, Aug 31, 2010 at 11:46:57AM -0700,
On Tue, Aug 31, 2010 at 02:54:39PM -0400, Brian Cuttler wrote:
Will,
Here is a crazy test. from the system I'd ssh'd into, I ssh'd
to a linux box where, the # ls command there has an option to
display different types of files in different colors. That worked
perfectly.
Term there was
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8 colors, that is
Black, Red, Green, Yellow, Blue, Magenta, Cyan, White (on white...)
When run on my Solaris 10 desktop I then get
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8 colors, that is
Black, Red, Green, Yellow, Blue, Magenta, Cyan, White
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8
Quoth Brian Cuttler on Tuesday, 31 August 2010:
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf
May I suggest that trimming some of the quoted material in these
messages? It'd make it easier to read the thread, and maybe help out.
Nico
--
BTW, I use screen in gnome-terminal.
I notice the following:
- TERM is screen-bce;
- VIM works fine, handles colors;
- Mutt built with S-Lang does not start unless I set TERM to xterm or
xterm-color; Mutt complains that Key sequence is too long,
SLcurses_initscr: init failed;
- If I
Quoth Nicolas Williams on Tuesday, 31 August 2010:
BTW, I use screen in gnome-terminal.
I notice the following:
- TERM is screen-bce;
- VIM works fine, handles colors;
- Mutt built with S-Lang does not start unless I set TERM to xterm or
xterm-color; Mutt complains that Key
On Tue, Aug 31, 2010 at 02:37:48PM -0700, Chip Camden wrote:
You could probably get mutt to start with TERM=screen-bce is termcap has
an appropriate entry for it. I found that even though mutt with slang
uses terminfo, it queries termcap on startup.
screen(1) does set TERMCAP in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tuesday, June 2 at 08:08 PM, quoth Ken Weingold:
I hope I can explain this well. I just built mutt 1.5.19 after using
1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19
was compiled using ncurses 5.6 (5.4 is also
On Wed, Jun 3, 2009, Kyle Wheeler wrote:
On Tuesday, June 2 at 08:08 PM, quoth Ken Weingold:
I hope I can explain this well. I just built mutt 1.5.19 after using
1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19
was compiled using ncurses 5.6 (5.4 is also
-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
On Wed, Jun 3, 2009, Kyle Wheeler wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, June 3 at 11:36 AM, quoth Ken Weingold:
Ah, crap. :) This on panix.com servers. I used
--with-curses=/usr/local/ncurses-5.6
They are really good, so I assume it is correct. There is also an
ncurses-5.4 install under /usr/local.
On Wed, Jun 3, 2009, Kyle Wheeler wrote:
Either way, there is a patch I used for the last version of mutt I
was using, 1.5.10. 5patch-1.5.1.nr.indicator_not_bright. This was
to make any text under the indicator bar not bold. It still works,
and interestintly enough, also fixes this
I hope I can explain this well. I just built mutt 1.5.19 after using
1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19
was compiled using ncurses 5.6 (5.4 is also available). I have new
mail in bold cyan. In 1.5.19, if I scroll the indicator up over the
new emails, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, April 18 at 10:27 AM, quoth He Wen:
i wanna know how to highlight a specific field of a index item, for
example, the date field?
There's no good way, unfortunately. There may be a patch out there
somewhere that allows you to do it, but
Hi,
* He Wen schrieb am Samstag, den 18. April 2009:
i wanna know how to highlight a specific field of a index item, for
example, the date field?
Here is the Indexcolor Patch:
http://greek0.net/mutt.html
Andreas
Hi you guys!
i wanna know how to highlight a specific field of a index item, for example, the
date field?
Thanks :-)
--
He Wen
School of Electrical Engineering Computer Science,
Peking University
Beijing, 100871 China
I'll have to try building 1.3.23i and see if I can spot the problem
(when
I'm at home). I did build one or two of the 1.3.x series, but just to
check on progress...
setting the color of the normal object to have a default background
makes all the difference.
it is not even necessary to
Lou,
I am happily repling to your message in the mutt editor, with properly
colored quotes and all, after replacing the mutt_vim_rc file with the
one you sent yesterday.
Thanks again!,
Marco
On 2001/07/10 20:18:20 -0400, Louis LeBlanc wrote:
I thought that file looked
On 07/11/01 07:32 PM, Marco Fioretti sat at the `puter and typed:
Lou,
I am happily repling to your message in the mutt editor, with properly
colored quotes and all, after replacing the mutt_vim_rc file with the
one you sent yesterday.
Thanks again!,
Marco
Glad
On Tue, Dec 26, 2000 at 01:00:28PM -0500, Thomas Dickey wrote:
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote:
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
2. ssh-ing into my home machine from a Windows box.
On Fri, Jan 05, 2001 at 06:30:53PM +0100, Virginie wrote:
On Tue, Dec 26, 2000 at 01:00:28PM -0500, Thomas Dickey wrote:
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote:
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
2. ssh-ing into my home machine from a Windows box.
When I'm home, I set all my background colors to "default" so that the
transparent Eterm effect works in X. However, when I'm on a
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote:
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
2. ssh-ing into my home machine from a Windows box.
When I'm home, I set all my background colors to "default" so that
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote:
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
Yay.
2. ssh-ing into my home machine from a Windows box.
My condolences :-).
When I'm home, I set all my background
On Mon, Nov 29, 1999 at 06:36:20PM -0600, David DeSimone wrote:
:
: set quote_regexp="^([ \t]?[ \t]?[:|])+"
I'm curious, I don't quite understand the logic behind setting your
quote matching to this kind of pattern instead of using the default:
set quote_regexp="^([ \t]*[|#:}])+"
--
George Georgalis [[EMAIL PROTECTED]] wrote:
I'm having problems with quoted colorings. At one point I thought the
mutt viewer would use a different color for each of the adjoining lines
below
color1
color2
color1
color2
They display in different colors in vim, but they are all the
George Georgalis [[EMAIL PROTECTED]] wrote:
I'm having problems with quoted colorings. At one point I thought the
mutt viewer would use a different color for each of the adjoining lines
below
color1
color2
color1
color2
They are all the same color for me, too. However, the
Scott Scriven [[EMAIL PROTECTED]] wrote:
George Georgalis [[EMAIL PROTECTED]] wrote:
I'm having problems with quoted colorings. At one point I thought the
mutt viewer would use a different color for each of the adjoining lines
below
color1
color2
color1
color2
They
George Georgalis [EMAIL PROTECTED] wrote:
color1
color2
color1
color2
They display in different colors in vim, but they are all the same in
the viewer?
For me, they show up in different colors.
You need two things to make this work:
1. Some colors defined for multiple quote
49 matches
Mail list logo
