X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <416096c60906251225n304f9eecy9a3cdac91b4d06d5@mail.gmail.com> References: <4A43B6C6 DOT 7040709 AT aim DOT com> <416096c60906251225n304f9eecy9a3cdac91b4d06d5 AT mail DOT gmail DOT com> Date: Fri, 26 Jun 2009 00:29:43 -0400 Message-ID: <17393e3e0906252129n49b8ba90p4202b451ff78141f@mail.gmail.com> Subject: Re: Problem with mintty-0.4.1-1 and orpie From: Matt Wozniski To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, Jun 25, 2009 at 3:25 PM, Andy Koppe wrote: > There's a bit in the TIPS section of the manual on how to set any > environment variable using the shell's -c option, e.g.: > > mintty sh -c "TERM=xterm-256color emacs" Hm. Maybe I'm missing something, but - isn't this a place where using /bin/env would make more sense than dealing with all the extra processing required to launch a shell? For instance, mintty env TERM=xterm-256color emacs ~Matt -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple