Re: Two questions regarding header display
On Mon, Jun 20, 2022 at 08:15:13AM +1000, Cameron Simpson wrote: > On 07Jun2022 09:56, raf wrote: > >And I'm not sure I can do anything about it. > > There are many things you can do. I see you've already shifted to just > using "bold" etc in your color directives, but also: > - run a personal terminfo record without the color capabilities; > decompile the provided terminfo with untic, edit to remove the colours > (or change the colours to "mono" escape sequences, build new entry > with tic, set $TERMINFO to refer to it > - run mutt itself from a script or alias which sets $TERM just for mutt > i.e. overriding the $TERM provided by screen (which will be describing > the terminal capabilities of screen itself) > - switch from screen to tmux > > Cheers, > Cameron Simpson Thanks. cheers, raf
Re: Two questions regarding header display
* Bastian [06-20-22 08:33]: > I did not follow the entire thread, sorry for potential double post. > On 20Jun22 08:15+1000, Cameron Simpson wrote: > > On 07Jun2022 09:56, raf wrote: > > >And I'm not sure I can do anything about it. > > There are many things you can do. I see you've already shifted to just > > using "bold" etc in your color directives, but also: > > On my systems, mutt is built and linked against ncurses. I could not > make it use 256 colors. I do not recall where, but I read somewhere on > the internet (and thus it must be true :) ) that mutt needs to be built > against slang to support 256 colors. I never tried that actually and I > just accept to only have the 16 default colors set in my Xdefaults. > Of course this might be total nonsense. my mutt is built against ncurses 6.3.20220612 and I have 256 colors mutt -v |grep -i color +HAVE_COLOR +HAVE_START_COLOR -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Re: Two questions regarding header display
On 07Jun2022 09:56, raf wrote: >And I'm not sure I can do anything about it. There are many things you can do. I see you've already shifted to just using "bold" etc in your color directives, but also: - run a personal terminfo record without the color capabilities; decompile the provided terminfo with untic, edit to remove the colours (or change the colours to "mono" escape sequences, build new entry with tic, set $TERMINFO to refer to it - run mutt itself from a script or alias which sets $TERM just for mutt i.e. overriding the $TERM provided by screen (which will be describing the terminal capabilities of screen itself) - switch from screen to tmux Cheers, Cameron Simpson
Re: Two questions regarding header display
> > raf schrieb am Di., 7. Juni 2022, 01:57: > > > > > TERM=screen. > > > > > > It's OK. screen is more important to me than bold > > > headers. > > > > > > On Wed, Jun 08, 2022 at 12:23:07AM +0200, Anton Sharonov > wrote: > > > ... Gnu screen definitely supports bold if running on > > xterm... > > ...not configured in mutt yet by > > now... Reply was from handheld. Now more precise: headers in compose menu, current message in index, status line and top bar in index - all are displayed bold for me. > > TERM value is screen-bce for me. It has to be supported by > > corresponding terminfo entry. That was wrong info: only TERM=xterm-256color works for me. Any other TERM value lead to no bold, not even simple colors are displayed in mutt (via gnu-screen or directly in xterm). > > There is a bunch of color related settings in > > .screenrc on my end as well. Even italic works in xterm+gnu screen but for > > italic you would need to compile not yet released dev version of gnu screen > > (last time checked in 2021, may be they even released since then already) gnu-screen has italic support (which can be seen in vim for example when edit markdown file with syntax enabled) at least in version compiled from https://git.savannah.gnu.org/git/screen.git master (pre 5.0 branch?), f0d6154b95075f1e1198cd1fd12f7516cca57add (Date: Mon Apr 27 18:24:37 2020 +0200). Still no 5.0 tag in git. Most recent v4.9.0 version branch has _lot_ of commits which are not on master at all, may be meanwhile has even italic support merged in. On Wed, Jun 08, 2022 at 11:18:22AM +1000, raf wrote: > > Thanks. It'll probably work if I just switch from "mono" > directives to "color" directives and tell it to use bold > and default colours. Yep, that did it: > > color header bold default default ^(Subject|From|To|Cc|Date): > > cheers, > raf > Everything with "bold" on my end: color header bold color25 color252 "^(Date:|To:|From:|CC:)" color header bold color133 color252 "^Subject:" color indicator bold color16 color153 color status bold color16 color153 cheers, Anton
Re: Two questions regarding header display
On Wed, Jun 08, 2022 at 12:23:07AM +0200, Anton Sharonov wrote: > raf schrieb am Di., 7. Juni 2022, 01:57: > > > TERM=screen. > > > > It's OK. screen is more important to me than bold > > headers. > > > > Don't give up. Gnu screen definitely supports bold if running on xterm, i > see it all the time - in my vim at least, not configured in mutt yet by > now. TERM value is screen-bce for me. It has to be supported by > corresponding terminfo entry. There is a bunch of color related settings in > .screenrc on my end as well. Even italic works in xterm+gnu screen but for > italic you would need to compile not yet released dev version of gnu screen > (last time checked in 2021, may be they even released since then already) > > Cheers, Anton Thanks. It'll probably work if I just switch from "mono" directives to "color" directives and tell it to use bold and default colours. Yep, that did it: color header bold default default ^(Subject|From|To|Cc|Date): cheers, raf
Re: Two questions regarding header display
raf schrieb am Di., 7. Juni 2022, 01:57: > TERM=screen. > > It's OK. screen is more important to me than bold > headers. > Don't give up. Gnu screen definitely supports bold if running on xterm, i see it all the time - in my vim at least, not configured in mutt yet by now. TERM value is screen-bce for me. It has to be supported by corresponding terminfo entry. There is a bunch of color related settings in .screenrc on my end as well. Even italic works in xterm+gnu screen but for italic you would need to compile not yet released dev version of gnu screen (last time checked in 2021, may be they even released since then already) Cheers, Anton
Re: Two questions regarding header display
On Mon, Jun 06, 2022 at 09:53:35AM -0700, "Kevin J. McCarthy" wrote: > On Tue, Jun 07, 2022 at 12:37:59AM +1000, raf wrote: > > On Sun, Jun 05, 2022 at 07:02:24PM -0700, "Kevin J. McCarthy" > > wrote: > > > TERM=xterm-mono might work for you > > > > Thanks, but that didn't change it. > > Interesting. It works for me, at least on Debian in an xterm. > > You may want to check your terminfo entries, e.g. what do "infocmp xterm | > grep color" and "infocmp xterm-mono | grep color" return? > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA I always assumed that xterm was mono because of the existence of xterm-color. I should mention that I run xterm with the resource XTerm*colorMode: False > infocmp xterm-color | grep color colors#8, cols#80, it#8, lines#24, ncv@, pairs#64, > infocmp xterm | grep color colors#8, cols#80, it#8, lines#24, pairs#64, > infocmp xterm-mono | grep color I can see what's breaking it for me. I always run mutt with -n via an alias. If I don't use -n then bold in xterm-mono works. But if I do use -n then the currently selected message doesn't appear in reverse video in the index, so I can't easily tell which one is selected. If I comment out everything in /etc/Muttrc.d/colors.rc (this is on Debian11), then it's fine, and the reverse video and bold work. But the screen program is also (mostly) to blame. I thought it odd that color directives in the system config would affect xterm-mono, and when I uncommented them again, it still worked (unlike my original report). But my alias is actually alias m='screen mutt -n', and within screen, the TERM variable is set to "screen". That's the real reason that setting TERM=xterm-mono didn't work - it was being discarded by screen. And I'm not sure I can do anything about it. If I create a script to set TERM=xterm-mono and then run mutt, and then run that script via screen, screen terminates immediately. It must really want TERM=screen. It's OK. screen is more important to me than bold headers. Thanks. cheers, raf
Re: Two questions regarding header display
On Tue, Jun 07, 2022 at 12:37:59AM +1000, raf wrote: On Sun, Jun 05, 2022 at 07:02:24PM -0700, "Kevin J. McCarthy" wrote: TERM=xterm-mono might work for you Thanks, but that didn't change it. Interesting. It works for me, at least on Debian in an xterm. You may want to check your terminfo entries, e.g. what do "infocmp xterm | grep color" and "infocmp xterm-mono | grep color" return? -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 07:02:24PM -0700, "Kevin J. McCarthy" wrote: > On Mon, Jun 06, 2022 at 10:57:47AM +1000, raf wrote: > > And there's also the "mono" directive for terminals that > > don't support colour, e.g.: > > > > mono header bold ^(Subject|From|To|Cc|Date): > > > > But it doesn't work for me anymore (with TERM=xterm). > > TERM=xterm-mono might work for you Thanks, but that didn't change it. > > And it would bold entire headers, not just their names. > > "color header bold default default ^(Subject|From|To|Cc|Date):" > will work the same, with $header_color_partial unset (the default). > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
Re: Two questions regarding header display
On Mon, Jun 06, 2022 at 10:57:47AM +1000, raf wrote: And there's also the "mono" directive for terminals that don't support colour, e.g.: mono header bold ^(Subject|From|To|Cc|Date): But it doesn't work for me anymore (with TERM=xterm). TERM=xterm-mono might work for you And it would bold entire headers, not just their names. "color header bold default default ^(Subject|From|To|Cc|Date):" will work the same, with $header_color_partial unset (the default). -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 09:33:43AM -0700, "Kevin J. McCarthy" wrote: > On Sun, Jun 05, 2022 at 10:24:47AM -0400, Jason Franklin wrote: > > On Sun, Jun 05, 2022 at 09:26:04AM +0200, Jakub Jindra wrote: > > > set header_color_partial = yes > > > color hdrdefault FG BG > > > color header FG BG "REGEX" > > > color header FG1 BG1 "REGEX1" > > > > > > tune the colors FG, BG and REGEX to your needs. > > > > I came across that option in the manual, but I couldn't make it work at > > the time. I will have to play around with it a bit. > > See http://www.mutt.org/relnotes/1.9/ for a sample usage. > > Also note, starting with 1.12 you can add attributes before the color name. > > For example, to *only* make the headers bold: > > set header_color_partial > color header bold default default '^[^[:blank:]:]*:' > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA And there's also the "mono" directive for terminals that don't support colour, e.g.: mono header bold ^(Subject|From|To|Cc|Date): But it doesn't work for me anymore (with TERM=xterm). I don't know why that is. I think it must have worked in the past. I just "ignore" the headers I don't want to see so it's not really a problem. And it would bold entire headers, not just their names. cheers, raf
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 10:24:47AM -0400, Jason Franklin wrote: On Sun, Jun 05, 2022 at 09:26:04AM +0200, Jakub Jindra wrote: set header_color_partial = yes color hdrdefault FG BG color header FG BG "REGEX" color header FG1 BG1 "REGEX1" tune the colors FG, BG and REGEX to your needs. I came across that option in the manual, but I couldn't make it work at the time. I will have to play around with it a bit. See http://www.mutt.org/relnotes/1.9/ for a sample usage. Also note, starting with 1.12 you can add attributes before the color name. For example, to *only* make the headers bold: set header_color_partial color header bold default default '^[^[:blank:]:]*:' -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 09:26:04AM +0200, Jakub Jindra wrote: > Hi Jason, > > You're looking for config option [1]header_color_partial > > 1. http://www.mutt.org/doc/manual/#header-color-partial > > set header_color_partial = yes > color hdrdefault FG BG > color header FG BG "REGEX" > color header FG1 BG1 "REGEX1" > > tune the colors FG, BG and REGEX to your needs. I came across that option in the manual, but I couldn't make it work at the time. I will have to play around with it a bit. At least I was looking in the right place. Thanks, Jakub! -- Jason
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 09:51:29PM +1000, raf wrote: > On Sun, Jun 05, 2022 at 11:32:34AM +0200, Anton Sharonov > wrote: > > Will usage of display_filter option with your perl script below not be > > already sufficient solution even without procmail? > > Good thinking. I just tried it and it works great. > > set display_filter = /home/me/bin/fix-mail-headers-filter This is really helpful! Many thanks to Anton and raf. :) -- Jason
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 11:32:34AM +0200, Anton Sharonov
wrote:
> raf schrieb am So., 5. Juni 2022, 07:52:
>
> > On Sun, Jun 05, 2022 at 12:06:52AM -0400, Jason Franklin
> > wrote:
> >
> > > Greetings:
> > >
> > > I have two questions regarding header display...
> > >
> > > First, can the pager display header names in bold if the terminal
> > > supports it?
> > >
> > > Second some senders have weird capitalization of headers. Is it possible
> > > to display some canonical representation of any given standard header?
> > >
> > > To clarify, if the header is sent as "reply-to", I would like to always
> > > see "Reply-To" in the pager.
> > >
> > > Thanks!
> > >
> > > --
> > > Jason
> >
> > Hi, I don't know about the first part, but the second part
> > could be done if procmail or similar is used for local
> > delivery, and it passes incoming messages through a filter
> > to "correct" the headers to your liking. But it might
> > be a hassle if you aren't already using procmail.
> >
>
> Will usage of display_filter option with your perl script below not be
> already sufficient solution even without procmail?
Good thinking. I just tried it and it works great.
set display_filter = /home/me/bin/fix-mail-headers-filter
But the script needs a fix to prevent changing the From_ mbox header:
/home/me/bin/fix-mail-headers-filter:
#!/usr/bin/env perl
use warnings;
use strict;
# Modify headers if needed (e.g. "reply-to:" to "Reply-To:")
while (<>)
{
# Skip to the following trivial loop after headers
print, last if /^$/;
# Replace lowercase at start of word before colon with uppercase
s/^([^: ]*)\b([a-z])/$1\U$2/ while /^[^: ]*\b[a-z]/;
print;
}
# Just print the rest unchanged
print while (<>);
> > The above was barely tested. Don't use it without testing it on
> > lots of existing mail (one message at a time - see formail(1))
> > until you are sure that it works. And note that it doesn't
> > convert any uppercase to lowercase, only the other way around.
> >
> > cheers,
> > raf
Re: Two questions regarding header display
raf schrieb am So., 5. Juni 2022, 07:52:
> On Sun, Jun 05, 2022 at 12:06:52AM -0400, Jason Franklin
> wrote:
>
> > Greetings:
> >
> > I have two questions regarding header display...
> >
> > First, can the pager display header names in bold if the terminal
> > supports it?
> >
> > Second some senders have weird capitalization of headers. Is it possible
> > to display some canonical representation of any given standard header?
> >
> > To clarify, if the header is sent as "reply-to", I would like to always
> > see "Reply-To" in the pager.
> >
> > Thanks!
> >
> > --
> > Jason
>
> Hi, I don't know about the first part, but the second part
> could be done if procmail or similar is used for local
> delivery, and it passes incoming messages through a filter
> to "correct" the headers to your liking. But it might
> be a hassle if you aren't already using procmail.
>
Will usage of display_filter option with your perl script below not be
already sufficient solution even without procmail?
> ~/.procmailrc:
>
> :0 fw
> | /home/me/bin/fix-mail-headers-filter
>
> /home/me/bin/fix-mail-headers-filter:
>
> #!/usr/bin/env perl
> use warnings;
> use strict;
> # Modify headers if needed (e.g. "reply-to:" to "Reply-To:")
> while (<>)
> {
> # Skip to the following trivial loop after headers
> print, last if /^$/;
> # Replace lowercase at start of word before colon with uppercase
> s/^([^:]*)\b([a-z])/$1\U$2/ while /^[^:]*\b[a-z]/;
> print;
> }
> # Jut print the rest unchanged
> print while (<>);
>
> The above was barely tested. Don't use it without testing it on
> lots of existing mail (one message at a time - see formail(1))
> until you are sure that it works. And note that it doesn't
> convert any uppercase to lowercase, only the other way around.
>
> cheers,
> raf
>
>
Re: Two questions regarding header display
Hi Jason, You're looking for config option [1]header_color_partial 1. http://www.mutt.org/doc/manual/#header-color-partial set header_color_partial = yes color hdrdefault FG BG color header FG BG "REGEX" color header FG1 BG1 "REGEX1" tune the colors FG, BG and REGEX to your needs. Best, JJ On 2022-06-05 00:06, Jason Franklin wrote: Greetings: I have two questions regarding header display... First, can the pager display header names in bold if the terminal supports it? Second some senders have weird capitalization of headers. Is it possible to display some canonical representation of any given standard header? To clarify, if the header is sent as "reply-to", I would like to always see "Reply-To" in the pager. Thanks! -- Jason -- Jakub Jindra signature.asc Description: PGP signature
Re: Two questions regarding header display
On Sun, Jun 05, 2022 at 12:06:52AM -0400, Jason Franklin
wrote:
> Greetings:
>
> I have two questions regarding header display...
>
> First, can the pager display header names in bold if the terminal
> supports it?
>
> Second some senders have weird capitalization of headers. Is it possible
> to display some canonical representation of any given standard header?
>
> To clarify, if the header is sent as "reply-to", I would like to always
> see "Reply-To" in the pager.
>
> Thanks!
>
> --
> Jason
Hi, I don't know about the first part, but the second part
could be done if procmail or similar is used for local
delivery, and it passes incoming messages through a filter
to "correct" the headers to your liking. But it might
be a hassle if you aren't already using procmail.
~/.procmailrc:
:0 fw
| /home/me/bin/fix-mail-headers-filter
/home/me/bin/fix-mail-headers-filter:
#!/usr/bin/env perl
use warnings;
use strict;
# Modify headers if needed (e.g. "reply-to:" to "Reply-To:")
while (<>)
{
# Skip to the following trivial loop after headers
print, last if /^$/;
# Replace lowercase at start of word before colon with uppercase
s/^([^:]*)\b([a-z])/$1\U$2/ while /^[^:]*\b[a-z]/;
print;
}
# Jut print the rest unchanged
print while (<>);
The above was barely tested. Don't use it without testing it on
lots of existing mail (one message at a time - see formail(1))
until you are sure that it works. And note that it doesn't
convert any uppercase to lowercase, only the other way around.
cheers,
raf
Two questions regarding header display
Greetings: I have two questions regarding header display... First, can the pager display header names in bold if the terminal supports it? Second some senders have weird capitalization of headers. Is it possible to display some canonical representation of any given standard header? To clarify, if the header is sent as "reply-to", I would like to always see "Reply-To" in the pager. Thanks! -- Jason
Re: mailing list config - two questions
On Thu, Feb 25, 2021 at 05:46:04PM -0500, Jon LaBadie wrote: > > When is it useful to have a mailing list to which > you are not subscribed "known"? IIRC, the original purpose was mostly to setup the (not ever ratified as a real standard, and not commonly used now) mail-followup-to header appropriately, that is, if you're subscribed and use "list-reply", the mail-followup-to header gets set to just the list's address, whereas if it's "known" only, it would set m-f-t to your email _and_ the list address when you use "list-reply". Since the draft, from what I can see, expired in 1998, and never became a standard, one could make the argument that it's not really sensible for Mutt to continue supporting it, but ¯\_(ツ)_/¯ w
mailing list config - two questions
While researching my response in another topic I came across the "subscribe" list that I don't recall seeing previously. I've been using the "lists" list for the same purpose. As I read it, "lists" items are known mailing lists and possibly subscribed to while "subscribe" items mailing lists to which I am subscribed and thus by default are known. When is it useful to have a mailing list to which you are not subscribed "known"? My mutt index typically shows the poster's name. But my own posts do not show my name. This is the situation for other mailing list also, not just mutt-user so I must be composing my header's incorrectly. How should the From:/To:/??? headers be composed so that mutt picks up my name for display in the index? -- Jon H. LaBadie mut...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Two questions
Greetings! Two questions. First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? Kind Regards, -Noesis -- _ ___ / | / /___ ___ _(_) / |/ / __ \/ _ \/ ___/ / ___/ / /| / /_/ / __(__ ) (__ ) /_/ |_/\/\___//_// noesis at darktide dot com http://www.darktide.com/noesis/ DigitalNoesis.com - Darktide.com msg30368/pgp0.pgp Description: PGP signature
Re: Two questions
Not sure about the error 13, but to keep a transparent background, use the default color as the background color for everything when setting your colors. Just make sure not to use mutt in a white background terminal after the change though :-. HTH It has come to my attention... ...that Noesis said on Tuesday, Aug 20 2002: Greetings! Two questions. First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? Kind Regards, -Noesis -- _ ___ / | / /___ ___ _(_) / |/ / __ \/ _ \/ ___/ / ___/ / /| / /_/ / __(__ ) (__ ) /_/ |_/\/\___//_// noesis at darktide dot com http://www.darktide.com/noesis/ DigitalNoesis.com - Darktide.com -- --Sam UC Davis, California USA
Re: Two questions - error 13 - terminal transparency
* Noesis [EMAIL PROTECTED] [2002-08-20 13:37]: First, when I send e-mail lately I get an error 13 - but the mail sends. Any ideas? os, mutt version [1], setup, commands, error messages? which MTA? changed its setup? checked the logs? Second, I like to keep mutts 'standard' look (plus or minus a few things), however I want to make the background transparent in mutt. How do I go about doing that? use a terminal which allows transparency?! ps: spamassassin reported your mails as spam. makes you think - i hope. Sven [1] (yes, i have seen the header. still - you never know..)
Re: Two questions
On Mon, Jun 03, 2002 at 04:36:35PM -0500, David T-G wrote: % 2) What's the right way to do batch refiling, particularly of mailing %lists? Is there a way to specify a save-hook based on To: rather %than From:? The actual best way is the same as when it is delivered: run it through procmail or another MDA. Otherwise you should probably tag a pattern and then save that bunch to wherever and go on to the next pattern. Actually, I've discovered that it is possible to set up a save-hook with a To: (or any header) match, using a pattern. Something like: save-hook ~h mutt-users@\\.mutt\\.org =mutt-users This works great! Combined with tagging threads, it makes it very fast to refile incoming messages. -- - Adam - Surgam, Inc. is a technology consulting firm with strong background in delivering scalable and robust enterprise web and IT applications. http://www.surgam.net
Re: Two questions
Rocco, et al -- ...and then Rocco Rutte said... % % Hi, Hello! % % * Benjamin Pflugmann [2002-06-04 01:24:14 CEST] wrote: % % Maybe I completely miss your point, as I am not sure why you would % want to do that. % % ...because I'm lazy. But I could think of other purposes as % well for a ``real'' batch mode, for example, when I want to % forward a bunch of mails to same address: inline and and one % by one. Maybe a tag-prefix pipe-message thru formail -r and hand to sendmail? You could even throw it into the background, like I do with what I hand to Vipul's Razor. % % Cheers, Rocco HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28565/pgp0.pgp Description: PGP signature
Re: Two questions
Hi, * David T-G [2002-06-04 13:28:28 CEST] wrote: ...and then Rocco Rutte said... % ...because I'm lazy. But I could think of other purposes as % well for a ``real'' batch mode, for example, when I want to % forward a bunch of mails to same address: inline and and one % by one. Maybe a tag-prefix pipe-message thru formail -r and hand to sendmail? Wouldn't that send out just empty messages because I had no chance putting in some text? You could even throw it into the background, like I do with what I hand to Vipul's Razor. To clear things a little up, it was only a side note that ``;'' can only perform an action on all tagged messages while doing it one-by-one is not possible. Nothing more. Anyway, let me add that it's kind of funny how creative some people are in solving non-existing problems. ;-) I think we can stop this discussion right now... Cheers, Rocco
Re: Two questions
Rocco, et al -- ...and then Rocco Rutte said... % % Hi, Hello! % % * David T-G [2002-06-04 13:28:28 CEST] wrote: % ...and then Rocco Rutte said... % % ...because I'm lazy. But I could think of other purposes as % % well for a ``real'' batch mode, for example, when I want to % % forward a bunch of mails to same address: inline and and one % % by one. % % Maybe a tag-prefix pipe-message thru formail -r and hand % to sendmail? % % Wouldn't that send out just empty messages because I had no % chance putting in some text? Oh, right. Sorry. I often forward stuff without preamble anyway. % % You could even throw it into the background, like I do % with what I hand to Vipul's Razor. % % To clear things a little up, it was only a side note that % ``;'' can only perform an action on all tagged messages % while doing it one-by-one is not possible. Nothing more. Right. So you offload the one-by-one to something else... % % Anyway, let me add that it's kind of funny how creative some % people are in solving non-existing problems. ;-) Well, of course; those are the best, and nobody ever really disproves your solutions in practice! % % I think we can stop this discussion right now... No, wait! Not yet! % % Cheers, Rocco HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28572/pgp0.pgp Description: PGP signature
Re: Two questions
Adam -- ...and then Adam Fields said... % % I'm new to mutt (moving from mh-e), and I have two questions for which Welcome! % I can't find the answers in the docs. % % 1) Is there a way to open part of a folder? Say I have a folder with %2000 messages, and I want to only look at, say, 190-200? You can limit your view to just about any slice that you want, but you'll still be opening the whole folder (mbox, Maildir/, mh, MMDF) and so processing time can be tough. Fortunately, mutt is light and lean and fast, and lots of folks have *huge* folders (my mutt-users folder has just topped 10k messages! and is still quite responsive) without problems. % % 2) What's the right way to do batch refiling, particularly of mailing %lists? Is there a way to specify a save-hook based on To: rather %than From:? The actual best way is the same as when it is delivered: run it through procmail or another MDA. Otherwise you should probably tag a pattern and then save that bunch to wherever and go on to the next pattern. % % % Thanks! HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg28546/pgp0.pgp Description: PGP signature
Re: Two questions
Hi, * Adam Fields [EMAIL PROTECTED] [02-06-03 23:04]: 1) Is there a way to open part of a folder? Say I have a folder with 2000 messages, and I want to only look at, say, 190-200? You have to open the whole thing, but you can limit it to a subset afterwards. Use 'l'. 2) What's the right way to do batch refiling, particularly of mailing lists? Is there a way to specify a save-hook based on To: rather than From:? The save-hook has a default pattern, but you can also use another one. See $default_hook. Thorsten -- Der Leser hat's gut: Er kann sich seine Schriftsteller aussuchen. - Kurt Tucholsky
Re: Two questions
* On Mon, 03 Jun 2002, Adam Fields wrote:
1) Is there a way to open part of a folder? Say I have a folder
with 2000 messages, and I want to only look at, say, 190-200?
Open the folder, then do a limit ('l' by default) using the
pattern ~m 190-200.
2) What's the right way to do batch refiling, particularly of mailing
lists?
You could, for example, tag-pattern ('T' by default) all
messages over 2 weeks old using the pattern ~d 2w.
Then save (move) all tagged messages to another folder:
;s
--
John
Re: Two questions
Hi,
* John Iverson [2002-06-04 23:51:06 CEST] wrote:
* On Mon, 03 Jun 2002, Adam Fields wrote:
2) What's the right way to do batch refiling,
particularly of mailing lists?
You could, for example, tag-pattern ('T' by default) all
messages over 2 weeks old using the pattern ~d 2w.
Then save (move) all tagged messages to another folder:
;s
That is sort of ``batch'', I guess. I miss one-by-one
instead of all-at-once. It would be nice if I could tag
messages I want to reply to so that I can answer each
individual mail instead of a mass reply...
Cheers, Rocco
Re: Two questions
Hi. On Tue 2002-06-04 at 00:50:01 +0200, Rocco Rutte wrote: [...] That is sort of ``batch'', I guess. I miss one-by-one instead of all-at-once. It would be nice if I could tag messages I want to reply to so that I can answer each individual mail instead of a mass reply... Maybe I completely miss your point, as I am not sure why you would want to do that. I guess you want to tag messages as you first read the whole folder, and then start replying to the messages you picked before. You could tag the messages in question, then limit your view to tagged messages and hit reply for each of them. Considering the amount of typing involved for answering a message, I doubt that extra r (or g or L) does hurt. Does that help or do you want to archieve something else? Bye, Benjamin. -- [EMAIL PROTECTED] msg28550/pgp0.pgp Description: PGP signature
Re: Two questions
On Mon, Jun 03, 2002 at 04:36:35PM -0500, David T-G wrote: Welcome! Thanks! % I can't find the answers in the docs. % % 1) Is there a way to open part of a folder? Say I have a folder with %2000 messages, and I want to only look at, say, 190-200? You can limit your view to just about any slice that you want, but you'll still be opening the whole folder (mbox, Maildir/, mh, MMDF) and so processing time can be tough. Fortunately, mutt is light and lean and fast, and lots of folks have *huge* folders (my mutt-users folder has just topped 10k messages! and is still quite responsive) without problems. I don't see immediately how to do that. Can you elaborate about the possibilities here? I have noticed that it's pretty fast. I'm using my existing mh folders as-is; is there any info available on whether other folder types are faster? % % 2) What's the right way to do batch refiling, particularly of mailing %lists? Is there a way to specify a save-hook based on To: rather %than From:? The actual best way is the same as when it is delivered: run it through procmail or another MDA. Otherwise you should probably tag a pattern and then save that bunch to wherever and go on to the next pattern. My normal usage pattern is to look at all of the messages that come in, then file them. What I'm looking for is the Pegasus Mail concept of rules-based filing on main folder close. It seems I might be able to sort of replicate this with procmail by having the mail filtered and then picked up from the existing folder, but I'm a little fuzzy on that. I'm a little confused about reading new mail - from what I read, I thought that mutt would pick up my new mail from the spool file and put it in the mbox folder (+inbox), but it seems that when I open it, I'm working with the spool file directly, and then I can move read messages to the inbox on changing to another folder. Can you offer more explanation of what's going on here? How does this mesh with having procmail do the filtering? This reminds me of another question - is there an easy way to rescan the spoolfile for new mail (I have fetchmail running in daemon mode to pick it up off the pop server)? -- - Adam - Surgam, Inc. is a technology consulting firm with strong background in delivering scalable and robust enterprise web and IT applications. http://www.surgam.net
Re: Two questions
Adam--
...and then Adam Fields said...
%
% On Mon, Jun 03, 2002 at 04:36:35PM -0500, David T-G wrote:
% Welcome!
%
% Thanks!
*grin*
%
% % I can't find the answers in the docs.
% %
% % 1) Is there a way to open part of a folder? Say I have a folder with
% %2000 messages, and I want to only look at, say, 190-200?
%
% You can limit your view to just about any slice that you want, but you'll
% still be opening the whole folder (mbox, Maildir/, mh, MMDF) and so
% processing time can be tough. Fortunately, mutt is light and lean and
% fast, and lots of folks have *huge* folders (my mutt-users folder has
% just topped 10k messages! and is still quite responsive) without
% problems.
%
% I don't see immediately how to do that. Can you elaborate about the
% possibilities here?
I think that's been answered already; you'd type
l ~m190-200
while in the index and, voila, you'd see only those messages. You could
limit to multiple ranges (either ~m190-200 ~m250-300 ... or perhaps all
together like ~m190-200,250-300 ... try it and see :-) You could also
limit on multiple criteria, like all new messages less than two weeks old
from a certain list: ~N ~F somelist ~d2w (you'll have to check me on the
date spec; I don't use it much). You get the idea...
%
% I have noticed that it's pretty fast. I'm using my existing mh folders
% as-is; is there any info available on whether other folder types are
% faster?
There has been nearly endless discussion of Maildir/ and mbox on the
list, all waiting for you in the archives :-) I haven't seen much talk
of mh or MMDF, but searching for speed and folder might turn up
something for them, too.
%
% % 2) What's the right way to do batch refiling, particularly of mailing
% %lists? Is there a way to specify a save-hook based on To: rather
% %than From:?
%
% The actual best way is the same as when it is delivered: run it through
% procmail or another MDA. Otherwise you should probably tag a pattern and
% then save that bunch to wherever and go on to the next pattern.
%
% My normal usage pattern is to look at all of the messages that come
% in, then file them. What I'm looking for is the Pegasus Mail concept
Fair enough. Could you look at them in their own incoming folders and
then file them in their archive or already read folders, or perhaps
just leave the read messages right there with the new ones since mutt not
only shows new ones but also handles threads so elegantly?
% of rules-based filing on main folder close. It seems I might be able
% to sort of replicate this with procmail by having the mail filtered
% and then picked up from the existing folder, but I'm a little fuzzy on
% that.
I'd venture to say that that's what most people do. So you'd have
procmail sort by list into =F.mutt, =F.gnupg, =F.suse, and so on (where
the = is a shortcut for the mail folder and the F. prefix makes it easy
to specify a mailboxes line in your muttrc) and then you'd have a bunch
of folders catching new mail, with your spoolfile probably catching
anything that didn't get sorted otherwise. You start mutt either with no
arguments (into your spool file) or with a -y to browse the list of
mailboxes with new mail in them, and then pick one and start reading.
When you're finished reading that one, type 'c' to change folders, hit
tab a couple of times (IIRC), and you have your list of folders that need
attention and you continue on. As you exit each folder, you might leave
the messages in there or move them all to =OLD/F.mutt and so on so that
your incoming folders stay light; I don't bother, but instead peel off a
few thousand messages every six months and save them in my compressed
archive folder =Z/F.mutt.gz (I bet you can guess where I got the Z if
you've been around *NIX for a while).
%
% I'm a little confused about reading new mail - from what I read, I
% thought that mutt would pick up my new mail from the spool file and
% put it in the mbox folder (+inbox), but it seems that when I open it,
It will put it there when you're done with it.
% I'm working with the spool file directly, and then I can move read
Yep. It's there on the system and the mail has been delivered, so why
not work with it that way?
% messages to the inbox on changing to another folder. Can you offer
% more explanation of what's going on here? How does this mesh with
% having procmail do the filtering?
See above, or ask more questions for more details.
%
% This reminds me of another question - is there an easy way to rescan
% the spoolfile for new mail (I have fetchmail running in daemon mode to
% pick it up off the pop server)?
Check $timeout and $wait_key and perhaps some other fun settings in the
manual; in general, mutt should happily see new mail (as long as you're
not stuck in the pager) when or shortly after it arrives. If all else
fails, sync the mailbox ('$' by default) to force any changes you've made
and generate a reread -- but, again, you
Re: Two questions
Hi, * Benjamin Pflugmann [2002-06-04 01:24:14 CEST] wrote: Maybe I completely miss your point, as I am not sure why you would want to do that. ...because I'm lazy. But I could think of other purposes as well for a ``real'' batch mode, for example, when I want to forward a bunch of mails to same address: inline and and one by one. Cheers, Rocco
Re: Two questions (maildir and mailinig lists)
On Thu, Apr 26, 2001 at 07:33:43AM +0800, Horace G. Friend III typed: I'm using the mbox mailbox format. I'm also experiencing problem 2. I have always thought of it as a default of Mutt when dealing with incoming mail which originated from yourself such as your replies to mailing lists. RTFM index_format Well, would anyone know if problem no. 2 is indeed a problem or Mutt's default? If it is the latter, how can we change this behavior? -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Two questions (maildir and mailinig lists)
Horace G. Friend III wrote: On Mon, Apr 23, 2001 at 01:15:44PM +0300, Micha Berdichevsky wrote: 2. When I post to a mailing list, I see my messages (in the idnex) with the 'From' field saying 'To list@host' instead of my name. Any ideas? I'm using the mbox mailbox format. I'm also experiencing problem 2. I have always thought of it as a default of Mutt when dealing with incoming mail which originated from yourself such as your replies to mailing lists. Well, would anyone know if problem no. 2 is indeed a problem or Mutt's default? If it is the latter, how can we change this behavior? You'll want to take a look at the $index_format variable. Like many things in Mutt, the format of the index is highly configurable. Good luck. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Two questions (maildir and mailinig lists)
Hi. I have a couple of slightly annoying problems: 1. I'm using maildir, and the 'sent' folder messages apear at the index with 0 lines (I had the same thing will all folders, but it was fixed using the procmail lines count). Can it be fixed? 2. When I post to a mailing list, I see my messages (in the idnex) with the 'From' field saying 'To list@host' instead of my name. Any ideas? Thanks, Micha.
two questions
1. Is there a debug feature in mutt for the .muttrc files? I have a line in .muttrc that is giving an error and I can't find it. 2. I would like to set up Lynx or Netscape to view html mail. How do I do that. 3. bonus question. I can't get color to work. I know color works in the xterm, because mc works fine. I tried a couple suggestions in the mutt FAQ but neither worked. -- Fred
Re: two questions
On Thu, Mar 15, 2001 at 07:07:56AM -0500, F. Heitkamp wrote:
1. Is there a debug feature in mutt for the .muttrc files?
I have a line in .muttrc that is giving an error and I can't
find it.
When you say you can't find it what do you mean exactly?
When mutt reports an error in a muttrc file the error message is
usually pretty explicit. It gives the line number and a message
indicating what the error is.
If you're not getting a line number then I would suggest that it's
not a muttrc error. If you don't understand the error message then
please post the error here and we'll do our best! :-)
2. I would like to set up Lynx or Netscape to view html
mail. How do I do that.
I *think* most of what you need is a line in your .mailcap file
something like:-
text/html; lynx -force_html %s; needsterminal ; nametemplate=%s.html
3. bonus question. I can't get color to work. I know color
works in the xterm, because mc works fine. I tried a couple
suggestions in the mutt FAQ but neither worked.
Are you using S-Lang or ncurses, the answers may be different
according to which you are using ('mutt -v' will tell you).
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Re: Works good, two questions tho
On Sat, Jan 06, 2001 at 12:00:07AM -0800, Gary Johnson wrote: On Sat, Jan 06, 2001 at 07:17:18AM +0100, Petri Kelottij?rvi wrote: 2: How do I make Mutt start in, say, ~/Mail/mutt-users instead of the global mailbox? I'm sure this is in the docs but I can't find it, as usual :( In your muttrc file, put set spoolfile=~Mail/mutt-users folder-hook . set spoolfile=$MAIL That will start mutt in ~Mail/mutt-users, then immediately restore your spoolfile to the system mailbox. A simpler solution, if you don't mind typing extra characters each time you start mutt, or if you want to start mutt in different mailbox each time, would be to start it as mutt -f ~/Mail/mutt-users Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Works good, two questions tho
Hi again, sorry to bother you once more :P Mutt's been working absolutely wonderful, managing my mail just like I want it and with my favourite colours too :D But still, I have one...make it two, questions: 1: Does the scoring evaluate only the first occurrence of a score rule? Like if I have a rule to catch "abc", and I get a message "abc\nabc", would it get twice the amount of points as just "abc"? 2: How do I make Mutt start in, say, ~/Mail/mutt-users instead of the global mailbox? I'm sure this is in the docs but I can't find it, as usual :( Thanks once again, /petri
Re: Works good, two questions tho
On Sat, Jan 06, 2001 at 07:17:18AM +0100, Petri Kelottij?rvi wrote: 2: How do I make Mutt start in, say, ~/Mail/mutt-users instead of the global mailbox? I'm sure this is in the docs but I can't find it, as usual :( In your muttrc file, put set spoolfile=~Mail/mutt-users folder-hook . set spoolfile=$MAIL That will start mutt in ~Mail/mutt-users, then immediately restore your spoolfile to the system mailbox. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications Product Generation Unit | Spokane, Washington, USA
Two questions
I'm using mutt version 1.2i on a Solaris 7 platform with Sendmail 8.9.3 and have the following two questions: 1: When I compose a new message or reply, the message header in my editor has the following line: From: Jeffery Small jeff@ Notice the missing domain portion of the address. When the message is mailed the line ends up reading: From: Jeffery Small This is new behavior in this recent version of mutt. Is this a change that was made as some form of anti-spam measure? Is there a variable I can set to restore the proper behavior of inserting the correct address on the From: line? 2: I mentioned this once before but never got a reply. In most cases, I can use either TAB or SPACE for filename completion. However, when I 'c'hange to a new mailbox, the TAB key works but the SPACE key will not perform filename completion. Do other people observe this behavior? If not, is there some variable that controls this behavior? Thanks for your responses. Regards, -- Jeff C. Jeffery Small ArchitectCJSA LLC (206) 232-3338 [EMAIL PROTECTED] 7000 E Mercer Way, Mercer Island, WA 98040
