Re: changing the subject line of a thread / sed zen
also sprach Kyle Wheeler <[EMAIL PROTECTED]> [2007.08.28.2158 +0200]:
> you just got really lucky). The way mutt determines whether a file is
> modified is by comparing the mtime of the temp file it created to the
> mtime of the temp file once the editor is done editing. The mtime is
> stored in seconds. Sed, of course, executes in less than a second, so
> the mtime is unchanged in all but the rarest of cases.
Perfect explanation, thanks Kyle!
> It would work if you'd piped it to a script like this:
You don't even need an editor:
set editor="sleep 1 && sed -i -e ..."
works just as well. On that note, however, you probably want formail
instead, due to multiline headers, but formail cannot edit in-place.
Thus, you'll need a script. :(
Or well, maybe not. The following sed -rn snippet extracts
a multiline header (name stored in $1):
:s;/^\$/q;/${1}/bj;d;:j;P;\$!n;/^[[:space:]]/bj;bs
It should not be too hard to come up with a sed recipe that replaces
the subject. My first try failed though (again, with -re):
":s;/^$/be;/^Subject:/bj;P;:j;n;/^[[:space:]]/bj;=;bs;:e;p;:e2;n;p;be2"
This correctly removes the subject. Where the = is, I wanted to
insert a new Subject line:
":s;/^$/be;/^Subject:/bj;P;:j;n;/^[[:space:]]/bj;iSubject: new" -e
"bs;:e;p;:e2;n;p;be2"
but for some reason, that gets called after *every* header. And yet,
the script should never reach that except after encountering
/^Subject:/ in the header, when it spins in the j loop until the
next header is found. *Then* and only then should it insert the
Subject. I am not a sed guru, so if anyone has a clue, please let me
know.
--
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
this message represents the official view of the voices in my head.
spamtraps: [EMAIL PROTECTED]
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
Subject charset issue (was: merging/linking tagged messages into thread: brilliant!)
Hi folks, I know, I'm a little off-topic, but I have a question about a charset issue: On Tue, Aug 28, 2007 at 02:39:54PM -0400, Cristóbal M. Palmer wrote: ^^ > Cristóbal Palmer ^ I have a clean mutt 1.5.16 running on a linux with locale "[EMAIL PROTECTED]" which is in fact iso8859-15. I connect with PuTTY configured to the same locale. The above quoted message has charset utf8 both in Subject and message body. Mutt displays message body correctly but Subject is not correctly decoded as you can see above. Did I miss some in my configuration (I can't imagine), is this a bug in mutt I should report or is it a wrong coded mail? Greets Alex -- * http://www.lespocky.de *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 pgpdlhUNPZ3Zj.pgp Description: PGP signature
Re: Subject charset issue (was: merging/linking tagged messages into thread: brilliant!)
On Wed, Aug 29, 2007 at 10:36:07AM +0200, Alexander Dahl wrote: > > Did I miss some in my configuration (I can't imagine), is this a bug in > mutt I should report or is it a wrong coded mail? Fair chance it's me. I've seen the same miscoding in my boss's inbox. He uses alpine: http://www.washington.edu/alpine/ I've been teasing him about this mercilessly... oops? It'd be awesome if somebody on this list could point out where I'm erring. FWIW if I mail myself something to my gmail account, the ó in the subject shows up fine. Cheers, -- Cristóbal Palmer ibiblio.org systems administrator
Re: changing the subject line of a thread
* Kyle Wheeler <[EMAIL PROTECTED]> [2007-08-28 13:58]: > On Tuesday, August 28 at 03:14 PM, quoth martin f krafft: > > So I wanted to change the subject line on all thread mails. First, I > > missed the "pass (Maildir) files of tagged messages to external > > command as *arguments*" command in mutt, so I had to create a new > > folder and put the files in there, then go to the shell and invoke > > sed. An alternative would have of course been to set $editor to the > > sed -i command, but I could not get this working. Even setting > > editor="sed -i -e '/./d'" just got me "message not modified". > > HEH. This *would* work, if you were on a much slower machine (or if > you just got really lucky). The way mutt determines whether a file is > modified is by comparing the mtime of the temp file it created to the > mtime of the temp file once the editor is done editing. The mtime is > stored in seconds. Sed, of course, executes in less than a second, so > the mtime is unchanged in all but the rarest of cases. It would work > if you'd piped it to a script like this: > > #!/bin/sh > sleep 1 > sed -i -e '/./d' "$1" > > Because then the mtime would be guaranteed (more or less) to be > different from when mutt created the tmp file. I worked around the same problem in some $editor script by incrementing the mtime via touch(1) as I didn't want the script to sleep(1). I guess it would be nice if Mutt (optionally?) used the MD5 sum or something instead of the mtime to check whether a file is modified. Holger
[Slightly OT] Allow for choosing browser to follow a link
Ctrl-b invokes urlview which provides a list of URLs in the current message and allows me to choose one of them to view it. This invokes w3m or elinks. This is good. But from time to time I want to invoke other browsers. Or just copy the URL to the X11 clipboard. Is there an alternative to urlview that would allow me to choose the program to run on a case-by-case basis? Kai
Re: [Slightly OT] Allow for choosing browser to follow a link
* Kai Grossjohann <[EMAIL PROTECTED]> [08-29-07 07:36]: > Ctrl-b invokes urlview which provides a list of URLs in the current > message and allows me to choose one of them to view it. This invokes > w3m or elinks. This is good. > > But from time to time I want to invoke other browsers. Or just copy the > URL to the X11 clipboard. > > Is there an alternative to urlview that would allow me to choose the > program to run on a case-by-case basis? man urlview provides REGEXP regexp urlview uses a regular expression to extract URLs from the specified text files. \r, \t, \n and \f are all converted to their normal printf(3) meanings. The default REGEXP is: (((https?|ftp|gopher)://|(mailto|file|news):)[^' \t<>"]+|(www|web|w3)\.[-a-z0-9.]+)[^' \t.,;<>":] from .muttrc macro pager \cb |urlview\n 'call urlview to extract URLs out of a message' write your own script putting the regex result into a variable and evoke the browser of your choice: firefox %s call the different scripts via different key combinations macro pager \cc !script\n 'call firefox to view ...' -- 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: Subject charset issue (was: merging/linking tagged messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 10:36 AM, quoth Alexander Dahl: >On Tue, Aug 28, 2007 at 02:39:54PM -0400, Cristóbal M. Palmer wrote: > ^^ >> Cristóbal Palmer > ^ Headers are only allowed to be sent in US-ASCII, and the From header in Cristóbal's emails should, rather than be flat utf-8, be encoded like this: =?UTF-8?Q?Crist=C3=B3bal?. >Did I miss some in my configuration (I can't imagine), is this a bug >in mutt I should report or is it a wrong coded mail? Yup, it is a wrongly coded mail (it's breaking a MUST in RFC 2822). ~Kyle - -- Life is too important to be taken seriously. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1W3HBkIOoMqOI14RArdoAJ9fhPYXp7CXdS1e4MHrMdExdr0AVQCg8uvx j2DtaF4H3OAXEw6au3iSnLg= =ouUy -END PGP SIGNATURE-
Re: Subject charset issue (was: merging/linking tagged messages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 05:44 AM, quoth Cristóbal M. Palmer: > It'd be awesome if somebody on this list could point out where I'm > erring. Hmm... Presumably, that's set in your muttrc via 'set realname="..."', right? My first guess would be that you need to tell mutt what charset you've encoded the muttrc file in (it assumes ascii unless you set config_charset to something). You'll need to set the config_charset before mutt reads any non-ascii characters (i.e. before you set realname). > FWIW if I mail myself something to my gmail account, the ó in the > subject shows up fine. The subject? You mean your *From* header, right? My guess is that gmail is better at guessing malformed headers. Guessing malformed headers is an *artform*, and mutt isn't the best guesser in the world. ~Kyle - -- Only a mediocre person is always at his best. -- Somerset Maugham -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1W/QBkIOoMqOI14RAuszAJ9Bn27sDYKlFlcv2kqi/hjXheHO3gCfdLEP yFm/UVgks/UR4eKtFjK/sd4= =SLgm -END PGP SIGNATURE-
Re: Subject charset issue (was: merging/linking tagged messages
On 29.08.2007 (07:08), Kyle Wheeler wrote: > Hmm... Presumably, that's set in your muttrc via 'set realname="..."', > right? My first guess would be that you need to tell mutt what charset > you've encoded the muttrc file in (it assumes ascii unless you set > config_charset to something). You'll need to set the config_charset > before mutt reads any non-ascii characters (i.e. before you set > realname). Hey! That's interesting! I've always made sure I only use ascii-ified versions of my last name in that kind of fields, just in case, but this seems to work. At least a test mail I sent to myself did. Let's see how this one fares... -- That's the difference between me and the rest of the world! Happiness isn't good enough for me! I demand euphoria! -- Calvin
Re: Subject charset issue (was: merging/linking tagged messages
> this seems to work. At least a test mail I sent to myself did. Let's > see how this one fares... Looks fine on my side. :-) -- * http://www.lespocky.de *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 pgpRB3XEkILEY.pgp Description: PGP signature
Re: 3 questions: Renaming folders with hook + browser reverse date
Hi,
mea culpa, mea culpa...
I had two set sorts in my muttrc... and the second one was overwriting
the good one...
Ok, that fixes the sort issue... now, macro indeces...
I got this email:
-
Alain Bench <[EMAIL PROTECTED]>
Hello,
On Saturday, August 18, 2007 at 23:21:08 +0200, Vim Visual wrote:
>| macro index 'c ~/mail/inbox ^M'
> doesn't work
Let's first write the macro cleanly:
- names instead of keys
- symbols instead of obscure key notations
- drop harmfull spaces (by default the key is bound to the
function at this prompt)
| macro index ~/mail/inbox
Does this work?
Bye!Alain.
-
and I say: A huge, vast, enormous THANK YOU to Alain! That fixed it!
And now the very last question:
I ssh to a linux box to check the email. This is more convenient
because that pc is part of a cluster and is being backup'ed every
night...
When I ssh it from my OpenBSD laptop mutt is behaving well but for ONE
thing: backspace does not work, so that I cannot scroll up the
screen... I get a "this key has not been defined" message, but it has
because when I physically log in on that box, it is working and, when
I use mutt from the very openbsd laptop, backspace is also working
fine. It is only the combination openbsd laptop + ssh tunnel to a
linux box what breaks backspace...
any hint??
Pau
> > > Use 'sort' instead of 'sort-browser'.
> >
> > set sort=reverse-date ?
> >
> > doesn't work either... I get the threads:
> >
> > 288 r + Aug 17 Woodchuck ( 795) Calvin II
> > 289 r + Aug 17 Woodchuck ( 48) +-+->
> > 290 + Aug 17 Woodchuck ( 20) | +->
> > 291 r + Aug 17 Woodchuck ( 11) +->
> > 292 + Aug 17 Woodchuck ( 49) +->
> > 293 + Aug 18 Woodchuck ( 49) +->
>
>:set sort=reverse-date-received
>
> The possible values are listed in this section of the manual:
>
>3.269. sort
>
> Type: sort order
> Default: date
>
> Specifies how to sort messages in the index menu. Valid values
> are:
>
> date or date-sent
> date-received
> from
> mailbox-order (unsorted)
> score
> size
> spam
> subject
> threads
> to
>
> You may optionally use the reverse- prefix to specify reverse
> sorting order (example: set sort=reverse-date-sent).
>
> Another way to find the 'sort' value is to type the 'o' or 'O'
> commands, choose the sort order that appeals to you, then execute
>
>:set ?sort
>
> to see the value you'd need to put in your muttrc.
>
> That being said, if you executed "set sort=reverse-date", you should
> not have seen messages sorted by threads. Perhaps 'sort' is also
> being set by a hook?
>
>
> > > > macro index 'c ~/mail/inbox ^M'
> > > >
> > > > doesn't work any more, with Mutt 1.5.16 (2007-06-09). It worked under
> > > > fedora5 with Mutt 1.4.1i (2003-03-19)
> > >
> > > You didn't say what "doesn't work" means,
> >
> > doesn't work = when I press F5 mutt doesn't react at all; no error
> > message wahtsoever and, of course, I do not get to inbox.
> >
> >
> > > termcap or terminfo data being used by mutt to determine the
> > > character sequence to send for is missing or not correct for
> > > the terminal you are using. Check that your $TERM environment
> > > variable is correct. Then execute
> > >
> > >infocmp -1 | grep kf5
> > >
> > > to see what character sequence, if any, is defined for . ("-1"
> > > is "minus one", not "minus ell".)
> >
> > F5 is not missing. In my vimrc I have
> >
> > map mx{v}gq'x
> >
> > and using it works as a charm.
> >
> > Nevertheless,
> >
> > elachistos| infocmp -1 | grep kf5
> > kf5=\E[15~,
> >
> > and I used that in muttrc to redefine it and didn't work either...
> >
> > Choosing other character, like "5" or "P" doesn't work either.
>
> You're saying that you used one of those characters to define the
> macro, like this?
>
>macro index P 'c ~/mail/inbox ^M'
>
> And that didn't work either? Did you define the macro at mutt's
> command line or just in your muttrc? I just tried that macro by
> defining it at my command line and it worked fine. (I changed the
> folder name to one I had.) Is it possible that your muttrc file is
> not being read?
>
> > By the way,
> >
> > elachistos| echo $TERM
> > xterm-xfree86
> >
> > This is set so because it solved a lot of problems I had in mutt
> > reconising the defined colours
>
> You had these problems while you were using Fedora or only after
> moving to OpenBSD? Did you have problems with vim's colors at the
> same time?
>
> I'm sorry I'm giving you more questions than answers. I'm just not
> making any sense yet of what you're observing.
>
> Regards,
> Gary
>
Re: Subject charset issue (was: merging/linking tagged messages
Hi Kyle, > The subject? You mean your *From* header, right? Sure the From header, sorry about that. O:-) Greets Alex -- * http://www.lespocky.de *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 pgpmtNu4dXqLI.pgp Description: PGP signature
Re: 3 questions: Renaming folders with hook + browser reverse date
> > elachistos| echo $TERM > > xterm-xfree86 > > > > This is set so because it solved a lot of problems I had in mutt > > reconising the defined colours > > You had these problems while you were using Fedora or only after > moving to OpenBSD? Did you have problems with vim's colors at the > same time? > > I'm sorry I'm giving you more questions than answers. I'm just not > making any sense yet of what you're observing. > > Regards, > Gary > Hi Gary, I didn't have those problems with fedora, nor did I have any problems with vim in openbsd. It was really only mutt + openbsd using the wrong TERM... xterm-xfree86 fixes everything Cheers, Pau
Re: Subject charset issue (was: merging/linking tagged messages
On Wednesday, August 29 at 03:35 PM, quoth Eyolf Østrem: On 29.08.2007 (07:08), Kyle Wheeler wrote: Hmm... Presumably, that's set in your muttrc via 'set realname="..."', right? My first guess would be that you need to tell mutt what charset you've encoded the muttrc file in (it assumes ascii unless you set config_charset to something). You'll need to set the config_charset before mutt reads any non-ascii characters (i.e. before you set realname). Hey! That's interesting! I've always made sure I only use ascii-ified versions of my last name in that kind of fields, just in case, but this seems to work. At least a test mail I sent to myself did. Let's see how this one fares... Looks good to me! ~Kyle -- Being powerful is like being a lady. If you have to tell people you are, you aren't. -- Margaret Thatcher pgpPQbHKNFmOB.pgp Description: PGP signature
Re: [Slightly OT] Allow for choosing browser to follow a link
On Wed, Aug 29, 2007 at 07:55:18AM -0400, Patrick Shanahan wrote: > * Kai Grossjohann <[EMAIL PROTECTED]> [08-29-07 07:36]: > > Ctrl-b invokes urlview which provides a list of URLs in the current > > message and allows me to choose one of them to view it. This invokes > > w3m or elinks. This is good. > > > > But from time to time I want to invoke other browsers. Or just copy the > > URL to the X11 clipboard. > > > > Is there an alternative to urlview that would allow me to choose the > > program to run on a case-by-case basis? > > man urlview provides > >REGEXP regexp > urlview uses a regular expression to extract URLs >from the specified text files. \r, \t, \n and \f >are all converted to their normal printf(3) >meanings. The default REGEXP is: > > (((https?|ftp|gopher)://|(mailto|file|news):)[^' > \t<>"]+|(www|web|w3)\.[-a-z0-9.]+)[^' \t.,;<>":] > > from .muttrc > >macro pager \cb |urlview\n 'call urlview to extract URLs out > of a message' > > > write your own script putting the regex result into a variable and > evoke the browser of your choice: firefox %s > > call the different scripts via different key combinations > >macro pager \cc !script\n 'call firefox to view ...' I don't understand :-( - Should the script search for the regex? In that case, it would need to handle multiple occurrences -- which is exactly the job urlview was designed for... - Should I create different config files for urlview, then invoke urlview with the "w3m" for one key or with the "firefox" config file for the other key? urlview doesn't provide an argument for the config file; this will get messy. Actually, what I want is a list of URLs just like that provided by urlview, but when selecting an http or https URL I should be able to choose a browser. Or perhaps choose a browser globally before selecting a URL to view. Kai
Re: [Slightly OT] Allow for choosing browser to follow a link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 04:30 PM, quoth Kai Grossjohann: >Actually, what I want is a list of URLs just like that provided by >urlview, but when selecting an http or https URL I should be able to >choose a browser. Or perhaps choose a browser globally before selecting >a URL to view. One way to do it would be to configure urlview to use a script as a browser. Then in this script, you can do something like: #!/bin/sh choice="" while [ "$choice" != 1 -a "$choice" != 2 ] ; do echo "Options:" echo "1. Firefox" echo "2. w3m" read -p "-> " choice done if [ "$choice" -eq 1 ] ; then firefox "$1" else w3m "$1" fi ... OR you could have your script decide based on an environment variable, like so: #!/bin/sh $BROWSER "$1" Then all you'd need to do is set BROWSER before calling urlview, like so: macro index,pager \cb 'env BROWSER=firefox urlview' macro index,pager \cn 'env BROWSER=w3m urlview' ~Kyle - -- Human beings are the only creatures that allow their children to come back home. -- Bill Cosby -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1ZPiBkIOoMqOI14RAuKdAJ9QNA/xw9VNJNcZo7/Me4EJEBYUQQCfYmK2 EtVuHofB+ejws59CZSs8COI= =vHzW -END PGP SIGNATURE-
Cristóbal (was: mergi ng/linking tagged messages into thread: brilliant!)
Hello Cristóbal, On Tuesday, August 28, 2007 at 14:39:54 -0400, Cristóbal M. Palmer wrote: > From: [EMAIL PROTECTED] (Cristóbal M. Palmer) Your name is misencoded in all your mails, probably because the "From:" field is not written by Mutt. May I suggest you to: Set $from and $realname, verify $use_from=yes, and not set $send_charset (the default is better)? You can mail me to validate the changes. Bye!Alain. -- Mutt compressed folders tip for stable archive timestamp: | open-hook \\.gz$ "gzip -cd '%f' > '%t' ; ret=$? ; touch --no-create --reference='%f' '%t' ; exit \$ret" | close-hook \\.gz$ "gzip -c '%t' > '%f' ; ret=$? ; touch --no-create --reference='%t' '%f' ; exit \$ret" | append-hook \\.gz$ "gzip -c '%t' >> '%f'"
Re: 3 questions: Renaming folders with hook + browser reverse date
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 03:53 PM, quoth Vim Visual: > I ssh to a linux box to check the email. This is more convenient > because that pc is part of a cluster and is being backup'ed every > night... > > When I ssh it from my OpenBSD laptop mutt is behaving well but for > ONE thing: backspace does not work, so that I cannot scroll up the > screen... I get a "this key has not been defined" message, but it > has because when I physically log in on that box, it is working and, > when I use mutt from the very openbsd laptop, backspace is also > working fine. It is only the combination openbsd laptop + ssh tunnel > to a linux box what breaks backspace... > > any hint?? This is a typical problem when going between Xterms on different systems. There are a couple quick solutions: 1. press control and left-click on your xterm, and select "Backarrow Key (BS/DEL)" 2. type `stty erase ` and then ctrl-v and then hit backspace, then hit enter For more permanent (and more portable) resolution, check this out: http://www.hypexr.org/linux_roboff.php ~Kyle - -- Strong coffee, much strong coffee, is what awakens me. Coffee gives me warmth, waking, an unusual force and a pain that is not without very great pleasure. -- Napoleon Bonaparte -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1ZcyBkIOoMqOI14RAqAkAKCUeI86uCijnIs1mHZXijPscq7egACbBc0n jFj/r64sSUZB8n1DWiGekTY= =zi+I -END PGP SIGNATURE-
Re: changing the subject line of a thread
On 2007-08-29, Holger Weiss <[EMAIL PROTECTED]> wrote: > * Kyle Wheeler <[EMAIL PROTECTED]> [2007-08-28 13:58]: > > On Tuesday, August 28 at 03:14 PM, quoth martin f krafft: > > > So I wanted to change the subject line on all thread mails. First, I > > > missed the "pass (Maildir) files of tagged messages to external > > > command as *arguments*" command in mutt, so I had to create a new > > > folder and put the files in there, then go to the shell and invoke > > > sed. An alternative would have of course been to set $editor to the > > > sed -i command, but I could not get this working. Even setting > > > editor="sed -i -e '/./d'" just got me "message not modified". > > > > HEH. This *would* work, if you were on a much slower machine (or if > > you just got really lucky). The way mutt determines whether a file is > > modified is by comparing the mtime of the temp file it created to the > > mtime of the temp file once the editor is done editing. The mtime is > > stored in seconds. Sed, of course, executes in less than a second, so > > the mtime is unchanged in all but the rarest of cases. It would work > > if you'd piped it to a script like this: > > > > #!/bin/sh > > sleep 1 > > sed -i -e '/./d' "$1" > > > > Because then the mtime would be guaranteed (more or less) to be > > different from when mutt created the tmp file. > > I worked around the same problem in some $editor script by incrementing > the mtime via touch(1) as I didn't want the script to sleep(1). > > I guess it would be nice if Mutt (optionally?) used the MD5 sum or > something instead of the mtime to check whether a file is modified. I was surprised by Kyle's comment because I thought mutt already did this, so I looked in the code. It turns out that mutt _sometimes_ does this. In the mutt_edit_headers() and ci_send_message() functions, mutt sets the mtime of the temporary file back one second before invoking the editor so that even if the editing occurs instantaneously, the mtime will be different after editing. Mutt then checks the mtime after invoking the editor to see if the file changed. Oddly, mutt does not do this in the edit_one_message() function which I think is the one being used in this case. I think this should be fixed. If folks agree and unless someone else wants to go for it, I can submit a patch. Regards, Gary
Re: changing the subject line of a thread
On Wednesday, 29 August 2007 at 08:57, Gary Johnson wrote: > On 2007-08-29, Holger Weiss <[EMAIL PROTECTED]> wrote: > > * Kyle Wheeler <[EMAIL PROTECTED]> [2007-08-28 13:58]: > > > HEH. This *would* work, if you were on a much slower machine (or if > > > you just got really lucky). The way mutt determines whether a file is > > > modified is by comparing the mtime of the temp file it created to the > > > mtime of the temp file once the editor is done editing. The mtime is > > > stored in seconds. Sed, of course, executes in less than a second, so > > > the mtime is unchanged in all but the rarest of cases. It would work > > > if you'd piped it to a script like this: > > > > > > #!/bin/sh > > > sleep 1 > > > sed -i -e '/./d' "$1" > > > > > > Because then the mtime would be guaranteed (more or less) to be > > > different from when mutt created the tmp file. > > > > I worked around the same problem in some $editor script by incrementing > > the mtime via touch(1) as I didn't want the script to sleep(1). > > > > I guess it would be nice if Mutt (optionally?) used the MD5 sum or > > something instead of the mtime to check whether a file is modified. > > I was surprised by Kyle's comment because I thought mutt already did > this, so I looked in the code. It turns out that mutt _sometimes_ > does this. In the mutt_edit_headers() and ci_send_message() > functions, mutt sets the mtime of the temporary file back one second > before invoking the editor so that even if the editing occurs > instantaneously, the mtime will be different after editing. Mutt > then checks the mtime after invoking the editor to see if the file > changed. > > Oddly, mutt does not do this in the edit_one_message() function > which I think is the one being used in this case. I think this > should be fixed. If folks agree and unless someone else wants to go > for it, I can submit a patch. That sounds like a good idea. But it would probably be good to set the mtime back to its original time after editing if the message isn't modified.
Re: changing the subject line of a thread
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 09:06 AM, quoth Brendan Cully: >> Oddly, mutt does not do this in the edit_one_message() function >> which I think is the one being used in this case. I think this >> should be fixed. If folks agree and unless someone else wants to >> go for it, I can submit a patch. > > That sounds like a good idea. But it would probably be good to set > the mtime back to its original time after editing if the message > isn't modified. Out of curiosity, why? Mutt's just gonna delete that temporary file... deleted files with slightly incorrect mtimes are just as gone. ~Kyle - -- Time is an illusion. Lunchtime doubly so. -- Douglas Adams -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1Zq6BkIOoMqOI14RAuzaAJ9GGhgdb/qbx+g1wYuLPGeQtRGX+wCfS7o8 /0beerYss+lpxrdP6uT332A= =oNAc -END PGP SIGNATURE-
Re: [Slightly OT] Allow for choosing browser to follow a link
On 2007-08-29, Kai Grossjohann <[EMAIL PROTECTED]> wrote: > Ctrl-b invokes urlview which provides a list of URLs in the current > message and allows me to choose one of them to view it. This invokes > w3m or elinks. This is good. > > But from time to time I want to invoke other browsers. Or just copy the > URL to the X11 clipboard. > > Is there an alternative to urlview that would allow me to choose the > program to run on a case-by-case basis? I use w3m instead of urlview for the Ctrl-B command. macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; unset pipe_decode\n" "call w3m to extract URLs out of a message" macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; unset pipe_decode\n" "call w3m to extract URLs out of a message" The : command within w3m turns all URL-looking strings in the text into links. W3m allows you to configure as many as three external browsers that can be used instead of w3m itself to view the current page (M, 2M or 3M) or follow the current link (M, 2M or 3M). HTH, Gary
Re: changing the subject line of a thread
On Wednesday, 29 August 2007 at 10:11, Kyle Wheeler wrote: > On Wednesday, August 29 at 09:06 AM, quoth Brendan Cully: > >> Oddly, mutt does not do this in the edit_one_message() function > >> which I think is the one being used in this case. I think this > >> should be fixed. If folks agree and unless someone else wants to > >> go for it, I can submit a patch. > > > > That sounds like a good idea. But it would probably be good to set > > the mtime back to its original time after editing if the message > > isn't modified. > > Out of curiosity, why? Mutt's just gonna delete that temporary file... > deleted files with slightly incorrect mtimes are just as gone. Whoops, right. I'd assumed mutt edited the message in place, but of course it doesn't. Time for coffee...
Re: [Slightly OT] Allow for choosing browser to follow a link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 09:15 AM, quoth Gary Johnson: >I use w3m instead of urlview for the Ctrl-B command. > > macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > unset pipe_decode\n" "call w3m to extract URLs out of a message" > macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > unset pipe_decode\n" "call w3m to extract URLs out of a message" > >The : command within w3m turns all URL-looking strings in the text >into links. W3m allows you to configure as many as three external >browsers that can be used instead of w3m itself to view the current >page (M, 2M or 3M) or follow the current link (M, 2M or >3M). Interesting... why do you set pipe_decode first? In html email, w3m (my usual inline html renderer) doesn't spit out all the links in convenient fashion at the bottom, like elinks does, and what links there are are often wrapped to the terminal width. How does w3m handle that? ~Kyle - -- To invent, you need a good imagination and a pile of junk. -- Thomas Jefferson -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1Z0fBkIOoMqOI14RArQMAKC0znjuPy57VJzUkTarHrZ1M2KmfwCgu5/P TzJmsoNAjnBYGMJHadzqMXs= =ycng -END PGP SIGNATURE-
[OT] List corrupting DomainKeys?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I swear this has been talked about before, but I can't find it in the list archive... My posts to the list are all signed with both DomainKey and DKIM signatures, and for some reason, they're all broken. What is the mutt mailing list software *doing* that's breaking the DKIM signatures? Should it perhaps be stripping DomainKey/DKIM signatures out of list messages? ~Kyle - -- Power always thinks it has a great soul and vast views beyond the comprehension of the weak; and that it is doing God's service when it is violating all his laws. -- John Adams -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1aX1BkIOoMqOI14RAqX0AKDwq30KOrXjSLOOrf9ZYHW5izXrgACfd7jg 3/cxuHf5DP9lR0mc3lxBfPE= =6WNZ -END PGP SIGNATURE-
Re: [OT] List corrupting DomainKeys?
On Wednesday, 29 August 2007 at 10:59, Kyle Wheeler wrote: > Hey all, > > I swear this has been talked about before, but I can't find it in the > list archive... > > My posts to the list are all signed with both DomainKey and DKIM > signatures, and for some reason, they're all broken. What is the mutt > mailing list software *doing* that's breaking the DKIM signatures? > > Should it perhaps be stripping DomainKey/DKIM signatures out of list > messages? According to my inbound DKIM validator, your message passes. Maybe it's only the domainkey that's failing? I believe domainkey is a little less robust.
Re: Setting subscribe/list within muttrc (using IMAP)
Am 2007-08-24 23:49:36, schrieb David J. Weller-Fahy: > Perhaps I'm looking for a feature that doesn't exist, and I'm almost > certainly missing something simple, but here's the background: It seems there is no way in mutt... I am too using a simplified code sniplet of "uw-imap" to get all directories (and number of NEW/READ messages ) from an imap-server... Greetings Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: [OT] List corrupting DomainKeys?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 10:03 AM, quoth Brendan Cully: >> My posts to the list are all signed with both DomainKey and DKIM >> signatures, and for some reason, they're all broken. What is the >> mutt mailing list software *doing* that's breaking the DKIM >> signatures? > > According to my inbound DKIM validator, your message passes. Maybe > it's only the domainkey that's failing? I believe domainkey is a > little less robust. Hrm, it would appear that you are correct. My DKIM validator was broken (needed to update Mail::DKIM), so now the DKIM signatures validate correctly. However my DomainKey signatures are still broken; my validator says "Message is not valid syntax.", whatever that means. Does anyone else have any clue? ~Kyle - -- Preach the Gospel at all times and when necessary use words. -- St. Francis of Assisi -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1a0nBkIOoMqOI14RAhkVAKDF9V58srS1khYTafze4jA+nfOliwCg2sal E7MTZHvqKZ2972U0HtjlX5U= =H9PE -END PGP SIGNATURE-
Re: [OT] List corrupting DomainKeys?
On Wed, Aug 29, 2007 at 11:30:15AM -0600, Kyle Wheeler wrote: > Hrm, it would appear that you are correct. My DKIM validator was > broken (needed to update Mail::DKIM), so now the DKIM signatures > validate correctly. However my DomainKey signatures are still broken; > my validator says "Message is not valid syntax.", whatever that means. What are you using for DK validation? I'm seeing the same as you (validation failures). I'm using a hand compiled C program, but it has been so long ago that I don't remember what library I was using. I though one of the newer DKIM libs also did DK? -- :: Jeff Macdonald | Director of Messaging Technologies :: e-Dialog | [EMAIL PROTECTED] :: 131 Hartwell Ave. | Lexington, MA 02421 :: v: 781-372-1922 | f: 781-863-8118 :: www.e-dialog.com
Re: mutt command line with gpg
Michelle Konzack wrote: > Am 2007-08-22 16:19:38, schrieb Meenal Pant: > >> Hello, >> I want to use mutt as a command inside a script and therefore I don't >> want to run mutt interactively. >> To achieve this, I use: >> $> mutt -F ./.muttrc -s "Hello" -i ../text.txt [EMAIL PROTECTED] > and get the desired result. >> My problem occurs when I use GnuPG and want to sign the message. I use >> set pgp_autosign=yes and define the signature key, set >> pgp_sign_as=0x127533B2 in .muttrc >> The message does not appear signed to the recipient. However when I use >> the same command without > message appears signed. Please help me fix this issue. Thanks >> >> Also is their a way to encrypt and sign using GnuPG and Mutt via command >> line ? >> > > It does not work, since mutt/gpg is waiting for the pass phrase... > To avoid this, you can use the "gpg-agent" > > Greetings > Michelle Konzack > Systemadministrator > Tamay Dogan Network > Debian GNU/Linux Consultant > > I tried your suggestion of using gpg-agent. This works well with mutt but only in interactive mode again. Any ideas ? When I try sending $> mutt -F ./.muttrc -s "Hello" [EMAIL PROTECTED]
Re: [Slightly OT] Allow for choosing browser to follow a link
On 2007-08-29, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > On Wednesday, August 29 at 09:15 AM, quoth Gary Johnson: > >I use w3m instead of urlview for the Ctrl-B command. > > > > macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > > >The : command within w3m turns all URL-looking strings in the text > >into links. W3m allows you to configure as many as three external > >browsers that can be used instead of w3m itself to view the current > >page (M, 2M or 3M) or follow the current link (M, 2M or > >3M). > > Interesting... why do you set pipe_decode first? To get rid of quoted-printable or base-64 encoding. > In html email, w3m (my usual inline html renderer) doesn't spit > out all the links in convenient fashion at the bottom, like elinks > does, and what links there are are often wrapped to the terminal > width. How does w3m handle that? It's true that w3m sometimes seems to break URLs at the ends of lines. I don't know why that is or whether the break is created by w3m or is in the original message. I doesn't happen often enough for me to have looked into it. I'm not sure I understand the issue with links at the bottom. I use w3m with mutt in several ways. o As a replacement for urlview as described above. In that case, the original message is usually plain text and w3m highlights the links in their original location in the message. Personally, I like that better than having all the links at the bottom. o As an HTML-to-plain-text converter ahead of mutt's built-in pager. W3m renders the HTML as it would be seen in a browser, so the URLs of links are often not rendered. It doesn't really matter, though, since links can't followed from mutt's pager anyway. To follow the links in such messages, I open the HTML part of the message from mutt's attachment menu which runs w3m as a browser. o As a pager for plain text messages that often contain URLs. Some newsletters I subscribe to contain short summaries of articles each followed by the URL of the full article. I use message-hooks to identify these messages and to set 'pager' to "w3m" or to some script that combines a filter with w3m. Again I find it more convenient to have the URLs presented as links in their original locations in the message rather than grouped at the bottom. Regards, Gary
Re: [OT] List corrupting DomainKeys?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 01:38 PM, quoth Jeff Macdonald: >On Wed, Aug 29, 2007 at 11:30:15AM -0600, Kyle Wheeler wrote: >> Hrm, it would appear that you are correct. My DKIM validator was >> broken (needed to update Mail::DKIM), so now the DKIM signatures >> validate correctly. However my DomainKey signatures are still broken; >> my validator says "Message is not valid syntax.", whatever that means. > >What are you using for DK validation? I'm seeing the same as you >(validation failures). I'm using a hand compiled C program, but it has >been so long ago that I don't remember what library I was using. I >though one of the newer DKIM libs also did DK? I use dktest, from libdomainkeys (http://domainkeys.sf.net). To verify (and create) DKIM signatures, I use the perl Mail::DKIM module. ~Kyle - -- People demand freedom of speech to make up for the freedom of thought which they avoid. -- Soren Aabye Kierkegaard (1813-1855) -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1bKLBkIOoMqOI14RAm65AJ0b8oNu6WmclYPrx4608wRCkweqpQCfcX6g l5s+EvQKUvBeadeOU5OcKe8= =i9oV -END PGP SIGNATURE-
Re: [Slightly OT] Allow for choosing browser to follow a link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 10:50 AM, quoth Gary Johnson: >> In html email, w3m (my usual inline html renderer) doesn't spit out >> all the links in convenient fashion at the bottom, like elinks >> does, and what links there are are often wrapped to the terminal >> width. How does w3m handle that? > > It's true that w3m sometimes seems to break URLs at the ends of > lines. I don't know why that is or whether the break is created by > w3m or is in the original message. I doesn't happen often enough > for me to have looked into it. > > I'm not sure I understand the issue with links at the bottom. My point is that when, in the html, they have something like this: Click http://example.com";>here! w3m will render that (as part of the pipe_decode process) into: Click here! pipe_decode uses w3m to *decode* the email before piping it to whatever you told it to pipe to; so piping an html message to w3m with pipe_decode set is feeding w3m its own output (read: mostly useless for extracting links). > o As an HTML-to-plain-text converter ahead of mutt's built-in > pager. W3m renders the HTML as it would be seen in a browser, so > the URLs of links are often not rendered. It doesn't really matter, > though, since links can't followed from mutt's pager anyway. To > follow the links in such messages, I open the HTML part of the > message from mutt's attachment menu which runs w3m as a browser. That's very different from what you were suggesting before. It's a few extra steps, too... ~Kyle - -- Liberty is the only thing you cannot have unless you are willing to give it to others. -- William Allen White -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1bT7BkIOoMqOI14RAs4QAJ9u8tSaYpQLKusdLWedXDeXkByxUACePTAt W7pCW8zAXFCiWJyLUHtkZ/M= =Xf1a -END PGP SIGNATURE-
Re: [Slightly OT] Allow for choosing browser to follow a link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, August 29 at 09:15 AM, quoth Gary Johnson: >I use w3m instead of urlview for the Ctrl-B command. > > macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > unset pipe_decode\n" "call w3m to extract URLs out of a message" > macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > unset pipe_decode\n" "call w3m to extract URLs out of a message" > >The : command within w3m turns all URL-looking strings in the text >into links. W3m allows you to configure as many as three external >browsers that can be used instead of w3m itself to view the current >page (M, 2M or 3M) or follow the current link (M, 2M or >3M). Also... in my w3m, pressing : doesn't seem to do anything, and pressing M just makes it say "Can't browse stdin". I presume you have something in your w3m config that changes it's behavior? ~Kyle - -- History will be kind to me, for I intend to write it. -- Winston Churchill -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG1Z7QBkIOoMqOI14RAmbbAJ46bs/s1ypdH+1Ei66yqo2D3fpdfwCeI0ni 0TNb1GKD/GqD3qOvA3Z6rK4= =/yX6 -END PGP SIGNATURE-
Re: mutt command line with gpg
2007/8/29, Meenal Pant <[EMAIL PROTECTED]>: > I tried your suggestion of using gpg-agent. This works well with mutt > but only in interactive mode again. Any ideas ? When I try sending > > $> mutt -F ./.muttrc -s "Hello" [EMAIL PROTECTED] > with pgp-autosign= yes set in .muttrc, it is delivered as a plaintext > messages. I am trying to send signed messages from mutt via a script, to > thunderbird and mac mail. try pexpect
Re: [Slightly OT] Allow for choosing browser to follow a link
On 2007-08-29, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > On Wednesday, August 29 at 10:50 AM, quoth Gary Johnson: > >> In html email, w3m (my usual inline html renderer) doesn't spit out > >> all the links in convenient fashion at the bottom, like elinks > >> does, and what links there are are often wrapped to the terminal > >> width. How does w3m handle that? > > > > It's true that w3m sometimes seems to break URLs at the ends of > > lines. I don't know why that is or whether the break is created by > > w3m or is in the original message. I doesn't happen often enough > > for me to have looked into it. > > > > I'm not sure I understand the issue with links at the bottom. > > My point is that when, in the html, they have something like this: > > Click http://example.com";>here! > > w3m will render that (as part of the pipe_decode process) into: > > Click here! > > pipe_decode uses w3m to *decode* the email before piping it to > whatever you told it to pipe to; so piping an html message to w3m with > pipe_decode set is feeding w3m its own output (read: mostly useless > for extracting links). > > > o As an HTML-to-plain-text converter ahead of mutt's built-in > > pager. W3m renders the HTML as it would be seen in a browser, so > > the URLs of links are often not rendered. It doesn't really matter, > > though, since links can't followed from mutt's pager anyway. To > > follow the links in such messages, I open the HTML part of the > > message from mutt's attachment menu which runs w3m as a browser. > > That's very different from what you were suggesting before. It's a few > extra steps, too... Right. I guess I just didn't think about that use case. If I can see the URLs the pager, I use Ctrl-B. If I can't see the URLs, I use the attachment menu. I don't encounter the latter very often, largely because of the types of e-mail I receive and because of the way I have my message-hooks set up to choose w3m as the pager for certain messages. Regards, Gary
web addresses cut with +
Hi, whenever I get a link to a web address it is shown in a line; that's fine, but for the lines which are too long (longer than the terminal size used). in that case mutt breaks the line and continues it in a new one and that's indicated with a + For instance: http://defectivebydesign.org/sites/nodrm.civicactions.net/modules/civicrm/extern +/url.php?u=361&qid=318672 You get the point now... the real web address is blablabla/modules/civicrm/extern/url.php?u=361&qid=318672 so, no + to indicate the continuation of the line When I copy it to paste it afterwards in the browser, the + breaks the link How can I get rid of it? Thanks Pau
Re: web addresses cut with +
On Wed, Aug 29, 2007 at 09:22:03PM +0200, Vim Visual wrote: > whenever I get a link to a web address it is shown in a line; that's > fine, but for the lines which are too long (longer than the terminal > size used). in that case mutt breaks the line and continues it in a > new one and that's indicated with a + look for $markers in TFM... unset it and it will get rid of the markers on wrapped lines. w
Re: Cristóbal (was: m
Quoting Alain Bench ([EMAIL PROTECTED]): > > From: [EMAIL PROTECTED] (Cristóbal M. Palmer) It shows up as a proper 'ó' at my screen. But probably because i am in a native UTF-8 environment. What you quoted back looks like an utf8 character in latin1 encoding ;) -- | Do people in Australia call the rest of the world "up over"? | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D
Re: Subject charset issue (was: merging/linking tagged messages into
Thus spake Alexander Dahl [08/29/07 @ 10.36.07 +0200]: > Hi folks, > > I know, I'm a little off-topic, but I have a question about a charset issue: > > On Tue, Aug 28, 2007 at 02:39:54PM -0400, Crist??bal M. Palmer wrote: >^^ > > Crist?bal Palmer >^ > > I have a clean mutt 1.5.16 running on a linux with locale "[EMAIL PROTECTED]" > which > is in fact iso8859-15. I connect with PuTTY configured to the same locale. > The above quoted message has charset utf8 both in Subject and message body. > Mutt displays message body correctly but Subject is not correctly decoded as > you can see above. > > Did I miss some in my configuration (I can't imagine), is this a bug in > mutt I should report or is it a wrong coded mail? This seems like a good time for me to jump in ... for me, the "from" line is rendered correctly but the signature is not. But the point of my post is this: the correctly-shown "from" is the very first time, ever, in my history with mutt that an accented character has been displayed. Normally, I get either a single question-mark or a double one. I have tried setting my terminal app to UTF-8, ASCII, MacRoman, etc., but none of that makes it appear correctly. I looked online at the wiki/faq/charset, and as it instructed I looked at $LANG. I found that echo $LANG returned nothing. (I'm on MacOSX 10.4, using Terminal.app). So I followed the wiki and did this: export LANG=en_US.ISO-8859-1. Still no dice, although the accented 'o' in 'Cristobal' stopped being rendered correctly, and now looks like this: Crist\xxx\xxxbal, where the x's are digits. Still following the wiki, I tried checking to see if mutt picked up on the fact that I changed $LANG, by typing :set &charset ?charset. Mutt revealed that charset="US-ASCII". Meanwhile, my terminal application (not bash) is still on UTF-8. For that matter, terminal-vim never displays accented characters correctly, either, whether it's called by mutt or not. But I don't think vim is the culprit, because mutt displays them wrongly in the index view and when reading messages. What do I do? Thanks much, -G
Re: [Slightly OT] Allow for choosing browser to follow a link
On 2007-08-29, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > On Wednesday, August 29 at 09:15 AM, quoth Gary Johnson: > >I use w3m instead of urlview for the Ctrl-B command. > > > > macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > > >The : command within w3m turns all URL-looking strings in the text > >into links. W3m allows you to configure as many as three external > >browsers that can be used instead of w3m itself to view the current > >page (M, 2M or 3M) or follow the current link (M, 2M or > >3M). > > Also... in my w3m, pressing : doesn't seem to do anything, and > pressing M just makes it say "Can't browse stdin". I presume you have > something in your w3m config that changes it's behavior? Hmm. I don't know why it wouldn't respond to :. I'm using w3m-0.5.2, but I think it has had that feature for quite a while. By default, : only affects URLs that are visible on the current page. To have it linkify all URLs in the document, you need to set Treat URL-like strings as links in all pages (*)YES ( )NO The M commands hand the URL of the current page or of the selected link to the external browser. W3m can't do that with stdin. I've attached my ~/.w3m/config so that you can compare it with yours. The 'extbrowser' setting may look odd. I run mutt on a Sun machine because that's where I do most of my work and have most of my tools installed but I run Firefox on a Linux machine (also my X server) because it's easier to install Firefox on Linux than on Sun. I hardly ever use the second or third external browser. I just tried using them and they don't work. They did in previous releases of w3m. Now though, 2M, 3M, 2M and 3M all open the page/link in Firefox. I just tested w3m-0.5.1 and it works correctly. Oh goody, one more thing to look into. Regards, Gary gb18030_as_ucs 0 strict_iso2022 1 use_jisx0213 0 use_jisx0212 0 use_jisx0201k 0 use_jisc6226 0 use_jisx0201 0 use_gb12345_map 0 fix_width_conv 1 search_conv 1 pre_conv 0 ucs_conv 1 use_language_tag 1 use_combining 1 use_wide 0 ext_halfdump 0 follow_locale 1 system_charset ISO-8859-1 auto_detect 2 document_charset ISO-8859-1 display_charset ISO-8859-1 cookie_accept_domains cookie_reject_domains accept_bad_cookie 0 accept_cookie 1 show_cookie 1 use_cookie 1 no_cache 0 noproxy_netaddr 1 no_proxy agilent.com ftp_proxy http://web-proxy:8088/ http_proxy http://web-proxy:8088/ use_proxy 1 max_news 50 nntpmode nntpserver news.spk.agilent.com dns_order 0 meta_refresh 1 follow_redirection 10 default_url 0 retry_http 1 argv_is_url 0 accept_media text/html, text/*;q=0.5, image/* accept_encoding gzip, compress, bzip, bzip2 accept_language en;q=1.0 no_referer 0 user_agent pre_form_file ~/.w3m/pre_form ftppass_hostnamegen 1 ftppasswd disable_secret_security_check 0 passwd_file ~/.w3m/passwd use_lessopen 0 bgextviewer 1 extbrowser3 lynx extbrowser2 /home/garyjohn/bin/netscape2 extbrowser remsh whiffle -n DISPLAY=$DISPLAY /home/garyjohn/bin/Linux/firefox-remote "'%s'" & mailer mutt editor vim urimethodmap ~/.w3m/urimethodmap, /home/garyjohn/src/SunOS/w3m-0.5.2/etc/w3m/urimethodmap mailcap ~/.w3m/mailcap, /home/garyjohn/src/SunOS/w3m-0.5.2/etc/w3m/mailcap mime_types ~/.mime.types, /home/garyjohn/src/SunOS/w3m-0.5.2/etc/mime.types index_file cgi_bin personal_document_root document_root keymap_file keymap preserve_timestamp 1 auto_uncompress 0 decode_cte 0 clear_buffer 1 fixed_wheel_scroll_count 5 relative_wheel_scroll_ratio 30 relative_wheel_scroll 0 reverse_mouse 0 use_mouse 1 ignorecase_search 1 wrap_search 0 mark_all_pages 1 vi_prec_num 0 emacs_like_lineedit 0 mark 0 close_tab_back 0 confirm_qq 0 save_hist 1 history 100 use_history 1 pagerline 1 visited_color magenta visited_anchor 0 active_color cyan active_style 0 bg_color terminal mark_color cyan form_color red image_color green anchor_color blue basic_color terminal color 1 nextpage_topline 1 label_topline 1 show_srch_str 1 show_lnum 0 fold_line 0 image_map_list 1 imgdisplay w3mimgdisplay image_scale 100 ext_image_viewer 1 max_load_image 4 auto_image 1 display_image 1 view_unseenobject 0 ignore_null_img_alt 1 display_ins_del 1 fold_textarea 0 graphic_char 0 alt_entity 1 multicol 0 dictcommand file:///$LIB/w3mdict.cgi use_dictcommand 0 dirlist_cmd file:///$LIB/dirlist.cgi ext_dirlist 1 display_lineinfo 1 decode_url 0 display_link 1 open_tab_dl_list 0 open_tab_blank 0 target_self 0 frame 1 pixel_per_line 14 pixel_per_char 7 indent_incr 4 tabstop 8
Re: web addresses cut with +
Big Lambchop bless you, William mutt is approaching now perfection... 2007/8/29, William Yardley <[EMAIL PROTECTED]>: > On Wed, Aug 29, 2007 at 09:22:03PM +0200, Vim Visual wrote: > > > whenever I get a link to a web address it is shown in a line; that's > > fine, but for the lines which are too long (longer than the terminal > > size used). in that case mutt breaks the line and continues it in a > > new one and that's indicated with a + > > look for $markers in TFM... unset it and it will get rid of the markers > on wrapped lines. > > w >
Re: web addresses cut with +
On Wednesday, Aug 29, 2007 at 12:47, William Yardley wrote: > look for $markers in TFM... unset it and it will get rid of the markers > on wrapped lines. This still doesn't prevent mutt from putting in a hard carriage return in order to wrap the line, though. This is annoying if, for example, you're trying to copy a long url from mutt in an xterm into a browser window. It's now a 2-step process (or more for very long urls). Anyone know if this is mutt's doing, or perhapsa limitation of the terminal being used to display mutt? Or of ncurses? Is it something that can be worked around in mutt? Thanks, -Conrad.
Re: web addresses cut with +
well, if you're using a fancy desktop environment or whatever you like to call it, click right and choose "copy link address" otherwise the two steps... it's not that dramatic... believe me, looking for the hidden + was much worse... or reduce the size of the font in your terminal until it fits the screen :) 2007/8/29, Lloyd-Knight, Conrad <[EMAIL PROTECTED]>: > On Wednesday, Aug 29, 2007 at 12:47, William Yardley wrote: > > look for $markers in TFM... unset it and it will get rid of the markers > > on wrapped lines. > > This still doesn't prevent mutt from putting in a hard carriage return > in order to wrap the line, though. This is annoying if, for example, > you're trying to copy a long url from mutt in an xterm into a browser > window. It's now a 2-step process (or more for very long urls). > > Anyone know if this is mutt's doing, or perhapsa limitation of the > terminal being used to display mutt? Or of ncurses? Is it something > that can be worked around in mutt? > > Thanks, > -Conrad. >
Re: web addresses cut with +
On Wed, Aug 29, 2007 at 04:20:18PM -0400, Lloyd-Knight, Conrad wrote: > On Wednesday, Aug 29, 2007 at 12:47, William Yardley wrote: > > look for $markers in TFM... unset it and it will get rid of the markers > > on wrapped lines. > > This still doesn't prevent mutt from putting in a hard carriage return > in order to wrap the line, though. This is annoying if, for example, > you're trying to copy a long url from mutt in an xterm into a browser > window. It's now a 2-step process (or more for very long urls). > Not for Firefox (and presumably related browsers) it isn't, the returns are irrelevant and pasting the multiline link works fine. > Anyone know if this is mutt's doing, or perhapsa limitation of the > terminal being used to display mutt? Or of ncurses? Is it something > that can be worked around in mutt? > > Thanks, > -Conrad. -- Chris Green
Re: [Slightly OT] Allow for choosing browser to follow a link
On 2007-08-29, Gary Johnson <[EMAIL PROTECTED]> wrote: > I hardly ever use the second or third external browser. I just > tried using them and they don't work. They did in previous releases > of w3m. Now though, 2M, 3M, 2M and 3M all open the > page/link in Firefox. I just tested w3m-0.5.1 and it works > correctly. Oh goody, one more thing to look into. I found the problem. It is a bug introduced in w3m-0.5.2 when the attempt was apparently made to fix another problem. The workaround is to set vi_prec_num 1 in your ~/.w3m/config, either directly or via the Option Setting Panel, in the Miscellaneous Settings section: Enable vi-like numeric prefix (*)YES ( )NO I have submitted a bug report to the w3m developers. Regards, Gary
