question on mime types
so i have application/pdf pdf in the mime.types file for mutt. but when i attatch a pdf file, it doesn't pick up that its a pdf file. same holds for ps files, but not for gz files (as it detects the octet stream.) i have changed the default location of the mime.types file at compile time to a different directory than normal, but that was at compile time, so i dont see how that would be a problem. ideas? i checked the archives, but didn't see anything offhand which was the same problem im dealing withthanks in advance. -- thanks adam Drink tea, there's lots of tea. any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: solaris + linux
On Fri, Jul 06, 2001 at 11:34:04AM +1000, David wrote: On Thu, 05 Jul 2001, adam morley wrote: i have no experience with cmdtool, but dtterm does color fine. what dont you like about it? I have to use either xterm-color or dtterm at uni as the xterm there is very old and doesn't do colour. I find that dtterm does colour alright but it doesn't seem to setup the end and home keys properly. i dont like to move my hand over there, so ive never noticed that. have you had any luck getting it to bind them right? (or have you tried at all?) what do you use home/end for in mutt? -- Don't tell me I'm burning the candle at both ends -- tell me where to get more wax!! - David Clarke [EMAIL PROTECTED] | David Clarke s3353950 GPG Fingerprint : 869B 53DD 5E80 E1F0 93F6 9871 0508 0296 5957 F723 -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: solaris + linux
On Fri, Jul 06, 2001 at 09:28:02AM -0700, Carl B . Constantine wrote: * David ([EMAIL PROTECTED]) wrote: On Thu, 05 Jul 2001, adam morley wrote: i have no experience with cmdtool, but dtterm does color fine. what dont you like about it? I have to use either xterm-color or dtterm at uni as the xterm there is very old and doesn't do colour. I find that dtterm does colour alright but it doesn't seem to setup the end and home keys properly. I also use dtterm on Solaris (at least until I install Gnome for it). Not only does it not set up the home and end keys properly, but pgup and pgdn scroll the window as opposed to the text stream which is also a pain in the butt. i have to admit, i like the page up/page down like they are in dtterm too. However, now that I have ncurses-5.2 working (Thanks Tom!) mutt and vim colors work great. what did you need ncurses 5.2 for? im actually not using ncurses, and i have no troubles. -- Carl B. Constantine University of Victoria Programmer Analysthttp://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: solaris + linux
On Fri, Jul 06, 2001 at 01:49:01PM -0700, Carl B . Constantine wrote: * adam morley ([EMAIL PROTECTED]) wrote: However, now that I have ncurses-5.2 working (Thanks Tom!) mutt and vim colors work great. what did you need ncurses 5.2 for? im actually not using ncurses, and i have no troubles. for proper terminfo and colorization. You might be using slang instead of ncurses, but ncurses works great for me. that might be why i had to use funky color names...i think im actually using the svr4 curses, but im not sure. (maybe ncruses/slang is hiding on here somewhere) -- Carl B. Constantine University of Victoria Programmer Analysthttp://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: solaris + linux
On Thu, Jul 05, 2001 at 10:41:10AM -0400, Rich Lafferty wrote: On Thu, Jul 05, 2001 at 11:34:20PM +0200, Jesper Holmberg ([EMAIL PROTECTED]) wrote: Suresh: thanks, vt100 seems to work the best. I haven't figured out how to get color out of an xterm under Solaris anyway, so the black and white means to loss of quality. Purge your Solaris box of its ancient xterm! I've had luck with rxvt, id agree, the xterm with solaris is probably a hold over from way back when. although if you're a real purist, the xterm-color atftp.x.org:/contrib should work too. (And don't even think about dtterm or cmdtool.) i have no experience with cmdtool, but dtterm does color fine. what dont you like about it? -Rich -- Rich Lafferty --+--- Montreal, Quebec, Canada | Do not dangle the mouse by the cord or http://www.lafferty.ca/| throw it at coworkers. -- SGI Indy manual [EMAIL PROTECTED] ---+--- -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: solaris + linux
On Thu, Jul 05, 2001 at 02:57:10PM -0400, adam morley wrote: On Thu, Jul 05, 2001 at 10:41:10AM -0400, Rich Lafferty wrote: On Thu, Jul 05, 2001 at 11:34:20PM +0200, Jesper Holmberg ([EMAIL PROTECTED]) wrote: Suresh: thanks, vt100 seems to work the best. I haven't figured out how to get color out of an xterm under Solaris anyway, so the black and white means to loss of quality. Purge your Solaris box of its ancient xterm! I've had luck with rxvt, id agree, the xterm with solaris is probably a hold over from way back when. although if you're a real purist, the xterm-color atftp.x.org:/contrib should work too. (And don't even think about dtterm or cmdtool.) i have no experience with cmdtool, but dtterm does color fine. what dont you like about it? replying to my own post well, not exactly fine, but it does color. -Rich -- Rich Lafferty --+--- Montreal, Quebec, Canada | Do not dangle the mouse by the cord or http://www.lafferty.ca/| throw it at coworkers. -- SGI Indy manual [EMAIL PROTECTED] ---+--- -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Color Errors on Solaris
On Wed, May 23, 2001 at 05:11:39PM -0700, Igor Pruchanskiy wrote: mutt -v | grep System does it say [ncurses 4.2] or something like that ? if it does default should do, if you have no ncurses, i do not believe that it knows what default color is You can replace default with black or whatever you like, then it should not complain... again, i think he's getting the /usr/lib/libcurses.so in the mix (which i thought was svr4 curses) If you do not have ncurses i recommend that you go to www.sunfreeware.com and get yourself an ncurses package and then install it. after that recompile mutt and it should be able to find your ncurses and compile against it. after that you can set your TERMINFO env to point to /usr/local/share/terminfo since this is where ncurses will install all the terminfo entries and you can also set your TERM to color_xterm and then default will work just fine... I actually had to go through it this morning i wouldn't set the term to color_xterm, as thats not what dtterm is. if you want color_xterm, run a colr xterm igor On Wed 23 May 2001, Carl B . Constantine wrote: I've compiled Mutt 1.2.5 for Solaris 8 and do have some colors working in dtterm with a couple exceptions. First, anyone know how to get the standard dtterm to act more like the standard xterm with a black background? the inverse video in the options looks horrible with ANSI colors. Ok, now for my main problem. I'm getting the following errors when I start up mutt: (cconstan@viper): ~% src/mutt-1.2/mutt Error in /home/cconstan/.muttrc, line 283: default: no such color Error in /home/cconstan/.muttrc, line 284: default: no such color Error in /home/cconstan/.muttrc, line 285: default: no such color Error in /home/cconstan/.muttrc, line 286: default: no such color Error in /home/cconstan/.muttrc, line 287: default: no such color Error in /home/cconstan/.muttrc, line 289: default: no such color Error in /home/cconstan/.muttrc, line 290: default: no such color Error in /home/cconstan/.muttrc, line 291: default: no such color Error in /home/cconstan/.muttrc, line 292: default: no such color Error in /home/cconstan/.muttrc, line 293: default: no such color Error in /home/cconstan/.muttrc, line 294: default: no such color Error in /home/cconstan/.muttrc, line 295: default: no such color Error in /home/cconstan/.muttrc, line 296: default: no such color Error in /home/cconstan/.muttrc, line 297: default: no such color Error in /home/cconstan/.muttrc, line 298: default: no such color Error in /home/cconstan/.muttrc, line 299: default: no such color Error in /home/cconstan/.muttrc, line 300: default: no such color Error in /home/cconstan/.muttrc, line 301: default: no such color Error in /home/cconstan/.muttrc, line 302: default: no such color Error in /home/cconstan/.muttrc, line 305: default: no such color Error in /home/cconstan/.muttrc, line 312: default: no such color Error in /home/cconstan/.muttrc, line 315: default: no such color Error in /home/cconstan/.muttrc, line 316: default: no such color Error in /home/cconstan/.muttrc, line 317: default: no such color Error in /home/cconstan/.muttrc, line 318: default: no such color Error in /home/cconstan/.muttrc, line 319: default: no such color Error in /home/cconstan/.muttrc, line 320: default: no such color Error in /home/cconstan/.muttrc, line 321: default: no such color Error in /home/cconstan/.muttrc, line 322: default: no such color Error in /home/cconstan/.muttrc, line 324: default: no such color Error in /home/cconstan/.muttrc, line 326: default: no such color Error in /home/cconstan/.muttrc, line 327: default: no such color Error in /home/cconstan/.muttrc, line 328: default: no such color Error in /home/cconstan/.muttrc, line 329: default: no such color Error in /home/cconstan/.muttrc, line 330: default: no such color Error in /home/cconstan/.muttrc, line 331: default: no such color Error in /home/cconstan/.muttrc, line 333: default: no such color Error in /home/cconstan/.muttrc, line 334: default: no such color Error in /home/cconstan/.muttrc, line 335: default: no such color Error in /home/cconstan/.muttrc, line 337: default: no such color Error in /home/cconstan/.muttrc, line 338: default: no such color Error in /home/cconstan/.muttrc, line 339: default: no such color Error in /home/cconstan/.muttrc, line 340: default: no such color Error in /home/cconstan/.muttrc, line 341: default: no such color Press any key to continue... here is the relevant section(s) of my ~/.muttrc: ## = ## Color definitions ## = color attachment white magenta color body cyan default ftp://[^ ]* color body brightgreen default [[:alnum:]][-+.#_[:alnum:]]*@[-+.[:alnum:]]*[[:alnum:]] color body cyan default URL:[^ ]* color bold green default color
Re: Color Errors on Solaris
On Wed, May 23, 2001 at 05:42:43PM -0700, Carl Constantine wrote: On 5/23/01 17:11, Igor Pruchanskiy at [EMAIL PROTECTED] wrote: I'm on this list from home and work, so... ;-) after that you can set your TERMINFO env to point to /usr/local/share/terminfo since this is where ncurses will install all the terminfo entries and you can also set your TERM to color_xterm and then default will work just fine... I actually had to go through it this morning With this work with the standard CDE Console dtterm. It's basically brain dead otherwise. i haven't really had any problems with it, and i wouldn't call it braindead. not exactly full featured, but not brain dead. Quite frankly, I would like to run Gnome/Enlightenment instead of CDE and I will be looking into how to do just that very soon. i thought gnome was a sawfish thing now? dont really use it, i like motif. the newer releases of solaris 8 come with a freeware cd, that has kde, gnome, and loads of other open source packages compiled. even puts a gnome entry in the dtlogin menu. -- __ _ Carl B. Constantine / / (_)__ __ __[EMAIL PROTECTED] / /__/ / _ \/ // /\ \/ / (2.4.1)ICQ: 26351441 //_/_//_/\_ _/ /_/\_\ Stormix 2000 PGP key available on request Up the line - out the server- past the firewall - nothing but Net!! -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Color Errors on Solaris
On Thu, May 24, 2001 at 09:40:34AM +0100, Steve Kennedy wrote: On Wed, May 23, 2001 at 05:42:43PM -0700, Carl Constantine wrote: Quite frankly, I would like to run Gnome/Enlightenment instead of CDE and I will be looking into how to do just that very soon. If you look on Sun's site, there is a link to a company that is doing the porting work for GNOME to Solaris. Last time I looked they hadn't quite got 1.4 packaged, but it was expected real soon now. also, something i forgot to mention is that sun is ditching cde for gnome. and some funky webdesk stuff, but thats another story. im guessing at a release date of gnome 2.0/solaris 9 timeframe. heard their desktop group actually has ppl on the gnome team...also heard something about star office and open office getting together. Steve -- NetTek Ltd tel +44-(0)20 7483 1169 fax +44-(0)20 7483 2455 Flat 2,43 Howitt Road, Belsize Park,London NW3 4LU mobile 07775 755503 Epage [EMAIL PROTECTED] [body only] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Sat, May 12, 2001 at 02:36:07PM +0200, Lawrence Mitchell wrote: * On [010511 22:45] Thomas Roessler [EMAIL PROTECTED] wrote: On 2001-05-11 15:56:33 -0400, adam morley wrote: I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? Is not _what_ standard? If we don't say this is format=flowed, we also don't have to emit format=flowed. This non-standard refers to quoting levels, in conjunction with format=flowed text, how to consider quoted text, and what defines the quote depth, as far as I can make out. The relevant RFC is; RFC 2646 section 4.5. Though, from what I can make out from it, it doesn't apply when the text format is not format=flowed.(?) non-format flowed text is definately a gray area, and open to a little interpretation based on what is seen in multiple rfcs. i see what you are saying, and i understand what thomas was saying. Lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 10:14:05AM +0530, Suresh Ramasubramanian wrote: adam morley proclaimed on mutt-users that: oh the mail-followup-to header might be a little weird, considering im using list reply and mine might not be configured the same as yours.still learning just how it works. Its pretty good is there a way to display it? ignore * # this means ignore all lines by default unignore from: subject to cc mail-followup-to \ date x-mailer x-url # this shows how nicely wrap long lines well, i wanted to see it at message compose time, not at view time. to make sure its right during testing. something like right below the To: header. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Sun, May 13, 2001 at 06:49:26AM +0530, Suresh Ramasubramanian wrote: Using a large mallet, adam morley whacked out: ignore * # this means ignore all lines by default unignore from: subject to cc mail-followup-to \ date x-mailer x-url # this shows how nicely wrap long lines well, i wanted to see it at message compose time, not at view time. to make sure its right during testing. something like right below the To: header. You want a vim macro for this I expect. no, i wanted to see it right below the to: line in the screen you see after you edit the message, as i dont yoink the headers into my editor. -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Mutt issues with Solaris 8
On Thu, May 10, 2001 at 09:06:04PM -0700, Carl Constantine wrote:
On 5/10/01 9:28, adam morley at [EMAIL PROTECTED] wrote:
i actually have mutt runing on solaris 8. the colors in the config file never
seem to mactch up with the colors diplayed. i just play around with it until
i get it to work. ill go back and read your original post and see if i can
figure it out.
Really? What did you do and how did you do it? Can you send me your configs
as well?
sure, my .muttrc is below. the global muttrc file is just the standard one i think.
Did you also use ncurses?
not that i remember. i dont think i have gnu curses, but i do have svr4 curses
begin muttrc--
# adam's muttrc. thanks to super tim
#
#
# My mail folder is
set folder=~/mail
# I am not prompted to ask whether I will move message out of the spool
# the answer is no
set move=no
# Messages are automatically purged when marked for deletion
#set delete=yes
#beeping...on new.
set beep_new=yes
set beep=no
set autoedit=yes
set menu_scroll=yes
# Specifies mailboxes with incoming mail
mailboxes deleted because i dont want you to know. :)
#mailing list config
set honor_followup_to=yes
set followup_to=yes
lists listname
subscribe listname
# Saves all messages I sent to a folder
set copy=yes
set record=~/mail/sent
# My Aliase file info
set alias_file=~/.mail_aliases
source ~/.mail_aliases
# Defines my header
my_hdr From: adam morley [EMAIL PROTECTED]
# Defines my editor
set editor=/usr/bin/vi
# Sets the place to put postponed messages
set postponed=~/mail/postponed
# Does not prompt when saving messages to an existing folder
set confirmappend=no
# Sets it so that when you get to the bottom of the message it stops rather than
going to the next message
set pager_stop=yes
# Makes the index view use threads - a cool feature
set sort=threads
#index formatting
set index_format=%4C %Z %{%d %b} %-15.15F (%4l) %s
#above changed to handle mailing liststhe F
# header display, j,k are mapped to vi-fu, x for pine like feel, - and space for pine
compatibility. the arrow keys work like pine, cept for left right which scroll like -
and space
bind pager H display-toggle-weed
bind pager h noop
bind pager j next-line
bind pager k previous-line
bind index x sync-mailbox
bind pager up previous-line
bind pager down next-line
bind pager left previous-entry
bind pager right next-entry
bind index - previous-page
bind index space next-page
#makes it feel like pine, to a certain extent.
# list of header fields to ignore when displaying messages
ignore from received content- mime-version status x-status message-id
ignore sender references return-path lines
ignore Envelope-to X- In-Reply-To NNTP-Postings Xref
#
# Stuff taken from the default global file
#
# don't add the hostname to the From header
unset use_domain
# don't generate a From header
unset use_from
# Exim does not removes Bcc headers
unset write_bcc
# imitate the old search-body function
macro index \eb '/~b ' 'search in message bodies'
# simulate the old url menu
macro index \cb |urlview\n 'call urlview to extract URLs out of a message'
macro pager \cb |urlview\n 'call urlview to extract URLs out of a message'
# colors
color hdrdefault brightcyan black #default
color quoted brightblue yellow
color signature cyan black
color attachment brightyellow blue
#color indicator black cyan
color indicator brightblack cyan # nicer in reverse-color xterms
color status brightblue white
color tree blue white
color markers brightblue red
color tildebrightblue red
color header blue white ^From:
color header brightgreen black ^To:
color header brightgreen black ^Cc:
color header brightgreen black ^Reply-To:
color header brightblue yellow ^Subject:
color body brightblue yellow [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+
color body brightblue yellow (http|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+
#the above stuff with brightblue/yellow is because other color combos don't seem to
work too well.
# aliases for broken MUAs
charset-hook US-ASCII ISO-8859-1
charset-hook x-unknownISO-8859-1
charset-hook windows-1250 CP1250
charset-hook windows-1251 CP1251
charset-hook windows-1252 CP1252
charset-hook windows-1253 CP1253
charset-hook windows-1254 CP1254
charset-hook windows-1255 CP1255
charset-hook windows-1256 CP1256
charset-hook windows-1257 CP1257
charset-hook windows-1258 CP1258
# GnuPG configuration
set pgp_sign_micalg=pgp-sha1 # default for DSS keys
set pgp_decode_command=gpg %?p?--passphrase-fd 0? --no-verbose --batch --output - %f
set pgp_verify_command=gpg --no-verbose --batch --output - --verify %s %f
set pgp_decrypt_command=gpg --passphrase-fd 0 --no-verbose --batch --output - %f
set pgp_sign_command=gpg --no-verbose --batch --output - --passphrase-fd 0 --armor
--detach-sign --textmode %?a?-u %a? %f
set pgp_clearsign_command=gpg --no-verbose
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote: At 23:04 -0400 10 May 2001, adam morley [EMAIL PROTECTED] wrote: On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote: format=flowed requires a lot more implementation than just adding a content-type header, iirc. I wouldn't really say a lot more (at least when not dealing with quoted text), but definitely more. well, if i write my messages so they are wrapped like this as you will You mean not wrapped. sorry, ive been talking about this too long with others, it starts to run together in my head. see in one second, then it can be classified as a flowed message. a I suppose it *could* be classified as such, but I don't see much point in doing so. The whole point of format=flowed is so that paragraphs will wrap in programs that support it, but still be readable with programs that don't do wrapping. well, the whole point is that ppl dont like unwrapped text. so one solution has been format=flowed. any others? It also doesn't follow part of RFC 2646: thats a should clause. not a must ] When generating Format=Flowed text, lines SHOULD be shorter than 80 ] characters. As suggested values, any paragraph longer than 79 Your nested quoting was also done incorrectly. According to section 4.5 of RFC 2646 there should be no space between the '' marks at the start of quoted lines. that, my friend was mutts doing, not mine. so if someone could explain why/how to change that, then thanks! -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ ... very sad life. Probably have very sad death but at least there is symmetry. -- Zathras -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote: At 23:04 -0400 10 May 2001, adam morley [EMAIL PROTECTED] wrote: On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote: format=flowed requires a lot more implementation than just adding a content-type header, iirc. I wouldn't really say a lot more (at least when not dealing with quoted text), but definitely more. well, if i write my messages so they are wrapped like this as you will You mean not wrapped. see in one second, then it can be classified as a flowed message. a I suppose it *could* be classified as such, but I don't see much point in doing so. The whole point of format=flowed is so that paragraphs will wrap in programs that support it, but still be readable with programs that don't do wrapping. one gnus user (under emacs) pointed out that unwrapped text is treated as fixed text so this line which just wrapped doesn't wrap word boundaries, but letter boundaries. is that wrong/right? It also doesn't follow part of RFC 2646: ] When generating Format=Flowed text, lines SHOULD be shorter than 80 ] characters. As suggested values, any paragraph longer than 79 Your nested quoting was also done incorrectly. According to section 4.5 of RFC 2646 there should be no space between the '' marks at the start of quoted lines. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ ... very sad life. Probably have very sad death but at least there is symmetry. -- Zathras -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 12:04:50PM -0400, Sam Roberts wrote: Quoting adam morley [EMAIL PROTECTED], who wrote: On Fri, May 11, 2001 at 04:34:03AM -0500, Aaron Schrab wrote: At 23:04 -0400 10 May 2001, adam morley [EMAIL PROTECTED] wrote: On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote: see in one second, then it can be classified as a flowed message. a I suppose it *could* be classified as such, but I don't see much point in doing so. The whole point of format=flowed is so that paragraphs will wrap in programs that support it, but still be readable with programs that don't do wrapping. well, the whole point is that ppl dont like unwrapped text. so one solution has been format=flowed. any others? Don't send unwrapped text? why? (and if you open up this can of worms, i can go on for at least 20 messages, so if others dont want to hear it, we might want to take it off the list) Sam -- Sam Roberts [EMAIL PROTECTED] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 06:49:19PM +0200, Lawrence Mitchell wrote: * On [010511 18:02] adam morley [EMAIL PROTECTED] wrote: Your nested quoting was also done incorrectly. According to section 4.5 of RFC 2646 there should be no space between the '' marks at the start of quoted lines. that, my friend was mutts doing, not mine. so if someone could explain why/how to change that, then thanks! Using vim as an editor, I came up with this: change double-quoted text to RFC 2646 format autocmd BufNewFile,BufRead .followup,.letter,mutt*,nn.*,snd.* :%s/^\(.*\)/\1/ The command on one line of course, hope that helps ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? lawrence -- Lawrence Mitchell | http://members.tripod.co.uk/EVSvienna/ [EMAIL PROTECTED] | He says gods like to see an atheist around. Gives them something to aim at. -- (Terry Pratchett, Small Gods) -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 07:45:46PM +0200, Thomas Roessler wrote: On 2001-05-11 13:21:40 -0400, adam morley wrote: ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? It's configurable, and the mutt version you are using doesn't even claim that it's producing text/plain; format=flowed. so how do i make mutt set the quote thing correctly? and im not setting format=flowed right now. mainly because nobody's told me how to automate it save editing the source. -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Setting correct double-nested quotes (was: Changing the Mime type of the outgoing message by default?)
On Fri, May 11, 2001 at 01:37:16PM -0500, Paul Cox wrote: On Friday, May 11, 2001, adam morley wrote: ah, if mutts not putting in the right, then MUTT is what is non-compliant, correct? i shouldn't have to make a vim macro to fix mutt's non-compliance? indent_string Type: string Default: Specifies the string to prepend to each line of text quoted in a message to which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. I've just been told that is non-standard though. which means we are distributing a software package that is non-standard. is that bad? -- [EMAIL PROTECTED], ICQ#: 25370820, OpenPGP key at www.keyserver.net 1024D/39F0BBF4 2024 B7CB 10BF 6BE7 2ECE E0FD 1360 0181 39F0 BBF4 Current Linux uptime: 5 days 22 hours 55 minutes. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 06:58:08PM +0200, Thomas Roessler wrote: On 2001-05-10 23:04:34 -0400, adam morley wrote: well, if i write my messages so they are wrapped like this as you will see in one second, then it can be classified as a flowed message. a zero paragraph flowed message. hence my need to know how to do such a thing. would require reformatting other messages tho. text/plain; format=flowed actually forbids overly long lines. Indeed, in a properly formatted text/plain; format=flowed message, no line will be longer than 78 characters when the message is viewed with a viewer which does _not_ support format=flowed. ah, no line *should* be longer than 78 chras, correct? its a should, not a must if i remember. The fact that a lines may be flowed is indicated by a space character in the end of a line. yes, and if i place the entire line as one big long unwrapped line, then i have zero paragraphs with each paragraph having at least one space-crlf sequence. which is compliant with the rfc in saying that format flowed is in effect. the only reason i bring this up is that people have been arguing that with the gnus mailer (emacs mailer) an unwrapped line of text is wrapped at the char (as it is format=fixed) whereas a flowed message (with the proper options set) is wrapped on word boundaries. (Look closely at this message for an example.) -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 06:55:47PM +0200, Thomas Roessler wrote: On 2001-05-10 13:29:17 -0400, adam morley wrote: so currently, the mime type of my message is text/plain. i want to change this to text/plain; format=flowed for each outgoing mail message. i didn't see this in the muttrc file or manual. thanks. You could update to the latest CVS version. It has some support for text/plain; format=flowed built into it. (Mutt now even makes use of the features for this format when, e.g., replying to messages.) really? thats cool. However, you'll also need an editor which supports editing messages in that format - that is, adds spaces whereever necessary, be it in not if you never space crlf. the end of a line when it wraps, or in the beginning of lines where that is not required by rfc 2646, it is a should statment. and it is there for non-flow aware mail readers. we avoid this when not wrapping and using fixed, as it aint flowed text. you have a character or the word From . this is an issue I have created a mode for jed which does all this (probably it still has a couple of bugs); you can try this, too. never used jed. too many editors already. -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 10:43:58PM +0200, Thomas Roessler wrote: On 2001-05-11 16:02:11 -0400, adam morley wrote: that is not required by rfc 2646, it is a should statment. and it is there for non-flow aware mail readers. we avoid this when not wrapping and using fixed, as it aint flowed text. You don't expect this to look nice in any usual mailer, do you? dont expect what again? i have a short term memory and yeah. thanks. -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 10:42:43PM +0200, Thomas Roessler wrote: On 2001-05-11 15:59:30 -0400, adam morley wrote: ah, no line *should* be longer than 78 chras, correct? its a should, not a must if i remember. Which means that you shouldn't violate this unless you have a very good reason (such as a long word) to violate it. my point is the reason for not violating said should clause is archaic. my reason is that if your mail reader can't handle it, step into the 21st century and get a reader that knows how to wrap text. -- Thomas Roessler http://log.does-not-exist.org/ -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 02:48:27PM -0700, [EMAIL PROTECTED] wrote: On Fri, May 11, 2001 at 05:29:44PM -0400, adam morley wrote: my point is the reason for not violating said should clause is archaic. my reason is that if your mail reader can't handle it, step into the 21st century and get a reader that knows how to wrap text. Mail systems unpredictably truncate lines longer than (IIRC) 1023 characters. So you're likely to have truncated paragraphs and sure to tick off just about everyone with your arrogant attitude. actually its 1000--998 + crlf. according to the rfc If you want to break RFCs get a job with M$, where doing so seems to be a good career move. uh. okay -rex -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Changing the Mime type of the outgoing message by default?
so currently, the mime type of my message is text/plain. i want to change this to text/plain; format=flowed for each outgoing mail message. i didn't see this in the muttrc file or manual. thanks. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote: On Thu, May 10, 2001 at 02:03:05PM -0400, Sam Roberts typed: You can edit the content-type type of the outgoing message with ctrl-T and add ; format=flowed. Maybe there's a way of automateing that, perhaps a hot-key that feeds the keyboard strokes to mutt? format=flowed requires a lot more implementation than just adding a content-type header, iirc. after more reading in 2646, i would agree. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Re: Changing the Mime type of the outgoing message by default?
On Fri, May 11, 2001 at 12:43:28AM +0530, Suresh Ramasubramanian wrote: On Thu, May 10, 2001 at 02:03:05PM -0400, Sam Roberts typed: You can edit the content-type type of the outgoing message with ctrl-T and add ; format=flowed. Maybe there's a way of automateing that, perhaps a hot-key that feeds the keyboard strokes to mutt? format=flowed requires a lot more implementation than just adding a content-type header, iirc. well, if i write my messages so they are wrapped like this as you will see in one second, then it can be classified as a flowed message. a zero paragraph flowed message. hence my need to know how to do such a thing. would require reformatting other messages tho. oh the mail-followup-to header might be a little weird, considering im using list reply and mine might not be configured the same as yours.still learning just how it works. is there a way to display it? thx. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Lists the From/To line in pager (inbox view)
when i set a list to lists listname in my muttrc file, it recognizes the list. but when i say im subscribed to it, the pager (i think thats what its called, the thing where all the messages are display) shows the to line, not the from line. how do i change this? thanks. -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
