X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: How to run GNU Emacs from Windows icon Date: Fri, 05 Jun 2009 08:47:20 -0700 Lines: 23 Message-ID: References: <746652D230364290B3E68BE37FA6CB50 AT corp DOT real DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.21 (X11/20090409) In-Reply-To: <746652D230364290B3E68BE37FA6CB50@corp.real.com> X-Stationery: 0.4.8.14 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 David Karr wrote: > I now need to set up Windows desktop icons that can start these > processes. I managed to get XEmacs working, with the following command > line: > > C:\cygwin\bin\bash.exe --login -c C:/cygwin/bin/xemacs-21.4.22.exe Why the insistence on running bash? Why not simply run Xemacs? That's what I do at work and it works fine for me. > However, when I try to do something similar for GNU Emacs, it fails > immediately. When I tried running the analogous command from the DOS > prompt, I got this: > > ----------------- >> C:\cygwin\bin\bash.exe --login -c "C:/cygwin/bin/emacs.exe" > emacs: Terminal type cygwin is not defined. > If that is not the actual type of terminal you have, > use the Bourne shell command `TERM=... export TERM' (C-shell: > `setenv TERM ...') to specify the correct type. It may be necessary > to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. Again, why run bash first then run emacs? -- Andrew DeFaria Press any key to continue or any other key to quit... -- 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/