Re: setting From dynamically
* Aldy Hernandez <[EMAIL PROTECTED]> [2002-09-08 19:29 -0400]: > Now all mutt needs is for f to be able to pick from the > alternates list. But this is very minor. I use: alias f_listNicolas Rachinsky alias f_Nicolas Rachinsky alias f_dauerreden Nicolas Rachinsky macro compose v "^Uf_" "Absender wählen" Nicolas
Re: location of signature.
* Bo Peng <[EMAIL PROTECTED]> [2002-09-05 17:00:19 -0500]: >This will be my last post about this topic. I am not gonna waste more >time on this trivial issue, even if it is important to many of you. Well, I've read quite a bit further down this thread before responding to this message, and I must say that regardless of any other netiquette breaches you may be guilty of, you did manage to not post again after saying you wouldn't; that's a skill a lot of us would do well to learn, I think. :p However... >I do not know exactly how many people reply before quoted message but >over 90% of my daily emails are in this style and I can see this kind of >emails all over the Internet. Maybe they are all bad-mannered people, >maybe they are all corrupted by M$, I feel quite comfortable with this >style and will continue to use it. Well, obviously neither I nor anyone else can stop you, but I wish you wouldn't. It's just simply not the best way to do things. In addition to the various politeness-based reasons already cited by others, the one thing that really brings it home for me (as someone who values solutions that have empirical merit) is that top-quoting simply doesn't scale. What I mean is, if you are responding to a message that contains two separate points, to which you want to reply separately, putting your reply in one block (either at the top _or_ bottom) has certain objective, quantifiable disadvantages. Therefore, assuming you accept these two statements: 1) A reply to two separate parts of the same message is clearer when the two reply blocks appear immediately below the parts of the message to which they pertain. 2) Consistency of style is important for effective communication. (Hint: the very existence of written language is a demonstration of this point) ...then it follows that top-replying is not the best way. As an additional point, I submit the following excerpt from a post from [EMAIL PROTECTED], to the newsgroup microsoft.public.win2000: #When including text from a previous message in the thread, trim it #down to include only text pertinent to your response. Your response #should appear below the quoted information. In follow-ups, whether #News or Mail, CUT headers & signatures, PRUNE quotations, and preserve #order. That is to say, quote above each part of your reply as much #of the earlier stuff as is needed to put the new material in context, #but no more; most readers will be able to refer to the earlier article #itself, if need be. Never write on the same line as a quotation, except #in lists and notes; generally leave a wholly blank line between. Do not #quote the header or the signature, unless it is relevant to do so. Whether one's interpretation of the above is "Microsoft said it, it must be true" or "Microsoft is saying it, which means it must be a standard that's been around so long that even they couldn't embrace and extend it", the message is the same. :) Now, I must say I find it quite humorous that their own official posting guidelines are violated by their own newsreader, but that's a whole other story. :) (Or is it...should you really think that all those Outlook users out there are doing the right thing when their client's default behaviour isn't even consistent with its author's employees' stated wishes?) >In this discussion, many replies are polite and informative but others >are cynical and rude, even they are written in 'good style'. I can sit >down and argue with you about compared to web, ftp, mp3, rm, how much >bandwidth is used for emails but I decide to quit this discussion just >because many of you are too righteous to hear about it. > >Have a very good day. >Bo Well, I'm still writing this followup in hopes that: 1) ...you are still reading the thread, if not replying, and your mind might still be changed, or 2) ...someone else who is on the fence will make the right decision. -- [EMAIL PROTECTED] (John Buttery) This .sig is dedicated to David T-G, the only person who noticed enough to wonder whether I was typing these in manually the last time I broke my sig rotation script. msg30804/pgp0.pgp Description: PGP signature
[no subject]
Hi mutt folks, 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. Save them as aliases certainly do. But I'm kind of lazy that I'd prefer spending hours poking around trying to find a trick rather than adding aliases one by one mechanically ;) I guess I need a hook or something, but don't know where to start. Any hint or suggestion is greatly appreciated. Clay -- 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
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
Mutt+Vim: ugly block cursor when editing
Dear and Happy mutt users,
I started playing with colors in Vim when editing mutt messages.
However, I get an ugly block cursor (orange or yellow depending on
the terminal) on each empty line.
I use Mutt 1.4i and Vim 6.1 on RedHat 7.2 (compiled from SRPMs).
Mutt runs in gnome-terminal.
I attached my vimrc for reference, and you can view what I'm talking
about: http://cern.ch/simer/mutt_vim.png
Can anyone help?
Erik
" CVS: $Id: vimrc,v 1.3 2002/08/23 08:35:32 es Exp $
"
" Common VIM initialization file
" Used with VIM 6
"
" INSTALLATION:
"
" Copy the following lines to your ~/.vimrc
"
" if filereadable(expand("~/config/vimrc"))
" source ~/config/vimrc
" endif
" Syntax highlighting
"if has("syntax") && &t_Co > 2
"syntax on
"endif
syntax off
" Indentation
if has("autocmd")
filetype plugin indent on
endif
set ai
" Tabs
set tabstop=4
set softtabstop=4
set expandtab
set noinsertmode
" Show whitespaces
set list
" Show trailing spaces
set listchars=tab:»·,trail:·
" Disable compatibility with old vi
set nocompatible
" Custom settings for mutt
au BufNewFile,BufRead /tmp/mutt* set et tw=68 comments=nb:>
au BufNewFile,BufRead /home/es/.letter set et tw=68 comments=nb:>
Following URLs under Cygwin-mutt
I use Mutt 1.4i in Cygwin so do not have access to Urlview. Previous mail to this list regarding alternatives to Urlview have recommended w3m and lynx, and I have had some success putting these in mailcap. However, alot of the links do not display at all in w3m and lynx. Undoubtedly, such pages are following bad HTML practice, but the result is that I often have to switch to Mozilla and type the URL -- to the point that I'm tempted to replicate the entire stream of incoming mail and send it to Eudora or Mozilla for the sole purpose of following URLs (as with Phil Agre's Red Rock Eater News Service, which lists URLs in plain text -- some of which are not readable with w3m and lynx). Is it possible to direct mutt to view plain-text mail in a non-console browser such as Mozilla? Or have others found console-based options to be satisfactory? Tom -- Dr. Thomas Baker[EMAIL PROTECTED] Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784 Fraunhofer-Gesellschaft work +49-30-8109-9027 53754 Sankt Augustin, Germanyfax +49-2241-144-1408
Re: Mutt+Vim: ugly block cursor when editing
* Erik Simon <[EMAIL PROTECTED]> [2002-09-09 06:36]: > I started playing with colors in Vim when editing mutt messages. > However, I get an ugly block cursor (orange or yellow depending on the > terminal) on each empty line. I was getting something the same thing for a long time. $editor was set to "vim -c '/^$', so it would start on the first blank line, and I had hlsearch set. You didn't specify the contents of $editor (the mutt-side variable, not the env var), and I didn't see hlsearch mentioned in your vimrc, but setting hlsearch right now gives me identical symptoms to what you're describing. So, try :set nohlsearch, and see if that works. (darren) -- You are what you see.
Re: rtfm dammit
[EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote: > Actually my sig is at least ELEVEN lines, but hey, whose counting ? > ( FYI - The last part of the sig has a word riddle in it) > //\ eLviintuaxbilse/\\ Linux is evitable? What's the sense on it? -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg30812/pgp0.pgp Description: PGP signature
Re: Mutt+Vim: ugly block cursor when editing
On Mon, Sep 09, 2002 at 08:48:18AM -0400, darren chamberlain wrote: > So, try :set nohlsearch, and see if that works. It works perfectly, thanks a lot Darren! Enjoy! Erik
Re: rtfm dammit
On Mon, Sep 09, 2002 at 08:59:24AM -0400, Bruno Lustosa wrote: > [EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote: > > Actually my sig is at least ELEVEN lines, but hey, whose counting ? > > ( FYI - The last part of the sig has a word riddle in it) > > //\ eLviintuaxbilse/\\ > > Linux is evitable? "Linux" is in "evitable" ==> "Linux is inevitable." -- Mark REED| CNN Internet Technology 1 CNN Center Rm SW0831G | [EMAIL PROTECTED] Atlanta, GA 30348 USA | +1 404 827 4754 -- The things that interest people most are usually none of their business.
Re: problems with iso-latin-2 characters
Hello Peter, This topic should be better discussed on mutt-users mailing list: Followups directed there. On Monday, September 9, 2002 at 10:59:25 AM +0200, Dr. Peter Leibner wrote: > Sometimes I get e-mails from the Czech Republic with ISO-8859-2 > encoding. To display them I've found the following solution: > message-hook '~h 8859-2' 'set display_filter="/usr/bin/sed -f >/home/leibner/bin/IL2toASCII.sed"' You could drop the filter, and either: - Get a Latin-2 terminal to read and reply to such mails. - Get an UTF-8 terminal, and setup everything accordingly: This way you'll see and quote correctly both your charset and Latin-2, even mixed in the same mail. - Set your $charset to something as "iso-8859-1//TRANSLIT". This will do nearly the same as your sed script, but will show some common accents, as "ä", and transliterate some, as Latin-2 n acute changed to the two chars "´n". > Content-Type: text/plain; charset=utf-8 Your mail was pure Latin-2 chars, no need to send in UTF-8: You should set $send_charset to something as: | set |send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:iso-8859-2:windows-1250:utf-8" Bye!Alain.
Re: rtfm dammit
* Bruno Lustosa <[EMAIL PROTECTED]> [2002-09-09 7:59am]: > [EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote: > > Actually my sig is at least ELEVEN lines, but hey, whose counting ? > > ( FYI - The last part of the sig has a word riddle in it) > > //\ eLviintuaxbilse/\\ > > Linux is evitable? > What's the sense on it? I think it's supposed to be "Linux is inevitable," since "linux" is "in" "evitable." Could be wrong, but oh well. -- "While I was looking around the nursery, I noticed that these were not normal children, but children specially bred by Dr. Panzari and his wife to be their family." -- Jack Handey, "My Big Thick Novel, Chapter 772"
quote (was: rtfm dammit)
On Mon, Sep 09, 2002 at 09:10:11AM -0400, Mark J. Reed wrote: > > "Linux" is in "evitable" ==> "Linux is inevitable." Yes. Quote from John "Maddog" Hall circa 1994 Linux Lectures. (and quite true IMHO). Word riddles are different from a plain scrambles in that they require leaps of logic. Mark's answer is correct. The diagram of his logic (presented by the quote marks) is a little different from the way I would present it: "Linux is" in "evitable" Here's a simple one: mind matter = "Mind over matter" Sadly now everyone with a keyboard and access to Google now knows the answer. :) (you fools! Now look what you've done!) ;-) Next time I post a riddle in my sig I'll have to put a disclaimer in it to send answers directly to me for private verification. But that will make my sig even longer.. :-) -- Jeff Kinz, Director, Emergent Research, Hudson, MA. "[EMAIL PROTECTED]" copyright 1995-2002. Use restricted to non-UCE uses. Any other use is an acceptance of the offer at http://www.ultranet.com/~jkinz/policy.html. "[EMAIL PROTECTED]" copyright 2002. Use is restricted. Any use is an acceptance of the offer at http://users.rcn.com/jkinz/policy.html. (¬_ -o) //\eLviintuaxbilse/\\ V_/_ _\_V
Re: problem removing a macro
That did the trick. Thanks! On Sun, Sep 08, 2002 at 10:22:30PM -0700, John Iverson wrote: > You need folder-hooks. Here's what I do: > > ## Move messages to trash rather than delete, unless > ## we're in the trash folder. > folder-hook . 'macro index d "=trash"' > folder-hook . 'macro pager d "=trash"' > folder-hook trash 'macro index d ""' > folder-hook trash 'macro pager d ""' > ## Delete old, non-flagged, non-new mail > folder-hook trash 'push ~r>10d!(~F|~N)' > > -- > John -- Chuck Tuffli<[EMAIL PROTECTED]> Agilent Technologies, Storage and Networking (916) 788 5086
Re: Mutt guessing wrong encoding for outgoing PDFs?
On Fri, Sep 06, 2002 at 11:21:09PM -0700, Michael Elkins wrote:
> Brian Grayson wrote:
> > Hm. I have 1.2.5 source locally, and it looks like in
> > mutt_set_encoding() in sendlib.c, the following logic may be
> > faulty:
>
> I just noticed that you are using an extremely ancient version of Mutt
> (0.95). Please try using Mutt 1.4, which is the current stable version.
> The logic for picking the CTE is much more complex now, and it should
> address your issue.
I downloaded 1.4 on Friday just to see, and the same problem
occurs. The fundamental problem is once the CTE code sees a
nonzero value of lobin, it goes into quoted, regardless of
whether hibin is nonzero. The following patch does the right
thing for my testcase here, but I don't know if there's a good
reason why the lobin/quotable check currently ignores whether
there are any hibins or not.
After a bit of inspection, the file rep.5k has hibins and
_no_ lobins, and hence goes properly into 8bit encoding. But
the file rep1k has a lobin (0x0b at offset 0x340, for example),
so it short-circuits into quoted-printable. Try mailing the
base64-encoded version of that to yourself, and it should
choose quotable, even in 1.4.
Brian
--
Brian Grayson, SysPerf (System Performance, Modeling, and Simulation)
Somerset Design Center
Motorola
Austin, TX
--- sendlib.c Sat Apr 20 02:25:49 2002
+++ sendlib.c.mod Fri Sep 6 21:27:18 2002
@@ -1196,10 +1196,12 @@
if (b->type == TYPETEXT)
{
char *chsname = mutt_get_body_charset (send_charset, sizeof (send_charset), b);
-if ((info->lobin && strncasecmp (chsname, "iso-2022", 8)) || info->linemax > 990
|| (info->from && option (OPTENCODEFROM)))
- b->encoding = ENCQUOTEDPRINTABLE;
-else if (info->hibin)
+if (info->hibin)
+{
b->encoding = option (OPTALLOW8BIT) ? ENC8BIT : ENCQUOTEDPRINTABLE;
+}
+else if ((info->lobin && strncasecmp (chsname, "iso-2022", 8)) || info->linemax >
+990 || (info->from && option (OPTENCODEFROM)))
+ b->encoding = ENCQUOTEDPRINTABLE;
else
b->encoding = ENC7BIT;
}
Re: rtfm dammit
* On 2002.09.09, in <[EMAIL PROTECTED]>,
* "Mark J. Reed" <[EMAIL PROTECTED]> wrote:
>
> On Mon, Sep 09, 2002 at 08:59:24AM -0400, Bruno Lustosa wrote:
> > [EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote:
> > > Actually my sig is at least ELEVEN lines, but hey, whose counting ?
> > > ( FYI - The last part of the sig has a word riddle in it)
> > > //\ eLviintuaxbilse/\\
> >
> > Linux is evitable?
> "Linux" is in "evitable" ==> "Linux is inevitable."
I dunno, I prefer the former. ("Evitable" just means "avoidable" -- it's
the positive reverse and the root of "inevitable". Unlike "inevitable",
though, you almost never hear it in common language.)
And if we try hard enough, and are stout of heart, we can avoid and
perhaps even survive Linux.
That fills my flame-bait quota for the week.
--
-D.We establised a fine coffee. What everybody can say
Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's
University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!"
[EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
Re: Mutt guessing wrong encoding for outgoing PDFs?
Brian Grayson wrote:
> I downloaded 1.4 on Friday just to see, and the same problem
> occurs. The fundamental problem is once the CTE code sees a
> nonzero value of lobin, it goes into quoted, regardless of
> whether hibin is nonzero. The following patch does the right
> thing for my testcase here, but I don't know if there's a good
> reason why the lobin/quotable check currently ignores whether
> there are any hibins or not.
>
> After a bit of inspection, the file rep.5k has hibins and
> _no_ lobins, and hence goes properly into 8bit encoding. But
> the file rep1k has a lobin (0x0b at offset 0x340, for example),
> so it short-circuits into quoted-printable. Try mailing the
> base64-encoded version of that to yourself, and it should
> choose quotable, even in 1.4.
Thanks for the extra info. I looked into this more closely, and I see
that there are a couple of factors that come into play into this
situation. First, I noticed that your PDF attachment was labeled
improperly as "text/plain". This is not so bad in itself, but that
piece of code that checks for which transfer encoding to use assumes
that it really is text, which is a problem. Since there was no
extension to the file, Mutt fell back into making a guess as to whether
or not the file was of type text/plain or appliation/octet-stream. Mutt
guessed text/plain because it saw only a few lobins in the file.
However, Mutt failed to notice that there were bare CRs in the file when
choosing the transfer encoding. The attach patch checks info->binary
even for the text/plain case. I just tested this and it correctly chose
base64 encoding for the file.
Index: sendlib.c
===
RCS file: /home/roessler/cvs/mutt/sendlib.c,v
retrieving revision 2.94.2.5
diff -u -r2.94.2.5 sendlib.c
--- sendlib.c 31 May 2002 16:59:39 - 2.94.2.5
+++ sendlib.c 9 Sep 2002 16:32:21 -
@@ -1196,7 +1196,17 @@
if (b->type == TYPETEXT)
{
char *chsname = mutt_get_body_charset (send_charset, sizeof (send_charset), b);
-if ((info->lobin && strncasecmp (chsname, "iso-2022", 8)) || info->linemax > 990
|| (info->from && option (OPTENCODEFROM)))
+
+/*
+ * given a lack of info about what the file is from the mime-types file,
+ * Mutt will make a guess as to whether or not the file is likely
+ * text/plain or application/octet-stream based upon statistical
+ * evidence. It is still possible that a binary file (one with a bare
+ * CR) might occur, so we need to account for it here.
+ */
+if (info->binary)
+ b->encoding = ENCBASE64;
+else if ((info->lobin && strncasecmp (chsname, "iso-2022", 8)) || info->linemax >
+990 || (info->from && option (OPTENCODEFROM)))
b->encoding = ENCQUOTEDPRINTABLE;
else if (info->hibin)
b->encoding = option (OPTALLOW8BIT) ? ENC8BIT : ENCQUOTEDPRINTABLE;
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 01:16:16PM +0200, Thomas Baker wrote:
> I use Mutt 1.4i in Cygwin so do not have access to Urlview.
> Previous mail to this list regarding alternatives to Urlview
> have recommended w3m and lynx, and I have had some success
> putting these in mailcap. However, alot of the links do not
> display at all in w3m and lynx.
> Is it possible to direct mutt to view plain-text mail in a
> non-console browser such as Mozilla? Or have others found
> console-based options to be satisfactory?
It's a little awkward, but you can do this with w3m. If you use 'M'
instead of Enter to follow a link, w3m will invoke an external browser
to view the link. You can define this browser in the "External Browser"
entry in the Option Setting Panel ('o').
HTH,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Spokane, Washington, USA
http://www.spocom.com/users/gjohnson/mutt/ |
Re: Following URLs under Cygwin-mutt
On Mon, 9 Sep 2002, Gary Johnson wrote:
> On Mon, Sep 09, 2002 at 01:16:16PM +0200, Thomas Baker wrote:
> > I use Mutt 1.4i in Cygwin so do not have access to Urlview.
> > Previous mail to this list regarding alternatives to Urlview
> > have recommended w3m and lynx, and I have had some success
> > putting these in mailcap. However, alot of the links do not
> > display at all in w3m and lynx.
>
> > Is it possible to direct mutt to view plain-text mail in a
> > non-console browser such as Mozilla? Or have others found
> > console-based options to be satisfactory?
>
> It's a little awkward, but you can do this with w3m. If you use 'M'
> instead of Enter to follow a link, w3m will invoke an external browser
> to view the link. You can define this browser in the "External Browser"
> entry in the Option Setting Panel ('o').
lynx (and I assume links) support external browsers as well. But it's
not clear from the description what/why w3m or lynx were not able to
satisfy his needs.
--
T.E.Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 01:51:27PM -0400, Thomas E. Dickey wrote:
> On Mon, 9 Sep 2002, Gary Johnson wrote:
>
> > On Mon, Sep 09, 2002 at 01:16:16PM +0200, Thomas Baker wrote:
> > > I use Mutt 1.4i in Cygwin so do not have access to Urlview.
> > > Previous mail to this list regarding alternatives to Urlview
> > > have recommended w3m and lynx, and I have had some success
> > > putting these in mailcap. However, alot of the links do not
> > > display at all in w3m and lynx.
> >
> > > Is it possible to direct mutt to view plain-text mail in a
> > > non-console browser such as Mozilla? Or have others found
> > > console-based options to be satisfactory?
> >
> > It's a little awkward, but you can do this with w3m. If you use 'M'
> > instead of Enter to follow a link, w3m will invoke an external browser
> > to view the link. You can define this browser in the "External Browser"
> > entry in the Option Setting Panel ('o').
>
> lynx (and I assume links) support external browsers as well. But it's
> not clear from the description what/why w3m or lynx were not able to
> satisfy his needs.
True. I did assume that "alot of the links do not display at all in w3m
and lynx" followed by the question about others finding "console-based
options to be satisfactory" meant that the pages to which those links
referred did not render well in a text browser. I suppose I should have
stated that assumption in my reply.
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Spokane, Washington, USA
http://www.spocom.com/users/gjohnson/mutt/ |
Re: Mutt+Vim: ugly block cursor when editing
On Mon, Sep 09, 2002 at 12:36:37PM +0200, Erik Simon wrote: > > I started playing with colors in Vim when editing mutt messages. > [and so on...] > Can anyone help? > Well this is offlist, but I will try. > syntax off Shouldn't it be on? Vim is so good at mail syntax hl. > " Show whitespaces > set list << " Show trailing spaces > set listchars=tab:»·,trail:· Why you use this? Vim's help shows this: :help listchars tab:xyTwo characters to be used to show a Tab. The first char is used once. The second char is repeated to fill the space that the Tab normally occupies. "tab:>-" will show a Tab that takes four spaces as ">---". When omitted, a Tab is show as ^I. trail:c Character to show for trailing spaces. When omitted, trailing spaces are blank. These options are AFAIK meant for editing source codes where one needs to know what exactly goes in the buffer. > " Disable compatibility with old vi > set nocompatible Vim's help shows this: :help nocp This is a special kind of option, because when it's set or reset, other options are also changed as a side effect. CAREFUL: Setting or resetting this option can have a lot of unexpected effects: Mappings are interpreted in another way, undo behaves differently, etc. If you set this option in your vimrc file, you should probably put it at the very start. Hence put it at the top of your vimrc. -- Vikram Goyal <[EMAIL PROTECTED]>
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 11:05:31AM -0700, Gary Johnson wrote:
> > > It's a little awkward, but you can do this with w3m. If you use 'M'
> > > instead of Enter to follow a link, w3m will invoke an external browser
> > > to view the link. You can define this browser in the "External Browser"
> > > entry in the Option Setting Panel ('o').
> >
> > lynx (and I assume links) support external browsers as well. But it's
> > not clear from the description what/why w3m or lynx were not able to
> > satisfy his needs.
>
> True. I did assume that "alot of the links do not display at all in w3m
> and lynx" followed by the question about others finding "console-based
> options to be satisfactory" meant that the pages to which those links
> referred did not render well in a text browser. I suppose I should have
> stated that assumption in my reply.
In my admittedly limited experience with text browsers,
alot of the links came up with unhelpful results like like
just "Frame 1" and "Frame 2", or exited with an error message
before showing anything. One could curse those Web editors for
making such unfriendly pages, but there are alot of pages like
that out there and I guess we have to live with them. I'd be
willing to stick it out with text browsers and workarounds
if I knew that others really do live with them comfortably.
In contrast, the one thing I did like about Netscape mail
back when I was using it was that it would recognize the URLs
in plain-text mail and make them clickable, so you could
immediately call up the Web page and see it the way it was
intended to be seen. I could never go back to Netscape
mail for other reasons, but this seems like the sort of
functionality that one shouldn't have to sacrifice under mutt.
Tom
--
Dr. Thomas Baker[EMAIL PROTECTED]
Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784
Fraunhofer-Gesellschaft work +49-30-8109-9027
53754 Sankt Augustin, Germanyfax +49-2241-144-1408
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 09:06:24PM +0200, Thomas Baker wrote: > In my admittedly limited experience with text browsers, > alot of the links came up with unhelpful results like like > just "Frame 1" and "Frame 2", or exited with an error message > before showing anything. One could curse those Web editors for > making such unfriendly pages, but there are alot of pages like > that out there and I guess we have to live with them. I'd be > willing to stick it out with text browsers and workarounds > if I knew that others really do live with them comfortably. I haven't noticed any html email with frames. (Most html email that I do see is spam, though - and I don't look closely at that). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: Mutt guessing wrong encoding for outgoing PDFs?
On 2002-09-09 09:42:21 -0700, Michael Elkins wrote: >Thanks for the extra info. I looked into this more closely, and I >see that there are a couple of factors that come into play into >this situation. First, I noticed that your PDF attachment was >labeled improperly as "text/plain". This is not so bad in itself, >but that piece of code that checks for which transfer encoding to >use assumes that it really is text, which is a problem. Since >there was no extension to the file, Mutt fell back into making a >guess as to whether or not the file was of type text/plain or >appliation/octet-stream. Mutt guessed text/plain because it saw >only a few lobins in the file. However, Mutt failed to notice that >there were bare CRs in the file when choosing the transfer >encoding. The attach patch checks info->binary even for the >text/plain case. I just tested this and it correctly chose base64 >encoding for the file. While the problem clearly lies with mutt mis-treating the PDF file as text, I'm not entirely sure that just changing content-transfer-encodings is the right kind of fix... This may also be a problem with either the old MIME encoder (which is what I tend to believe), or it may come from the special-casing text mode has to do for CR-LF sequences (i.e., line ends), regardless of the content transfer encoding. If it's the latter, there's ultimately nothing we can do about this - apart of not using text mode to transfer binary files. In order to test things, I saved the quoted-printable version of the file to my hard disk, and then sent it to myself using mutt-1.4 and 1.5 (as text/plain, with quoted-printable encoding), and then saved the file. The new file was identical to the old one, down to the byte. Can you guys reproduce this? Or was I already using a mis-treated version of the file as my test case? (MD5 checksum: 57631c6d362944c179c24cbe1512ce2e) -- Thomas Roessler<[EMAIL PROTECTED]>
Re: do NOT attach screen shots to this list! (was: A couple of questions)
Sven, et al - ...and then Sven Guckes said... % % * David Thorburn-Gundlach <[EMAIL PROTECTED]> [2002-09-06]: % > Can you verify that a test message that meets these requirements .. % > Once you have such a message in hand, please gzip it and forward it % > to the list along with screen clips ... % % argh! NO! do *not* attach screen clips to your message. repeat: do NOT! % instead, upload them to some web server and include their addresses. Fair enough; even though what you mean is not what I meant, I can see the possibility of misinterpretation. Since mutt is entirely text-based, there is no need for anything other than a text paste in an email. No, I don't need a two megabyte bitmap of your entire desktop showing all fourteen million colors that you use; I just meant the text that mutt is showing :-) Thanks & 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! msg30829/pgp0.pgp Description: PGP signature
Mutt transport problem
Hi Mutters, I have been using Mutt for several years, but recently came across a deliver problem that relates to Mutt. On my home LAN, I just set up a separate mail server on another box, and removed it off of my main machine. In doing so, I removed Postfix from my machine, as I have no need for it, as the mail server with qmail now takes care of all the LAN's mail. However, I have no transport mechanism to move mail from Mutt to the mail server. How have others accomplished this. Previously, the small oem sendmail from Postfix would send the mail from Mutt. Any ideas greatly appreciated. -- Best regards, Today's thought: When you come to a fork in the road, take it!
Re: Mutt transport problem -> stmp spken here?
* <[EMAIL PROTECTED]> [2002-09-10 00:28]: > On my home LAN, I just set up a separate mail server on another box, > and removed it off of my main machine. In doing so, I removed > Postfix from my machine, as I have no need for it, as the mail > server with qmail now takes care of all the LAN's mail. However, > I have no transport mechanism to move mail from Mutt to the mail server. > How have others accomplished this? install a really simple smtp speaking client like nullmailer or ssmtp. (there were more, but.. 02:32am..) Sven -- http://www.math.fu-berlin.de/~guckes/mutt/util.php3
Re: Mutt transport problem -> stmp spken here?
Hi Sven, On Monday, September 9, 2002, 7:33 PM, you put forth, in part, about "Mutt transport problem -> stmp spken here?": >> I have no transport mechanism to move mail from Mutt to the mail >> server. How have others accomplished this? S> install a really simple smtp speaking client like S> nullmailer or ssmtp. (there were more, but.. 02:32am..) Perfect, just what I need. Thanks Sven... oh, and good night -- Best regards, Gary How do you tell when you run out of invisible ink?
Re: Following URLs under Cygwin-mutt
On Mon, Sep 09, 2002 at 03:22:19PM -0400, Thomas Dickey wrote: > On Mon, Sep 09, 2002 at 09:06:24PM +0200, Thomas Baker wrote: > > In my admittedly limited experience with text browsers, > > alot of the links came up with unhelpful results like like > > just "Frame 1" and "Frame 2", or exited with an error message > > before showing anything. One could curse those Web editors for > > making such unfriendly pages, but there are alot of pages like > > that out there and I guess we have to live with them. I'd be > > willing to stick it out with text browsers and workarounds > > if I knew that others really do live with them comfortably. > > I haven't noticed any html email with frames. (Most html email that I do > see is spam, though - and I don't look closely at that). I haven't either. The problem for me is not HTML email, it's following the URLs cited in text email and viewing them in a graphical browser such as Mozilla or Internet Explorer. I have used various workarounds -- at one extreme, switch to Mozilla and re-type the URL -- but this is really inefficient if the task is to click my way through, say, a blog bulletin from Red Rock Eater (with lots of URLs). It sounds like Gary Johnson's suggestion above (calling Mozilla from w3m) could do the trick, though I guess what I'd really like to do is hand the message off immediately to, say, the mailer in Netscape or Mozilla. Tom -- Dr. Thomas Baker[EMAIL PROTECTED] Institutszentrum Schloss Birlinghoven mobile +49-171-408-5784 Fraunhofer-Gesellschaft work +49-30-8109-9027 53754 Sankt Augustin, Germanyfax +49-2241-144-1408
Sourcing scripts, screen flashes.
Since I've added source lines for a couple scripts, when I start up mutt, the screen flashes several times. source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"| source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"| That sort of thing. Anything I can do to avoid this?
Re: Following URLs under Cygwin-mutt
Hi Thomas, * Thomas Baker ([EMAIL PROTECTED]) [020909 23:03]: [snip] > I have used various workarounds -- at one extreme, switch to > Mozilla and re-type the URL -- but this is really inefficient > if the task is to click my way through, say, a blog bulletin > from Red Rock Eater (with lots of URLs). Hmm... does copy and paste not work in your cygwin environment? Are you using the cygwin dos console? You might want to install the rxvt cygwin package. It's much more friendlier ;). > It sounds like Gary Johnson's suggestion above (calling > Mozilla from w3m) could do the trick, though I guess what > I'd really like to do is hand the message off immediately to, > say, the mailer in Netscape or Mozilla. I refrained from commenting until other more experienced people responded first. If you want to use mozilla in Windows to visit the embedded urls in your text e-mail, you had the answer in your first post in this thread. You mentioned urlview: ftp://ftp.mutt.org/mutt/contrib/urlview-0.9.tar.gz and that you couldn't use it in cygwin for some reason. I've compiled it successfully in cygwin and it works perfectly as it does in unix. After compiling and installing urlview in your cygwin environment, add lines in your $HOME/.muttrc, example from http://www.math.fu-berlin.de/~guckes/setup/muttrc.forall macro index ,\Cb |urlview\n "Extract a URL, and queue for later download" macro pager ,\Cb |urlview\n "Extract a URL, and queue for later download" and finally create a file called $HOME/.urlview with: # # Sample urlview(1) configuration file # # regular expression to use to match URLs REGEXP ht|f)tp)|mailto):(//)?[^ >"\t]*|www\.[-a-z0-9.]+)[^ .,;\t>">] # command to invoke for selected URL COMMAND "/cygdrive/c/Program Files/mozilla.org/Mozilla/mozilla.exe" #COMMAND url_handler.sh #COMMAND netscape -remote 'openURL(%s) Note the COMMAND path to mozilla is from a default install in Windows. Change this to match your setup. I hope this helps! -- jbkim
