Re: your mail
On 20201024, Globe Trotter via Mutt-users wrote: An irritating thing right now is that if I hit q in error after composing a message, I get: Postpone message (yes/no) and if I say no, then the message appears lost. Is is possible to have an an option on this which should be to cancel the postpone question: perhaps a prompt that is [yes/no/cancel] Try ^G. I just tried it on this message and it does cancel the quit. You do have to type "e" to get back to editing. Or go ahead and postpone, then type "m" to send a new message. This notices the draft and asks if you want to work on that. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & wood chipper / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: your mail
On Thu, Oct 22, 2020 at 01:40:43AM +, Globe wrote in : My aoologies for the earlier attempts at sending e-mail. But I am new to mutt (as of today) and do not have my mailer set up and trying to get started. I hope this goes through in plain-text format. It did. But due to you using yahoo mail (not your fault) and the way yahoo has configured their domain, using a yahoo email address with mailing lists doesn't work too well. In this case it makes it harder for people to reply to your messages as your messages are being encapsulated in another message to work around this feature of yahoo. I can't tell for certain, but this might be why you haven't received a reply to your question yet. My set up is as follows: I use fetchmail and procmail to get my mail delivered to Maildir mailboxes. So,my mail is inside folders in ~/Maildir in the following manner: ~/Maildir/inbox ~/Maildir/sent ~/Maildir/drafts ~/Maildir/work/ ~/Maildir/work/user1 ~/Maildir/work/user2 ~/Maildir/bills ~/Maildir/family If these are all the mailboxes you have, it might be easiest to just include these "as is" in your .muttrc. So: mailboxes +inbox mailboxes +sent etc. etc. I want to show this tree on a side-pane. So, my initial attempt at .muttrc has the following: modified from mutt & Maildir Mini-HOWTO set mbox_type=Maildir set folder="~/Maildir" mailboxes `echo -n "+ "; find ~/Maildir -type d -name "*" -printf "+'%f' "` If you run the command between the two back ticks at the shell prompt, do you get the output you expect? I notice that it seems to add a "+ " at the very start without any further mailbox name before listing the other mailboxes. I wonder if this is what causes the unexpected behavior. You might want to leave the 'echo -n "+ ";' part out. However, when I launch mutt, I get nothing and after a lot of blank stares on-screen, I get: Mutt:/var/spool/mail/itsme [Msgs: 0 Inc: 20](date/date)(all)-- This is not what you would expect. As it shows, mutt opened /var/spool/mail/itsme instead of any of the folders you'd like it to. When you use the 'c' command, can you then open your folders such as ~/Maildir/inbox ?
Re: Default subject Re: your mail when replying to empty-subject e-mails
* On 21 Nov 2012, Marcelo Laia wrote: On 21/11/12 at 07:00pm, David Champion wrote: You could create a personal translation, I guess. Have any idea how to do? Only roughly (I haven't done it): create your own mutt.po file, override the right message in it, compile it with msgfmt, choose a locale name, put the resulting mutt.mo file in the proper location, set your locale to your custom locale name, run mutt. It turns out I'm wrong anyway though. Re: your mail is not localized in mutt's code. -- David Champion • d...@bikeshed.us
Re: Default subject Re: your mail when replying to empty-subject e-mails
2012/11/21 Will Yardley mutt-us...@veggiechinese.net: On Wed, Nov 21, 2012 at 01:41:02AM +0100, E. Prom wrote: When replying to an e-mail with an empty subject, the subject of the answer is set to Re: your mail. I thought it was configurable, but didn't find anything from a quick search in TFM. Also, it looks like it's hard-coded in send.c. Thanks Will, I will change it the day I'll decide to compile it myself... E.
Re: Default subject Re: your mail when replying to empty-subject e-mails
* On 21 Nov 2012, E. Prom wrote: 2012/11/21 Will Yardley mutt-us...@veggiechinese.net: On Wed, Nov 21, 2012 at 01:41:02AM +0100, E. Prom wrote: When replying to an e-mail with an empty subject, the subject of the answer is set to Re: your mail. I thought it was configurable, but didn't find anything from a quick search in TFM. Also, it looks like it's hard-coded in send.c. Thanks Will, I will change it the day I'll decide to compile it myself... You could create a personal translation, I guess. -- David Champion • d...@bikeshed.us
Re: Default subject Re: your mail when replying to empty-subject e-mails
On 21/11/12 at 07:00pm, David Champion wrote: You could create a personal translation, I guess. Have any idea how to do? -- Marcelo Brasil (Brazil, for English Speakers) Linux user number 487797
Default subject Re: your mail when replying to empty-subject e-mails
Hi, When replying to an e-mail with an empty subject, the subject of the answer is set to Re: your mail. I would like to customize/localize it, but it does not seem to be an option. Have I missed something? (No, I would prefer keeping using Debian's binaries ;-)
Re: Default subject Re: your mail when replying to empty-subject e-mails
On Wed, Nov 21, 2012 at 01:41:02AM +0100, E. Prom wrote: When replying to an e-mail with an empty subject, the subject of the answer is set to Re: your mail. I thought it was configurable, but didn't find anything from a quick search in TFM. Also, it looks like it's hard-coded in send.c. w
Change default Re: your mail subject when replying to blank subject
Hi, Is it possible to change the default Re: your mail subject that mutt uses when replying to emails that arrive without a subject to something less, er, passive aggressive -- or something in another language? Apologies if this is a FAQ, but it's rather difficult to Google, and I can find no mention in the manual. -- Mike
Re: Change default Re: your mail subject when replying to blank
On Mon, Nov 02, 2009 at 12:49:38PM -0400, Monte Stevens wrote: Is it possible to change the default Re: your mail subject that mutt uses when replying to emails that arrive without a subject to something less, er, passive aggressive -- or something in another language? You can edit the source send.c file. Look for: else if (!env-subject) env-subject = safe_strdup (Re: your mail); Change 'your mail' to 'whatever you like'; I use 'no subject'. Thanks, that works. Seems like the kind of thing that should be exposed to end user configuration rather than requiring the user to edit source code. I have raised a ticket: http://dev.mutt.org/trac/ticket/3349. -- Mike
Re: Change default Re: your mail subject when replying to blank
On 2009-11-02, Michael Williams willi...@astro.ox.ac.uk wrote: On Mon, Nov 02, 2009 at 12:49:38PM -0400, Monte Stevens wrote: Is it possible to change the default Re: your mail subject that mutt uses when replying to emails that arrive without a subject to something less, er, passive aggressive -- or something in another language? You can edit the source send.c file. Look for: else if (!env-subject) env-subject = safe_strdup (Re: your mail); Change 'your mail' to 'whatever you like'; I use 'no subject'. Thanks, that works. Seems like the kind of thing that should be exposed to end user configuration rather than requiring the user to edit source code. I have raised a ticket: http://dev.mutt.org/trac/ticket/3349. But changing that subject doesn't require the user to edit source code--the user can easily change it when prompted for the subject of the reply or from the compose menu. Further, if you're going to be picky about the subject, it should really reflect the subject of the message, not be just some generic equivalent of you forgot the subject. It hardly seems worth making this configurable. Regards, Gary
Re: Change default Re: your mail subject when replying to blank
On Mon, Nov 02, 2009 at 01:46:12PM -0800, Gary Johnson wrote: On 2009-11-02, Michael Williams willi...@astro.ox.ac.uk wrote: On Mon, Nov 02, 2009 at 12:49:38PM -0400, Monte Stevens wrote: Is it possible to change the default Re: your mail subject that [..] You can edit the source send.c file. Look for: [..] [..] Seems like the kind of thing that should be exposed to end user [..] But changing that subject doesn't require the user to edit source code--the user can easily change it when prompted for the subject of the reply or from the compose menu. I think the point of having a configurable default is so that we don't have to change it when prompted. I'd rather not have to type Re: my custom non-subject reply subject or whatever every time I reply to a message which had no subject. Further, if you're going to be picky about the subject, it should really reflect the subject of the message, not be just some generic equivalent of you forgot the subject. It hardly seems worth making this configurable. By that logic, why do we have the Re: your mail hard-coded default at all? Cheers, -- Noah Sheppard Assistant Computer Resource Manager Taylor University CSE Department nshep...@cse.taylor.edu
Re: Change default Re: your mail subject when replying to blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, November 2 at 05:13 PM, quoth Noah Sheppard: I think the point of having a configurable default is so that we don't have to change it when prompted. I'd rather not have to type Re: my custom non-subject reply subject or whatever every time I reply to a message which had no subject. Actually... couldn't you do that with a reply-hook? reply-hook '~s ^$' 'edit-subjectkill-lineMy Custom Headerenter' (I haven't tested that, of course) ~Kyle - -- You cannot reason a person out of a position he did not reason himself into in the first place. -- Jonathan Swift -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSu9cbCuveozR/AWeAQjBbBAAiZg/f2aHeVu+DEqD5kJziNNTexFAfxL2 mDxZBKNiNnFJYnxzPTXYuNxn2YM0iKCUKTY5/MtkmsAh7GdY42Tp1JU8q3QRC8do ELKxxwkSqJVO3wyQZVmM69QSwGpm7tcSLmHW5WxborG8Tu+UguFIb0XJUb93qQIr Zo80MKpEo7W40DnM8ci4j29SN4uShin/DT7MKTzf0JY8+Qhb4hJRGNigTiKCdSPM oGfIWdLhG7MxfkGs1wDVF1C9j/PmJeT+tlqOlGH+PbuTP0zdrDFgpFy2ueQSnpVj VAGQObGLe9FI4hiDvulN4fwMlvwplvTqUVsD8ulPQmOhmxNJRfvcsKAlcYn01nDz 6un0pS+bc5S2rp83nQ4QiAJKJMfScqjSTMq9M5+ODcIGIhgYoxSJmqu4XOi7bvsR 6X+d26deXlET9jiht00ZXirbYmQOwMpLNyohIeeP12T67fj0urdO199qBowuavN9 hjG7DsLFWWVscV/WEc/K8QfP101Ga6IFj5GxdDq0LI4yWqjSYEwF+NGSmxVCDPQ6 nhPFnaTV4U4F2woh0mRmXm9MJsSEuA99RDH0ML/rDw4j+OUbAEJDrEAMufgornWR wqPil/P3JcE2SxzaNN8Ud8lneHfvKjMP27Eqzy/dwfXVtWIDBmaYM+qKeIIqoggg HhXVzQ1abPw= =2JJH -END PGP SIGNATURE-
Re: Change default Re: your mail subject when replying to blank
On 17:13 Mon 02 Nov , Noah Sheppard wrote: On Mon, Nov 02, 2009 at 01:46:12PM -0800, Gary Johnson wrote: On 2009-11-02, Michael Williams willi...@astro.ox.ac.uk wrote: On Mon, Nov 02, 2009 at 12:49:38PM -0400, Monte Stevens wrote: Is it possible to change the default Re: your mail subject that [..] You can edit the source send.c file. Look for: [..] [..] Seems like the kind of thing that should be exposed to end user [..] But changing that subject doesn't require the user to edit source code--the user can easily change it when prompted for the subject of the reply or from the compose menu. I think the point of having a configurable default is so that we don't have to change it when prompted. I'd rather not have to type Re: my custom non-subject reply subject or whatever every time I reply to a message which had no subject. Further, if you're going to be picky about the subject, it should really reflect the subject of the message, not be just some generic equivalent of you forgot the subject. It hardly seems worth making this configurable. By that logic, why do we have the Re: your mail hard-coded default at all? Surely the easiest way is to 'set edit-headers' and change the Re: to whatever. Subjects evolve. -- Regards, John K Masters
Re: Change default Re: your mail subject when replying to blank
* Noah Sheppard nhshepp...@taylor.edu [11-02-09 17:15]: I think the point of having a configurable default is so that we don't have to change it when prompted. I'd rather not have to type Re: my custom non-subject reply subject or whatever every time I reply to a message which had no subject. ... By that logic, why do we have the Re: your mail hard-coded default at all? Good questions. It should default to *requiring* a subject and there would be no problem :^) -- Patrick Shanahan Plainfield, Indiana, USAHOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://counter.li.org
Re: Change default Re: your mail subject when replying to blank
On 2009-11-02, Noah Sheppard nhshepp...@taylor.edu wrote: On Mon, Nov 02, 2009 at 01:46:12PM -0800, Gary Johnson wrote: Further, if you're going to be picky about the subject, it should really reflect the subject of the message, not be just some generic equivalent of you forgot the subject. It hardly seems worth making this configurable. By that logic, why do we have the Re: your mail hard-coded default at all? Because at that point in the code, mutt has to do something about creating a subject for a reply to a message without a subject. Testing for and providing a reasonable solution for that rare case took two lines of code. The subject could have been simply Re: , but the author decided to make it a little nicer with Re: your mail, a difference of nine characters in a string. Doing any more than that to address the very narrow case of I don't want to bother changing the reply but I don't like the default, just seems to me like overkill. Of course, I can probably count on one hand the number of replies I've sent to messages without subjects. Regards, Gary
Re: Change default Re: your mail subject when replying to blank
On Mon, Nov 02, 2009 at 03:03:08PM -0800, Gary Johnson wrote: Doing any more than that to address the very narrow case of I don't want to bother changing the reply but I don't like the default, just seems to me like overkill. You're forgetting I don't want to bother changing the reply and my recipient (and I) do not correspond in English. In the absence of an option to change this string exposed to the user -- or a change mutt-wide to *require* a real subject for new messages and replies -- the hard-coded default in the source code should be changed to just the users current reply prefix (Re:, AW:, etc.). The current default subject happens to be badly worded (in my opinion), but at best it adds no useful information whatsoever to the email for English speakers, and adds noise for non-English speakers that must be manually removed. -- Mike
Re: Change default Re: your mail subject when replying to blank
On Mon, 02 Nov 2009, Michael Williams wrote: Is it possible to change the default Re: your mail subject that mutt I have no problem with that default, but the subject Re: your mail looks like a spam. -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Re: Change default Re: your mail subject when replying to blank
On Tue, Nov 3, 2009 at 8:27 AM, Michael Williams willi...@astro.ox.ac.uk wrote: You're forgetting I don't want to bother changing the reply and my recipient (and I) do not correspond in English. Mutt now supports internationalization, so for this purpose the developers could replace Re: your mail with _(Re: your mail) and leave this up to the translators? -- John C. McCabe-Dansted
Re: your mail
On Mon, Sep 09, 2002 at 04:25:18PM +0800, Isaac Claymore wrote: I need to email people at my company constantly, say foo.com. What I want is: whenever I write an email, I just supply jack as 'To:' to mutt, and mutt completes that as [EMAIL PROTECTED], it'll save me a lot typing. What works for me is: set hostname=domain.gumpf.etc# Is appended to local recipients. Regards, Erik
Re: your mail
On Mon, 09 Sep 2002, Isaac Claymore wrote:
--fine-- No HTML/RTF in email
--fine-- No M$ Word docs in email
Please put a subject when you write emails to the public.
Thanks
--
Lukas Ruf
http://www.lpr.chhttp://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
Re: your mail
On Mon, Sep 09, 2002 at 11:07:49AM +0200, Lukas Ruf wrote: Please put a subject when you write emails to the public. Sorry, it slipped my mind, and I've already commented that 'set abort_nosubject=no' out of my muttrc ;) -- Isaac Claymore /\ASCII Ribbon Campaign Dawning Inc.\ /Respect for open standards Beijing, China X No HTML/RTF in email http://www.dawning.com.cn / \No M$ Word docs in email
Re: your mail
Hi, * Mike Schiraldi [05/16/02 17:50:02 CEST] wrote: Also, using a subject line of URGENT!!! was pretty rude. Hmm, better than no subject... ;-) SCNR, Cheers, Rocco.
Re: your mail
On 18:50 16 May 2002, Rocco Rutte [EMAIL PROTECTED] wrote: | * Mike Schiraldi [05/16/02 17:50:02 CEST] wrote: | Also, using a subject line of | URGENT!!! was pretty rude. | | Hmm, better than no subject... ;-) Not really. Especially since a language setting isn't URGENT It's certainly frustrating and inconvenient, but if it were urgent he'd be asking someone and/or reading documentation. Mailing lists are often too slow, and if your problem is with your mail reader then a mailing list is not where I'd seek help first. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ Mountain rescue teams insist the all climbers wear helmets, and fall haedfirst. They are then impacted into a small globular mass easily stowed in a rucsac. - Tom Patey, who didnt, and wasnt
Re: your mail
Hi, On 17 May 2002, Cameron Simpson [EMAIL PROTECTED] wrote: On 18:50 16 May 2002, Rocco Rutte [EMAIL PROTECTED] wrote: | Hmm, better than no subject... ;-) Not really. Especially since a language setting isn't URGENT Especially since usually it's not urgent for someone who *reads* the message, and who usually does not like to be hurried at all. It's certainly frustrating and inconvenient, but if it were urgent he'd be asking someone and/or reading documentation. I just grepped the documentation for some mentioning of LC_*, LANG, or interpretation of environment variables in general, without any success. Perhaps some note should be added (or listed explicitely in the contents if it is indeed hidden somewhere in there and I just missed it). So long, Jochen. -- f u cn rd ths, u mst hv bn sng nx
Re: [OT] Re: your mail
...while adding other problems: Apologies for not getting back to the list with requested specs. My hard drive died and I've spent the last day or so getting things back to normal (whatever that is..) I haven't solved the X problem yet but I'm close. Thomas I followed your advice about inserting the XFree86 termcap and it worked.. Things were working fine in X.. thanks
[OT] Re: your mail
On Sun Jan 27, 2002 at 02:08:08PM -0800, Dale Morris wrote: Oh, if I'm in X using xterm, there's no color in mutt but I can backspace to delete text. If I'm in rxvt I have color in mutt but can't backspace/delete. Hi. If you're using xfree86/x-term, put the following in your ~/.Xdefaults (_instead_ of mucking around with $TERM): xterm*termName: xterm-color That should fix you no-colour while in x-term-problem. HTH -- Martin Karlsson martin.karlsson at visit.se
Re: your mail
On Sun, 27 Jan 2002, Will Yardley wrote: Thomas Dickey wrote: [this is getting OT, so it might be nicest to continue this discussion off list if necessary] I had in mind (having forgotten that FreeBSD has a not-invented-here mentality) that they'd implemented a copy of the GNU 'ls', and didn't consider that they may have fixed one problem while introducing another... is it gnu's ls? it isn't in /usr/src/gnu/bin - it's in /usr/src/bin, and has a standard BSD license at the top. also the options are different in freebsd - it's 'ls -G' not 'ls --color[=]'. I seem to recall some discussion that there was a port of the GNU ls, and that it was unsatisfactory (since it wasn't part of the base system). There was some related discussion regarding some incompatible changes made to the console's color handling - middle of last year iirc (the 3 *BSD's now have 3 incompatible flavors of the same console driver, making it hard to decide if I should reflect any of that in the terminfo database). The tone of the discussion however was that the color 'ls' was just-like-GNU (but-different-of-course). Part of the discussion was in newsgroups, part I saw in mailing lists via google. (I look at related discussions to see if there are problems for ncurses, etc.). Anyway, the color 'ls' you're talking about is not quite the same as in the FreeBSD 4.1 that I have (which doesn't mention xterm in the manpage, though it does have color support. I might recall that more readily, however I don't use that feature - 'ls' is useful for scripting, but I get color using my directory editor... -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: [OT] Re: your mail
On Mon, Jan 28, 2002 at 09:40:43AM +0100, Martin Karlsson wrote:
On Sun Jan 27, 2002 at 02:08:08PM -0800, Dale Morris wrote:
Oh, if I'm in X using xterm, there's no color in mutt but I can
backspace to delete text. If I'm in rxvt I have color in mutt but can't
backspace/delete.
Hi. If you're using xfree86/x-term, put the following in your
~/.Xdefaults (_instead_ of mucking around with $TERM):
xterm*termName: xterm-color
That should fix you no-colour while in x-term-problem.
...while adding other problems:
comparing xterm-color to xterm-xfree86.
comparing booleans.
OTbs: T:F.
bce: F:T.
mc5i: F:T.
npc: F:T.
comparing numbers.
comparing strings.
blink: NULL, '\E[5m'.
cbt: NULL, '\E[Z'.
civis: NULL, '\E[?25l'.
cnorm: NULL, '\E[?25h'.
ech: NULL, '\E[%p1%dX'.
el1: NULL, '\E[1K'.
enacs: '\E)0', '\E(B\E)0'.
flash: NULL, '\E[?5h$100/\E[?5l'.
hpa: NULL, '\E[%i%p1%dG'.
ich: NULL, '\E[%p1%d@'.
invis: NULL, '\E[8m'.
is2: '\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4l\E8\E', '\E[!p\E[?3;4l\E[4l\E'.
kDC: NULL, '\E[3;2~'.
kEND: NULL, '\EO2F'.
kHOM: NULL, '\EO2H'.
kIC: NULL, '\E[2;2~'.
kLFT: NULL, '\EO2D'.
kNXT: NULL, '\E[6;2~'.
kPRV: NULL, '\E[5;2~'.
kRIT: NULL, '\EO2C'.
kb2: NULL, '\EOE'.
kcbt: NULL, '\E[Z'.
kend: NULL, '\EOF'.
kent: NULL, '\EOM'.
kf1: '\E[11~', '\EOP'.
kf13: '\E[25~', '\EO2P'.
kf14: '\E[26~', '\EO2Q'.
kf15: '\E[28~', '\EO2R'.
kf16: '\E[29~', '\EO2S'.
kf17: '\E[31~', '\E[15;2~'.
kf18: '\E[32~', '\E[17;2~'.
kf19: '\E[33~', '\E[18;2~'.
kf2: '\E[12~', '\EOQ'.
kf20: '\E[34~', '\E[19;2~'.
kf21: NULL, '\E[20;2~'.
kf22: NULL, '\E[21;2~'.
kf23: NULL, '\E[23;2~'.
kf24: NULL, '\E[24;2~'.
kf25: NULL, '\EO5P'.
kf26: NULL, '\EO5Q'.
kf27: NULL, '\EO5R'.
kf28: NULL, '\EO5S'.
kf29: NULL, '\E[15;5~'.
kf3: '\E[13~', '\EOR'.
kf30: NULL, '\E[17;5~'.
kf31: NULL, '\E[18;5~'.
kf32: NULL, '\E[19;5~'.
kf33: NULL, '\E[20;5~'.
kf34: NULL, '\E[21;5~'.
kf35: NULL, '\E[23;5~'.
kf36: NULL, '\E[24;5~'.
kf37: NULL, '\EO6P'.
kf38: NULL, '\EO6Q'.
kf39: NULL, '\EO6R'.
kf4: '\E[14~', '\EOS'.
kf40: NULL, '\EO6S'.
kf41: NULL, '\E[15;6~'.
kf42: NULL, '\E[17;6~'.
kf43: NULL, '\E[18;6~'.
kf44: NULL, '\E[19;6~'.
kf45: NULL, '\E[20;6~'.
kf46: NULL, '\E[21;6~'.
kf47: NULL, '\E[23;6~'.
kf48: NULL, '\E[24;6~'.
kfnd: '\E[1~', NULL.
khome: NULL, '\EOH'.
kslt: '\E[4~', NULL.
mc0: NULL, '\E[i'.
mc4: NULL, '\E[4i'.
mc5: NULL, '\E[5i'.
op: '\E[m', '\E[39;49m'.
rmam: NULL, '\E[?7l'.
rmcup: '\E[2J\E[?47l\E8', '\E[?1049l'.
rmso: '\E[m', '\E[27m'.
rmul: '\E[m', '\E[24m'.
rs1: NULL, '\Ec'.
rs2: '\E7\E[r\E8\E[m\E[?7h\E[?1;3;4;6l\E[4l\E', '\E[!p\E[?3;4l\E[4l\E'.
setb: NULL,
'\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m'.
setf: NULL,
'\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m'.
sgr: NULL,
'\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\016%e\017%;'.
sgr0: '\E[m', '\E[m\017'.
smam: NULL, '\E[?7h'.
smcup: '\E7\E[?47h', '\E[?1049h'.
vpa: NULL, '\E[%i%p1%dd'.
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
Re: your mail
On Sun, Jan 27, 2002 at 02:08:08PM -0800, Dale Morris wrote: I've just recently installed FreeBSD. I've got most all of my mail functioning properly, but I'm having a problem with mutt. When I am in a console, the bottom messages don't appear. For example I enter q and at the bottom of the screen is a black spaced indent and then the cursor. No text. If I type y mutt quits. It sounds as if your choice of $TERM is resetting colors to black-on-black. I'm using mutt 1.25 and Roland Rosenfeld's .muttrc and setup files icewm-gnome .xinitrc .tcsh Oh, if I'm in X using xterm, there's no color in mutt but I can backspace to delete text. If I'm in rxvt I have color in mutt but can't backspace/delete. same problem (the terminfo entry tells the application what to expect for backspace - kbs - and delete - kdch1). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: your mail
Dale Morris wrote: [might be a good idea to use a subject line] I've just recently installed FreeBSD. I've got most all of my mail functioning properly, but I'm having a problem with mutt. When I am in a console, the bottom messages don't appear. For example I enter q and at the bottom of the screen is a black spaced indent and then the cursor. No text. If I type y mutt quits. did you build mutt from ports, or from source? if you built from the ports, you might specify the option to build with ncurses instead of slang. do you mean in the actual console, or in a terminal window? i don't have this problem in either case in a terminal window (usually Eterm) or on the console on my FreeBSD 4.4 machines. Also, my main mail machine is a linux box but I read it from FreeBSD and i don't have this problem here also. if you mean a terminal rather than the actual console, probably you have the wrong $TERM setting. if you're in the console, is $TERM set to cons25? I'm using mutt 1.25 and Roland Rosenfeld's .muttrc and setup files you might also include mutt -v output, and let us know what $TERM is set to anywhere you have the problem (echo $TERM in bourne derived shells; not sure about csh derived shells, but env | grep TERM will do it). Oh, if I'm in X using xterm, there's no color in mutt but I can backspace to delete text. If I'm in rxvt I have color in mutt but can't backspace/delete. i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. experiment with different TERM settings and terminal programs and see what works for you. personally i find Eterm nicer looking (after you mess with the default colors and stuff) than xterm or rxvt, although it can be a bit of a memory hog. w
Re: your mail
On Sun, Jan 27, 2002 at 02:24:22PM -0800, Will Yardley wrote: i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. xterm-color is always incorrect for xterm and rxvt... (it happens to work if you don't care much about how well). see http://dickey.his.com/xterm/xterm.faq.html#xterm_terminfo color 'ls' ignores the termcap and terminfo databases, btw. experiment with different TERM settings and terminal programs and see what works for you. personally i find Eterm nicer looking (after you mess with the default colors and stuff) than xterm or rxvt, although it can be a bit of a memory hog. Both (XFree86) xterm and rxvt implement default colors, have done so since long before Eterm was written. (There's no difference, except of course if you're setting $TERM to xterm-color for one of the latter). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: your mail
Thomas Dickey wrote: On Sun, Jan 27, 2002 at 02:24:22PM -0800, Will Yardley wrote: i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. xterm-color is always incorrect for xterm and rxvt... (it happens to work if you don't care much about how well). color 'ls' ignores the termcap and terminfo databases, btw. CLICOLOR Use ANSI color sequences to distinguish file types. See LSCOLORS below. In addition to the file types mentioned in the -F option some extra attributes (setuid bit set, etc.) are also displayed. The colorization is dependent on a terminal type with the proper termcap(5) capabilities. The default ``cons25'' console has the proper capabilities, but to display the colors in an xterm(1), for example, the TERM variable must be set to ``xterm-color''. Other terminal types may require similar adjustments. Colorization is silently disabled if the output isn't directed to a terminal unless the CLICOLOR_FORCE variable is defined. (from the 'ls' man page). in freebsd, colorized ls doesn't work with xterm (ie it will work if you're on a linux machine or something but not on the machine itself). i use Eterm, but haven't had any problems with xterm-color. i know that it's incorrect, but it works for me ok. if anyone knows a better workaround, let me know. w
Re: your mail
On Sun, Jan 27, 2002 at 02:50:16PM -0800, Will Yardley wrote: Thomas Dickey wrote: On Sun, Jan 27, 2002 at 02:24:22PM -0800, Will Yardley wrote: i usually use xterm-color in FreeBSD even though you really shouldn't ever use 'xterm-color' since color 'ls' only works (AFAIK) when $TERM is set to this. on linux, i use xterm-xfree86, or sometimes just xterm. It's trivial to fix this (FreeBSD's termcap is badly-undermaintained). All you need to do is take the termcap that's part of the xterm distribution, paste it at the front of your /usr/share/misc/termcap, and regenerated the termcap database. Any competant sys-admin can do this. xterm-color is always incorrect for xterm and rxvt... (it happens to work if you don't care much about how well). color 'ls' ignores the termcap and terminfo databases, btw. I had in mind (having forgotten that FreeBSD has a not-invented-here mentality) that they'd implemented a copy of the GNU 'ls', and didn't consider that they may have fixed one problem while introducing another... CLICOLOR Use ANSI color sequences to distinguish file types. See LSCOLORS below. In addition to the file types mentioned in the -F option some extra attributes (setuid bit set, etc.) are also displayed. The colorization is dependent on a terminal type with the proper termcap(5) capabilities. The default ``cons25'' console has the proper capabilities, but to display the colors in an xterm(1), for example, the TERM variable must be set to ``xterm-color''. Other it's still wrong even if it's in the manpage (I think I'm more familiar with this stuff than the ostensible author of this manpage). i use Eterm, but haven't had any problems with xterm-color. i know that it's incorrect, but it works for me ok. you won't get default colors (by anything that relies on the termcap settings). hardcoded programs, of course, are not affected. if anyone knows a better workaround, let me know. I haven't been counting, but I'm certain I've mentioned it at least once a week for the past year. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net
Re: your mail
Thomas Dickey wrote: [this is getting OT, so it might be nicest to continue this discussion off list if necessary] I had in mind (having forgotten that FreeBSD has a not-invented-here mentality) that they'd implemented a copy of the GNU 'ls', and didn't consider that they may have fixed one problem while introducing another... is it gnu's ls? it isn't in /usr/src/gnu/bin - it's in /usr/src/bin, and has a standard BSD license at the top. also the options are different in freebsd - it's 'ls -G' not 'ls --color[=]'. it's still wrong even if it's in the manpage (I think I'm more familiar with this stuff than the ostensible author of this manpage). perhaps (i'm not being sarcastic), but the fact of the matter is that if i have TERM set to ANYTHING other than 'xterm-color', LS output doesn't show up in color. i don't know any way to prove this, but that's the case. i don't think it has to do with the terminal settngs not being capable. i will try regenerating my termcap database and stuff. i appreciate your (generally helpful) commentary on this list. i do think that perhaps you sometimes assume that other people know more about this stuff than most people actually do. while i like to do things the Right Way, i'm more interested in results; using xterm-color hasn't caused me any problems that bother me, so i'm not overly concerned about it. i will review the documenation on your site; if you have links to any other docs that might be helpful (especially freebsd specific, as their termcap database does seem to be kind of wacky) i'd appreciate those links as well. w
Re: your mail
* On Mon Apr 16 2001, Robert T.G. Tan screamed: - I've entered some colors in my .muttrc file, but they don't - show up in Eterm, a color monitor I'm using. - - So what's up with that? - - Tnx, rotan. Check the $TERM var. It should be set to 'linux' not 'xterm' --- Nelson D. Guerrero Platinom.NET Dominicana | E-Mail: [EMAIL PROTECTED] Cub Scout #42, Ens. Naco| Tel: (809) 567-4600 Santo Domingo, Dominican Republic | WWW: http://www.platinom.net -
Re: your mail
On Wed, 18 Apr 2001, Nelson D. Guerrero wrote: * On Mon Apr 16 2001, Robert T.G. Tan screamed: - I've entered some colors in my .muttrc file, but they don't - show up in Eterm, a color monitor I'm using. - - So what's up with that? - - Tnx, rotan. Check the $TERM var. It should be set to 'linux' not 'xterm' run infocmp Eterm linux to see why this is bad advice. -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: your mail
Well, passing the message to a very simple one line script seems to work. I made a ~/.mutt/mailout (mode +x to make it executable): #!/bin/sh cat | procmail ~/.procoutrc # End of ~/.mutt/mailout [Splutter] Useless Use of cat.
Re: your mail
On Mon, Mar 12, 2001 at 02:00:02AM -0500, Mark Spivak wrote: What would be the .muttrc directive to disable the lame "no subject. abort? ([y]/n)" prompt? from the manual : abort_nosubject Type: quadoption Default: ask-yes If set to yes, when composing messages and no subject is given at the subject prompt, composition will be aborted. If set to no, composing messages with no subject given at the subject prompt will never be aborted. barry -- http://www.theshining.org
about subject lines : Re: your mail
Mark Spivak proclaimed on mutt-users that: What would be the .muttrc directive to disable the lame "no subject. abort? ([y]/n)" prompt? set abort_nosubject=no -s (who still thinks it's lame not to use a subject line on posts to a list) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin I block all posts from WebTV with a filter, they make AOL look like MIT's computing dept. -- Old Salt
Re: your mail
On Mon, Mr 12, 2001 at 02:00:02AM -0500, Mark Spivak wrote: What would be the .muttrc directive to disable the lame "no subject. abort? ([y]/n)" prompt? set abort_nosubject=no beware: subjects are a netiquette topic. there's a reason because this is the default.
Re: your mail
On Mon, Feb 19, 2001 at 09:39:33AM -0600, Craig Neuwirt wrote: Can mutt be configured to work over a firewall with a proxy server. Yes.
Re: your mail
Craig Neuwirt proclaimed on mutt-users that: Can mutt be configured to work over a firewall with a proxy server. Use fetchmail (or .forward files or whatever) to move mail to your box from the mailserver. Then use sendmail (which should be configured to go through the proxy) to send out mail. If you have a central pop and smtp server, set up fetchmail, and sendmail (or even ssmtp, masqmail etc) to smarthost through your central smtp server. -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: your mail
Nelson [[EMAIL PROTECTED]] wrote: What do I have to add to my .muttrc to make it check only the mbox type files on ~/mail? I currentlly have mailboxes =Mutt =Inbox Why don't you try - mailboxes`echo ~/mail/*` In my muttrc it works just fine. Markus -- PGP/GPG-Key |E-Mail To Subject |oooO Oooo available || ( ) ( ) on request|PGP - [EMAIL PROTECTED] Send Key|\ ( ) / |GPG - [EMAIL PROTECTED] Send Key| \_) (_/
Re: your mail
* On Tue Feb 13 2001, Nelson D. Guerrero screamed: - Florian, It's not that...It works fine, it detects all my mailboxes - correctlly using my command... - - I want to know is how to set it to look like this: - - -- Mutt: Mailboxes [2] - - instead of this: - - -- Mutt: Directory [~/mail], File mask: !^\.[^.] Ok, here's what I want to do. I want my browser to show only the mailboxes I specified on my ~/.muttrc, just as if I was typing Tab on the browser itself. But I want it to be default. I can't find a damn thing on the example muttrc or 'man muttrc'. --- Nelson D. Guerrero| E-Mail: [EMAIL PROTECTED] Platinom.NET Dominicana | Phone: (809) 567-4600 Dialup / Web Hosting / E-Commerce |WWW: http://www.platinom.net/
Re: your mail
* On Tue Feb 13 2001, Florian Friesdorf screamed: - - mailboxes `for i in ~/mail/*; do test -f $i echo -n $i; done; echo` - - untested but should work. - You can use this in a second mailboxes line. - - -ff - - -- - Florian Friesdorf [EMAIL PROTECTED] - OpenPGP key available on public key servers - Florian, It's not that...It works fine, it detects all my mailboxes correctlly using my command... I want to know is how to set it to look like this: -- Mutt: Mailboxes [2] instead of this: -- Mutt: Directory [~/mail], File mask: !^\.[^.] --- Nelson D. Guerrero| E-Mail: [EMAIL PROTECTED] Platinom.NET Dominicana | Phone: (809) 567-4600 Dialup / Web Hosting / E-Commerce |WWW: http://www.platinom.net/
Re: your mail
On Tue, Feb 06, 2001 at 07:06:30AM +0530, Suresh Ramasubramanian wrote: On Tue, Feb 06, 2001 at 02:24:16AM +0100, Waldemar Brodkorb typed: On Mon, Feb 05, 2001 at 04:43:12PM +0100, Daniel Kollar wrote: Normally, mutt encrypts an email for all persons mentioned in the "To:" header automatically. and although in the Cc: header. But what todo if there's a small mailinglist with 3-5 persons, for example [EMAIL PROTECTED] . How I manage this? An alias in sendmail, perhaps? Never tried it :) And anyway, encrypting mail sent to a list is not exactly a very good idea (unless there's a common "list key" given only to list members, for a small list it'd work) Why not, there at the moment 3 friends of me, and we want to dicuss about a project secure. O.K. the solution is to create an alias group name1 name2 name3 That works. Thanks Daniel Kollar. -- MfG Waldemar Brodkorb Every Generation got its own disease - Fury in the Slaughterhause 1993 and we got Aquired Immunodeficiency Syndrome, Bovine Spongiform Encephalopathy and Microsoft Windows 2000 Professional
Re: your mail
Normally, mutt encrypts an email for all persons mentioned in the "To:" header automatically. On Sun, Feb 04, 2001 at 03:56:41PM +0100, Waldemar Brodkorb wrote: Date: Sun, 4 Feb 2001 15:56:41 +0100 From: Waldemar Brodkorb [EMAIL PROTECTED] To: [EMAIL PROTECTED] Mail-Followup-To: [EMAIL PROTECTED] Hello Mutt-User, is it possible to encrypt messages to more then one person out of Mutt? I know I could use gpg -d text.asc -r person1 -r person2 and send it as Attachment, but this is not very elegant. The toggle function did'nt work in the key-id-select window. Any idea's? -- MfG Waldemar Brodkorb Linux rulez !
Re: your mail
On Mon, Feb 05, 2001 at 04:43:12PM +0100, Daniel Kollar wrote: Normally, mutt encrypts an email for all persons mentioned in the "To:" header automatically. and although in the Cc: header. But what todo if there's a small mailinglist with 3-5 persons, for example [EMAIL PROTECTED] . How I manage this? -- MfG Waldemar Brodkorb Linux rulez !
Re: your mail
On Tue, Feb 06, 2001 at 02:24:16AM +0100, Waldemar Brodkorb typed: On Mon, Feb 05, 2001 at 04:43:12PM +0100, Daniel Kollar wrote: Normally, mutt encrypts an email for all persons mentioned in the "To:" header automatically. and although in the Cc: header. But what todo if there's a small mailinglist with 3-5 persons, for example [EMAIL PROTECTED] . How I manage this? An alias in sendmail, perhaps? Never tried it :) And anyway, encrypting mail sent to a list is not exactly a very good idea (unless there's a common "list key" given only to list members, for a small list it'd work) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: your mail
Bruce Simms [EMAIL PROTECTED] wrote on Tue, 16 May 2000: I'm using mutt version 0.95.4.us to send mail with attachments in a command line and it works well, but I would like to have the email have a different From: as I'm using this in a cron job I would like to have the ability to change this when mutt is run. Example of my current string. mutt [EMAIL PROTECTED] -s "This is a test" -a test.pdf test1.msg Any suggested solutions? Sure. Either add a "my_hdr From" line in your .muttrc (you can create a separate .muttrc just for this purpose and then source it with -F, if needed), or use -e on the command line to execute the my_hdr command. For more info, look up my_hdr in the manual. BTW, questions like this are better posted to mutt-users, not mutt-dev. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Caution: breathing may be hazardous to your health.
Re: your mail
On Thu, May 11, 2000 at 02:05:48AM -0500, Carlos Puchol wrote: alternatively, are there any suggestions of some place to get some decent (s)rpms that of mutt 1.2? Do you insist do get a (s)rpm? If not, i would recommend to get the .tar.gz and build it yourself, as described in the docs. You can use rpmfind, too. HTH Frank
Re: your mail
On Thu, 11 May 2000, Carlos Puchol wrote:
| hi, thanks for your tip.
| it looks like the problematic part of the rpm spec is this one:
|
| %install
| rm -rf $RPM_BUILD_ROOT
| make prefix=$RPM_BUILD_ROOT/usr \
| sharedir=$RPM_BUILD_ROOT/etc \
| sysconfdir=$RPM_BUILD_ROOT/etc \
| docdir=$RPM_BUILD_ROOT/usr/doc/mutt-%{version} install
|
| i don't know much about rpms, but
| i have tried removing the $RPM_BUILD_ROOT, and what
| happens is that when the install time comes,
| it tries to overwrite stuff in /etc, naturally, however,
| i always compile rpms as a uder, never as root, to
| prevent percisely these kinds of security violations.
| do you have any suggestions?
It is the $RPM_BUILD_ROOT that allows users to build rpms. The install is
all done under $RPM_BUILD_ROOT and then that prefix is stripped by by RPM
in the %files section. The problem arises when somebody hardcodes a path
that should be $RPM_BUILD_ROOT into part of the spec file.
| alternatively, are there any suggestions of
| some place to get some decent
| (s)rpms that of mutt 1.2?
| thanks for your help,
|
| ++ carlos
Your Mail to C C Survey Vessel
This is an automated message from C C's satellite E-Mail system. Your E-Mail message has been delivered. Your message contains attachments. Please send attachments only if required for operations. Thank you for your cooperation, C C's E-Mail Computer The e-mail message follows: - Received: from buffy.tpgi.com.au([203.12.160.34]) (2198 bytes) by kraken.cctechnol.com via sendmail with P:esmtp/R:batch_it/T:batch_smtp (sender: [EMAIL PROTECTED]) id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Wed, 29 Mar 2000 20:17:11 -0600 (CST) (Smail-3.2.0.111 2000-Feb-17 #2 built 2000-Mar-20) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.9.3/8.9.3) id MAA18448 for [EMAIL PROTECTED]; Thu, 30 Mar 2000 12:17:00 +1000 Received: from bri2-56k-098.tpgi.com.au(203.29.144.98), claiming to be "serra" via SMTP by buffy.tpgi.com.au, id smtpdKbkZme; Thu Mar 30 12:16:49 2000 Received: by serra (sSMTP sendmail emulation); Thu, 30 Mar 2000 12:23:05 +1000 Date: Thu, 30 Mar 2000 12:23:04 +1000 From: Darrin Mison [EMAIL PROTECTED] To: Sam Alleman [EMAIL PROTECTED] Subject: Re: update encoding? Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" X-Mailer: Mutt 1.0i In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Wed, Mar 29, 2000 at 10:45:23PM +0900 X-Operating-System: Linux serra 2.2.12-20 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable guessing here, but you use pgp to sign a message which=20 you have postponed and then you get this when you send=20 it again. Don't know how to avoid it or if to. As Sam Alleman[EMAIL PROTECTED] once said: =20 Hello again, =20 Can anyone tell me what this message is all about: =20 ~~/tmp/mutt-xena-22566-0 [#1] modified. Update encoding? ([y]/n): =20 What does this mean, and is there any way to bypass this question? Thanks. =20 Sam -- Darrin Mison --=20 "Necessity is the mother of invention" is a silly proverb. "Necessity is the mother of futile dodges" is much nearer the truth. -- Alfred North Whitehead --opJtzjQTFsWo+cga Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEAREBAAYFAjjiuogACgkQbJuZmIkY3S6B5ACeMgFDnAoSqSP099T75Tq0D+xm 7JAAn0LT5oLioplDYNnuZyM15xGI2UV2 =//v7 -END PGP SIGNATURE- --opJtzjQTFsWo+cga-- .
Re: your mail
On Tue, Jan 25, 2000 at 02:02:50PM -, andy scaplehorn wrote: is it possible to use mutt on sco os5 could you point me in the direction of some where i can get information. http://www.mutt.org/download.html download it and try to build. -- Ralf Hildebrandt [EMAIL PROTECTED] www.stahl.bau.tu-bs.de/~hildeb Like medieval peasants, computer manufacturers and millions of users are locked in a seemingly eternal lease with their evil landlord, who comes around every two years to collect billions of dollars of taxes in return for mediocre services. --Mark Harris, Electronics Times
Re: your mail
On Sun, Jan 23, 2000 at 07:19:20PM +0200, Mikko Hänninen wrote: You can have that by setting the order to "unsorted" (which obviously isn't truly unsorted). This of course has the drawback that your file browser is then in the unsorted order, not alphabetical... I admit that I prefer having my mailboxes sorted than having my file browser unsorted :) As a moderately well working work-around, I have this macro that I use: macro index i ":set sort_browser=unsorted\nc?\t:set sort_browser=alpha\n" "show (change to) incoming folders" Well, that's perfect, thanks for your help, that's now in my macros ... -- Stephane ENTEN
