does not show messages based on my
color highlighting rules, but based on prior behavor things
are looking good.
I ran into what I suspect is a syntax error with the inbox
when I invoke mutt with no arguments.
Bad IDN imaps.wadsworth.org.
.muttrc file beings this way.
[curie] ~ 233 more .muttrc
inverse
and the index bar being visible.
Typically the outbox does not show messages based on my
color highlighting rules, but based on prior behavor things
are looking good.
I ran into what I suspect is a syntax error with the inbox
when I invoke mutt with no arguments.
Bad IDN
, it needs to have the correct number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built with the same color options (256 color support, in my case).
So, what kind
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built with the same color options (256 color support, in my case).
So, what kind of problem are you seeing? Is mutt
such a rudimenary question.
When you ssh in to the server what does:
env|grep TERM
output?
If the TERM is xterm, perhaps also exporting COLORTERM=xterm-color
will help.
--
Will Fiveash
up correctly in *both*
termcap and terminfo. Specifically, it needs to have the correct number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built
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
ssh in to the server what does:
env|grep TERM
output?
If the TERM is xterm, perhaps also exporting COLORTERM=xterm-color
will help.
--
Will Fiveash
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth
definition I use has to be set up correctly in *both*
termcap and terminfo. Specifically, it needs to have the correct number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt
# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built with the same color options (256 color support, in my case).
So, what kind of problem are you seeing? Is mutt complaining
definition I use has to be set up correctly in *both*
termcap and terminfo. Specifically, it needs to have the correct number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt
) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built with the same color options (256 color support, in my case).
So, what kind of problem are you seeing? Is mutt complaining
display color.
I have a shell script wrapper for mutt so it can find the
/usr/gnu/lib/libncurses.so.5 lib. It basically looks like:
#!/usr/bin/ksh -p
export LD_LIBRARY_PATH=/usr/gnu/lib
exec $HOME/bin/$(uname -p)/mutt $@
# end of script
I have the binary version of mutt in $HOME/bin/i386
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
# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has to
be built with the same color options (256 color support, in my case).
So, what kind of problem are you seeing? Is mutt complaining
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 ${color}``date
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
On Wed, Jul 21, 2010 at 02:02:56PM -0700, Chip Camden wrote:
Quoth Chip Camden on Wednesday, 21 July 2010:
I have 256 colors enabled for my urxvt, and all works well with mutt
until I try to define more than 21 color specifications in .muttrc, the
colors seem to get confused. Must be a table
I have 256 colors enabled for my urxvt, and all works well with mutt
until I try to define more than 21 color specifications in .muttrc, the
colors seem to get confused. Must be a table overflow or something.
Should I engender a flea? Or is this already known? I tried searching
the flea
Quoth Chip Camden on Wednesday, 21 July 2010:
I have 256 colors enabled for my urxvt, and all works well with mutt
until I try to define more than 21 color specifications in .muttrc, the
colors seem to get confused. Must be a table overflow or something.
Should I engender a flea
On Wed, Jul 21, 2010 at 01:53:58PM -0700, Chip Camden wrote:
I have 256 colors enabled for my urxvt, and all works well with mutt
until I try to define more than 21 color specifications in .muttrc, the
colors seem to get confused. Must be a table overflow or something.
Should I engender a flea
Quoth Michael Elkins on Wednesday, 21 July 2010:
On Wed, Jul 21, 2010 at 01:53:58PM -0700, Chip Camden wrote:
I have 256 colors enabled for my urxvt, and all works well with mutt
until I try to define more than 21 color specifications in .muttrc, the
colors seem to get confused. Must
Hi Gary,
On Thu, May 27, 2010 at 03:38 PM PDT, Gary Johnson wrote:
GJ On 2010-05-27, Mun mjeli...@gmail.com wrote:
GJ Hi,
GJ
GJ I would like to use 'color body' to highlight a line which matches
GJ 'pattern' AND also highlight the successive line. However, I couldn't
GJ find any way
Hi,
I would like to use 'color body' to highlight a line which matches
'pattern' AND also highlight the successive line. However, I couldn't
find any way to extend 'pattern' across multiple lines.
Is such a thing possible in mutt?
Regards,
--
Mun
On 2010-05-27, Mun mjeli...@gmail.com wrote:
Hi,
I would like to use 'color body' to highlight a line which matches
'pattern' AND also highlight the successive line. However, I couldn't
find any way to extend 'pattern' across multiple lines.
Is such a thing possible in mutt?
I don't
On Tue, Mar 16, 2010 at 11:02:25AM -0400, Chuck Smith wrote:
I know this is a little off topic for this list, but my latest
update from Ubuntu resulted in color syntax in vim for reply
messages in Mutt to disappear. Now everything is the default
console green. Any ideas?
Hi,
Check
Hi. I use w3m as an external program to view html mails in mutt. I
have the following in my mailcap
text/html; w3m -T text/html -I %{charset} -dump %s;
nametemplate=%s.html; copiousoutput
This works very well for me because w3m can handle the charset problem
very well. However, there is another
On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote:
* peng shao on Tuesday, March 16, 2010 at 05:00:03 -0400
Because you w3m -dump to standard output -- or in this case to
Mutt's pager.
Okay I see, thanks.
With lynx -dump? I doubt it.
I use
text/html; lynx -dump
On Tue, Mar 16, 2010 at 6:12 AM, peng shao shallp...@gmail.com wrote:
On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote:
much. But for me there is still some drawback, the
%{charset} is lost :(
Is there any possibility if I set autoview as off, and when I read an
email,
* peng shao on Tuesday, March 16, 2010 at 06:12:02 -0400
On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote:
With lynx -dump? I doubt it.
I use
text/html; lynx -dump -force_html -assume-charset=%{charset} %s;
needsterminal; copiousoutput;
in the mailcap and set
On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote:
Mmh, you could create an addional mailcap file and toggle the
$mailcap_path variable. Try the following (untested):
set my_lynx_cap=/path/to/lynxmailcap
macro pager K1 \
enter-command set
On 2010-03-16, peng shao shallp...@gmail.com wrote:
On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote:
Mmh, you could create an addional mailcap file and toggle the
$mailcap_path variable. Try the following (untested):
set my_lynx_cap=/path/to/lynxmailcap
I know this is a little off topic for this list, but my latest update from
Ubuntu resulted in color syntax in vim for reply messages in Mutt to disappear.
Now everything is the default console green. Any ideas?
--
Chuck Smith
signature.asc
Description: Digital signature
On Tue, Mar 16, 2010 at 10:32 AM, Gary Johnson garyj...@spocom.com wrote:
On 2010-03-16, peng shao shallp...@gmail.com wrote:
On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote:
d.
The pipe is allowed here. If you are getting an error message from
using that rule, the
On Sun, Jan 17, 2010 at 07:01:03PM -0400, Monte Stevens wrote:
On Sun, Jan 17, 2010 at 10:42:48PM +0100, Jeffrey Ratcliffe wrote:
What is the advantage of running mutt within emacs?
Short answer:
You don't have to navigate to Emacs (server) when editing a message.
Longer answer:
I
On Sat, Jan 16, 2010 at 09:21:17AM -0500, Haines Brown KB1GRM ET1 wrote:
I'm running mutt on debian and within emcas. I have emcacs set up so
that the keybinding M-C-m opens mutt in emacs. The problem is that I
can't get this to use my mutt color configuration.
What
On Sun, Jan 17, 2010 at 10:42:48PM +0100, Jeffrey Ratcliffe wrote:
What is the advantage of running mutt within emacs?
Short answer:
You don't have to navigate to Emacs (server) when editing a message.
Longer answer:
I have my Mutt editor set to emacsclient and I have Emacs' server
running.
this to use my mutt color configuration.
What shell/terminal is emacs using? multi-term and ansi-term work with
colors here.
Monte,
I have emacs use anti-term.
Haines
that the keybinding M-C-m opens mutt in emacs. The problem is that I
can't get this to use my mutt color configuration.
What shell/terminal is emacs using? multi-term and ansi-term work with
colors here.
Monte,
I have emacs use anti-term.
I'm not familiar with anti-term (neither is Google
Horacio Sanson wrote:
Currently I am using the ivy league color theme from Aaron Toponce
(see link below) with a couple of modifications to make it work in my
transparent KDE Konsole.
http://pthree.org/2008/10/22/ivy-league-theme-for-mutt/
I was looking for similar 256 color themes
Currently I am using the ivy league color theme from Aaron Toponce (see link
below) with a couple of modifications to make it work in my transparent KDE
Konsole.
http://pthree.org/2008/10/22/ivy-league-theme-for-mutt/
I was looking for similar 256 color themes for mutt but there does not appear
On Tue 05 Jan 2010 at 00:37:59 PST Horacio Sanson wrote:
I was looking for similar 256 color themes for mutt but there does not
appear to be any on the whole Internet.
Are there any other themes around? Or is anyone willing to share their
colors?
Also a work in progress, but here's what I use
* Horacio Sanson hsan...@gmail.com [2010-01-05 09:39]:
Currently I am using the ivy league color theme from Aaron Toponce (see link
below) with a couple of modifications to make it work in my transparent KDE
Konsole.
http://pthree.org/2008/10/22/ivy-league-theme-for-mutt/
I was looking
On Tue 05 Jan 2010 at 01:24:30 PST Charlie Kester wrote:
On Tue 05 Jan 2010 at 00:37:59 PST Horacio Sanson wrote:
I was looking for similar 256 color themes for mutt but there does not
appear to be any on the whole Internet.
Are there any other themes around? Or is anyone willing to share
Does anyone know how to make mutt display patches/diff files in color?
I tried using pygmentize that in console colors the diff files correctly but
when used from within mutt the text is displayed correctly but not colored.
Here is my configuration:
My .mailcap file:
text/x-diff;pygmentize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, October 26 at 01:56 PM, quoth Horacio Sanson:
I tried using pygmentize that in console colors the diff files
correctly but when used from within mutt the text is displayed
correctly but not colored.
Add this to your muttrc:
set
Hi Kyle!
On Fri, 30 Oct 2009, Kyle Wheeler wrote:
On Monday, October 26 at 01:56 PM, quoth Horacio Sanson:
I tried using pygmentize that in console colors the diff files
correctly but when used from within mutt the text is displayed
correctly but not colored.
Add this to your muttrc:
On Tue, Oct 27, 2009 at 09:57:39PM -0700, Gary Johnson wrote:
On 2009-10-28, Horacio Sanson hsan...@gmail.com wrote:
Does anyone know how to make mutt display patches/diff files in color?
I am using pygmentize that in a terminal outputs the diff/patch files with
easy to read
colors
Does anyone know how to make mutt display patches/diff files in color?
I am using pygmentize that in a terminal outputs the diff/patch files with easy
to read
colors but when used from within mutt the text is displayed correctly but not
colored.
Here is my configuration:
My .mailcap file
On 2009-10-28, Horacio Sanson hsan...@gmail.com wrote:
Does anyone know how to make mutt display patches/diff files in color?
I am using pygmentize that in a terminal outputs the diff/patch files with
easy to read
colors but when used from within mutt the text is displayed correctly
On Thu, Sep 10, 2009 at 03:15:52PM -0500, Kyle Wheeler wrote:
} I do it by adding the following to my ~/.bashrc file:
}
} export TERM=nsterm-16color
I see now that setting the terminal type in
Preferences - Advanced - Emulation - Declare terminal as:
is really just setting the
On Wed, Sep 09, 2009 at 02:32:53PM -0500, Kyle Wheeler wrote:
} What's your TERM setting?
I usually use dtterm, which as I understood it was the most
compatible with Terminal.app. I just tried all of ansi,
xterm, xterm-color, rxvt and vt100. All of them show the same
color problem except
Can you try opening up a stock Terminal.app window and see if you
get similiar issues?
With dtterm, mutt complains that most of my color settings are
invalid, because dtterm doesn't have enough colors (officially, dtterm
only supports 8 colors, while Apple's Terminal supports 16, and I use
all
On Thu, Sep 10, 2009 at 03:15:52PM -0500, Kyle Wheeler wrote:
Meh. dtterm is, I believe, for Sun terminals.
Close enough; dtterm is the standard terminal application from CDE,
the Common Desktop Environment, based on Motif. It was supposed to be
platform neutral, available on all major Unix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, September 10 at 04:04 PM, quoth Derek Martin:
On Thu, Sep 10, 2009 at 03:15:52PM -0500, Kyle Wheeler wrote:
Meh. dtterm is, I believe, for Sun terminals.
Close enough; dtterm is the standard terminal application from CDE,
the Common
).
For example in my .muttrc file I have:
color error brightred default
Where I a black on white Terminal.app screen the error
will be red on grey. Using 'default' for the background
is supposed to leave it set as it was. In this way, by
just setting foreground colors, the same settings may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, September 9 at 07:33 AM, quoth Vance Shipley:
Since upgrading to Snow Leopard my colour definitions are
messed up. Anywhere where I set the colour I use 'default'
for the background colour so that it remains whatever 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
Is there a way to design multiple color rules for incoming mail in the index? I
want to have all new mail green, for instance, and if the mail belongs to a
known mailing list, color it as yellow after it has been read.
Currently, I can color mail yellow with ~l, and new mail green with ~N, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, May 8 at 10:56 AM, quoth Eric Patton:
Is there a way to design multiple color rules for incoming mail in
the index? I want to have all new mail green, for instance, and if
the mail belongs to a known mailing list, color it as yellow
Kyle Wheeler wrote:
Thus, list messages will only be yellow if they aren't new, because if
they're new, they match both rules, and the last one wins.
Of course, you can always make complex patterns. For example:
color index yellow default '~l ! ~N'
Does that help?
Yes, this last
patterns. For example:
color index yellow default '~l ! ~N'
Does that help?
Yes, this last line you wrote was what I was referring to - I don't know what
this syntax (!) means, and how to construct complex coloring patterns in
general.
Does '~l ! ~N' mean 'color list mail yellow
Hi,
* Eric Patton wrote:
Does '~l ! ~N' mean 'color list mail yellow if it is not new', or...?
Yepp. Please start reading at:
http://dev.mutt.org/doc/manual.html#complex-patterns
It's about searching, but mutt uses the same pattern syntax for coloring.
Rocco
it, but in standard mutt... nope.
I thought that maybe you could do it by changing your $index_format to
include color-changing commands... but that gets passed through iconv
(apparently), so the ansi color commands get masked out by question
marks.
~Kyle
- --
Victory goes to the player who makes
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 am working with an IBM ThinkPad 570 (P2/366MHz/192MB) and it works
perfectly but for some days I have setup some new colorization and now
mutt kill all of my CPU and Memory resources...
[ '~/.mutt/colors' ]
color body brightmagenta
' ]
| color body brightmagentadefault ^\-\-\-\-\\[ STDIN \\]\-\-.*
1: Why are all the dashes ('-') backslashed?
2: You do not need the trailing '.*' on all these patterns.
| color body brightmagentadefault ^\\+\-\-\-\\[ STDIN \\]\-\-.*
| color
Hi all
How can I set the background color ? I use mutt in a xterm with custom
background color. I would like to keep this setting. Actually when I launch
mutt he reset (to white) the background.
The color I use in my xterm is not the «classic» color #fbe6b3 (what I
mean is the color
On 06/11/08 10:14, Albert Shih wrote:
Hi all
How can I set the background color ? I use mutt in a xterm with custom
background color. I would like to keep this setting.
Set default as the background color. This works for me in
xfce4-terminal, preserving terminal transparency.
For example
Hi,
it's just a cosmetic but it hurts my eyes every day :-)
Seems to me that the color of tree symbols is static.
I have this in my muttrc
color tree black white
color index black magenta ~T
color indicator white blue
And when I tag a mail that uses tree symbols these
do not respect
On Thu, Feb 08, 2007 at 05:38:15PM -0600, Travis H. wrote:
On Thu, Feb 08, 2007 at 06:34:19PM +0100, Rado S wrote:
Is there still considerable danger in dumping html via w3m or
some other html to text converter?
Well, theoretically, any time you operate on data provided by someone
who
On Thu, Feb 08, 2007 at 05:49:45PM -0600, Travis H. wrote:
On Thu, Feb 08, 2007 at 06:29:35PM +0100, Rado S wrote:
I work in a startup of 10 people. I'm the only reason {... for
IMAP, ssh, linux.}
By most in our company, the effort to keep this going is
considered a waste of time.
far
enough to see the git version has the option, but I haven't actually tried
it yet.
I tried it, and was disappointed. While in the *terminal*, it works
like a charm (though it has the nasty habit of not restoring the
original color scheme), mutt seems to strip all the color commands
the nasty habit of not restoring the
original color scheme), mutt seems to strip all the color commands
from the output of mailcap programs.
Even with
set allow_ansi
in your muttrc?
Yes. Now, interestingly, that is only true for autoview'd html. If I
view-attachments and then view the html
On Fri, Feb 02, 2007 at 05:02:32PM +0100, Rado S wrote:
{...}
I'm sorry, explain, I don't see how it works against you when 2 sides
agree on a common course that helps both by making things simpler.
I'm not afraid to ask, I'm just wise enough to know that its
futile, or worse,
On Thu, Feb 01, 2007 at 11:04:23PM -0600, Travis H. wrote:
I would say your best angle is a security angle. See if you can get
someone with the authority to recognize that reading your email with a
web browser and/or sending HTML poses a threat to the security of the
company and the users
On Mon, Feb 05, 2007 at 05:53:39PM -0600, Jeremy Blosser wrote:
Anyway, to the original question: the elinks and links family of text
browsers can render HTML colors as ascii. If you use those as your HTML
viewers you can get the colors and follow the quoting.
Thanks very much. Hoping that
=- Marc Vaillant wrote on Thu 8.Feb'07 at 11:58:48 -0500 -=
Is there still considerable danger in dumping html via w3m or
some other html to text converter?
No, see wiki FAQ how to make it work.
Also, we correspond with several DoD organizations on a weekly
basis. We've never had an email
=- Marc Vaillant wrote on Thu 8.Feb'07 at 11:52:23 -0500 -=
I'm sorry, explain, I don't see how it works against you when
2 sides agree on a common course that helps both by making
things simpler.
I'm not afraid to ask, I'm just wise enough to know that its
futile, or worse,
On Thu, Feb 08, 2007 at 06:34:19PM +0100, Rado S wrote:
=- Marc Vaillant wrote on Thu 8.Feb'07 at 11:58:48 -0500 -=
Is there still considerable danger in dumping html via w3m or
some other html to text converter?
No, see wiki FAQ how to make it work.
Ok thanks. I do it now, just
On Thu, Feb 08, 2007 at 06:34:19PM +0100, Rado S wrote:
Is there still considerable danger in dumping html via w3m or
some other html to text converter?
Well, theoretically, any time you operate on data provided by someone
who may not be trustworthy, you face a risk. The magnitude of the
On Thu, Feb 08, 2007 at 06:29:35PM +0100, Rado S wrote:
I work in a startup of 10 people. I'm the only reason {... for
IMAP, ssh, linux.}
By most in our company, the effort to keep this going is
considered a waste of time.
I'd jump ship, honestly. I really don't like the Windows
On Feb 08, Marc Vaillant [EMAIL PROTECTED] wrote:
On Mon, Feb 05, 2007 at 05:53:39PM -0600, Jeremy Blosser wrote:
Anyway, to the original question: the elinks and links family of text
browsers can render HTML colors as ascii. If you use those as your HTML
viewers you can get the colors and
enough to see the git version has the option, but I haven't actually tried
it yet.
I tried it, and was disappointed. While in the *terminal*, it works
like a charm (though it has the nasty habit of not restoring the
original color scheme), mutt seems to strip all the color commands
from the output
On Mon, Feb 05, 2007 at 06:31:03PM +0100, Rado S wrote:
... one part being the defensive things listed by Travis, but you
also shouldn't forget that some outsiders rate html-ized mails
as spammy, so at least the score increases or in the worst case
it's outright blocked unless white-listed.
=- Travis H. wrote on Thu 1.Feb'07 at 23:04:23 -0600 -=
On Thu, Feb 01, 2007 at 03:59:51PM -0500, Marc Vaillant wrote:
This just isn't realistic. What sort of view of mutt do you
think an outlook user (potential mutt user) is going to get if
I tell them Hey check out this great text based
; they are pretty happy to top quote back and
forth until I give a detailed properly-quoted response to their thread,
after which they will reply with this color-coded style. This is either
peer pressure (doubtful) or they see the value in proper quoting and are
trying to do it with what they have (possible
the quoting.
It would be really nice if I could convince them to do so in
combination with the -dump flag, so that I could view the pretty HTML
*inline*. I heard a rumor that elinks supported --dump-color-mode,
but... 0.11.1 (the version in Debian stable) does not appear to do so.
~Kyle
101 - 200 of 624 matches
Mail list logo
