Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 5 Aug 2004 12:55:28 +0200 From: Corinna Vinschen To: cygwin Subject: Re: Mutt and Paths Message-ID: <20040805105528.GK24647@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin References: <41120F0D.50404@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41120F0D.50404@sbcglobal.net> User-Agent: Mutt/1.4.2i On Aug 5 03:42, George wrote: > If this is mutt-specific I apologise in advance but I'm trying to figure > out why shell commands executed within mutt fail if the command includes > the '~' notation. For example: > > !less /etc/passwd # works > !less ~/.muttrc # fails - no such file or directory > > What's curious is that in the second example, mutt does seem to expand > '~' on its command-line (tab completion works), but the command itself > fails. Very likely mutt calls system() to run these commands which in turn starts a subshell to run these commands under. The subshell is /bin/sh which doesn't understand the ~ notation. Corinna -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/