[Mutt] #2893: fcc_attach=no should record filenames (like deleted attachments)

2007-05-23 Thread Mutt
#2893: fcc_attach=no should record filenames (like deleted attachments) {{{ Forwarding to trac so we don't forget it... - Forwarded message from Louis-David Mitterrand - Date: Thu, 3 May 2007 17:21:26 +0200 From: Louis-David Mitterrand <[EMAIL PROTECTED]> To: mutt-dev@mutt.org Su

Re: [PATCH, RFC] mouse tracking support

2007-05-23 Thread Christoph Berg
Hi, thanks for the comments. Re: Gary Johnson 2007-05-21 <[EMAIL PROTECTED]> > I just built the ncurses-5.5 library with --enable-ext-mouse and > built mutt-1.5.15 with this library and your patch on a machine > running SunOS 5.8. With the minimal use I've given it so far, it > seems to work

[PATCH] Support for reading users and/or passwords from netrc(5)

2007-05-23 Thread Luciano Rocha
# HG changeset patch # User [EMAIL PROTECTED] # Date 1179848062 -3600 # Node ID 0a3bb46d1d5ee19199f2f7170cfdd16a46cb3553 # Parent 357b7651d6095f5b2e9c5dab1e4cb5c7fb6bc379 Support for reading users and/or passwords from netrc(5) Extended mutt_account_getuser and mutt_account_getpass in account.c w

Re: [PATCH] Support for reading users and/or passwords from

2007-05-23 Thread Kyle Wheeler
On Wednesday, May 23 at 05:16 PM, quoth Luciano Rocha: Support for reading users and/or passwords from netrc(5) Extended mutt_account_getuser and mutt_account_getpass in account.c with netrc_user and netrc_password for retrieving username and password from ~/.netrc. ...according to my netrc(5)

[PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread Luciano Rocha
# HG changeset patch # User [EMAIL PROTECTED] # Date 1179846675 -3600 # Node ID 357b7651d6095f5b2e9c5dab1e4cb5c7fb6bc379 # Parent 516f41633e202184e897bef24a6d9f17bba7c0ba when using `which` send errors to /dev/null diff -r 516f41633e20 -r 357b7651d609 hcachever.sh --- a/hcachever.sh Sun May

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread Rado S
=- Luciano Rocha wrote on Wed 23.May'07 at 18:48:01 +0100 -= > when using `which` send errors to /dev/null > {...} > -if test -x "`which md5`" > +if test -x "`which md5 2> /dev/null`" On solaris 8 which produces noise on STDOUT, not STDERR. Maybe the attached version suits all. -- © Rado S. --

Re: [PATCH] Support for reading users and/or passwords from

2007-05-23 Thread Luciano Rocha
On Wed, May 23, 2007 at 11:42:21AM -0600, Kyle Wheeler wrote: > On Wednesday, May 23 at 05:16 PM, quoth Luciano Rocha: >> Support for reading users and/or passwords from netrc(5) >> >> Extended mutt_account_getuser and mutt_account_getpass in account.c with >> netrc_user and netrc_password for retr

Re: [PATCH] Support for reading users and/or passwords from

2007-05-23 Thread Kyle Wheeler
On Wednesday, May 23 at 07:15 PM, quoth Luciano Rocha: ...according to my netrc(5) man pages, ~/.netrc is specific to ftp. Why is fetching information out of it and using it for email a good idea? Well, for starters, it isn't called .ftprc. =) HEH. Fair enough, but still, it's not exactly so

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread David Champion
* On 2007.05.23, in <[EMAIL PROTECTED]>, * "Rado S" <[EMAIL PROTECTED]> wrote: > =- Luciano Rocha wrote on Wed 23.May'07 at 18:48:01 +0100 -= > > > when using `which` send errors to /dev/null > > {...} > > -if test -x "`which md5`" > > +if test -x "`which md5 2> /dev/null`" > > On solaris

Re: [PATCH, RFC] mouse tracking support

2007-05-23 Thread Gary Johnson
On 2007-05-23, Christoph Berg <[EMAIL PROTECTED]> wrote: > Re: Gary Johnson 2007-05-22 <[EMAIL PROTECTED]> > > I've encountered a few issues with using this patch. None of these > > are bugs, just areas where I think the behavior could be improved. > > The next issue is probably just a matter o

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread Luciano Rocha
On Wed, May 23, 2007 at 01:33:56PM -0500, David Champion wrote: > * On 2007.05.23, in <[EMAIL PROTECTED]>, > * "Rado S" <[EMAIL PROTECTED]> wrote: > > =- Luciano Rocha wrote on Wed 23.May'07 at 18:48:01 +0100 -= > > > > > when using `which` send errors to /dev/null > > > {...} > > > -if test

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread Rado S
=- Luciano Rocha wrote on Wed 23.May'07 at 20:22:32 +0100 -= > > It's easy enough to add a which-like command though. > > What about stopping to find where the binary is and check only if it can > be run? > if echo | md5sum &> /dev/null; then > MD5=md5sum > elif echo | md5 &> /dev/null; then >

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread Luciano Rocha
On Wed, May 23, 2007 at 10:01:37PM +0200, Rado S wrote: > =- Luciano Rocha wrote on Wed 23.May'07 at 20:22:32 +0100 -= > > > > It's easy enough to add a which-like command though. > > > > What about stopping to find where the binary is and check only if it can > > be run? > > if echo | md5sum &>

Re: when using `which` send errors to /dev/null

2007-05-23 Thread Cameron Simpson
On 23May2007 13:33, David Champion <[EMAIL PROTECTED]> wrote: | Is the problem with irregular behavior of different whiches? I've never trusted it even to exist everywhere:-) | Which is | convenient but besides this has the drawback that since it's almost | always a csh script, it sometimes retur

Re: when using `which` send errors to /dev/null

2007-05-23 Thread Cameron Simpson
On 23May2007 20:22, Luciano Rocha <[EMAIL PROTECTED]> wrote: | if echo | md5sum &> /dev/null; then "&>" is not portable. It's a bastard import into bash from csh:-( Just go ">/dev/null 2>&1". Portable and just as readable. -- Cameron Simpson <[EMAIL PROTECTED]> DoD#743 http://www.cskk.ezoshosting

Re: [PATCH, RFC] mouse tracking support

2007-05-23 Thread Kyle Wheeler
On Monday, May 21 at 12:39 PM, quoth Kyle Wheeler: On Monday, May 21 at 07:15 PM, quoth Christoph Berg: I've updated Anatoly's patch from 2005 that adds mouse tracking using slang/ncurses to mutt. With "set mouse" (unset by default) mutt will react to button1/2/3/wheel with configurable bindings

Re: when using `which` send errors to /dev/null

2007-05-23 Thread David Champion
* On 2007.05.23, in <[EMAIL PROTECTED]>, * "Cameron Simpson" <[EMAIL PROTECTED]> wrote: > > printf "%s\n" "$PATH" | tr : '\012' | while read -r dir; do > > Unless that breaks on Solaris, which it may:-( I don't think -r is present in a strict Bourne shell's "read". Solaris's gives "-r:

Re: when using `which` send errors to /dev/null

2007-05-23 Thread Cameron Simpson
On 23May2007 21:21, David Champion <[EMAIL PROTECTED]> wrote: | * On 2007.05.23, in <[EMAIL PROTECTED]>, | * "Cameron Simpson" <[EMAIL PROTECTED]> wrote: | > printf "%s\n" "$PATH" | tr : '\012' | while read -r dir; do | > Unless that breaks on Solaris, which it may:-( | | I don't think -r i

Re: when using `which` send errors to /dev/null

2007-05-23 Thread Ralf Wildenhues
* Cameron Simpson wrote on Thu, May 24, 2007 at 01:31:31AM CEST: > On 23May2007 13:33, David Champion <[EMAIL PROTECTED]> wrote: > > | { > | echo $PATH | tr : '\012' | while read dir; do > > This is more robustly written: > > printf "%s\n" "$PATH" | tr : '\012' | while read -r dir; do An

Re: [PATCH] when using `which` send errors to /dev/null

2007-05-23 Thread David Laight
On Wed, May 23, 2007 at 10:55:25PM +0100, Luciano Rocha wrote: > > } 3>&2 > /dev/null 2>&1 (or 3>&2 &> /dev/null) should work instead. Except that &> isn't posix-compliant shell syntax (it is from csh), and isn't supported by all shells. Also, since the redirection of {...} will enforce a subsh