Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: cygwin AT cygwin DOT com From: "Paminu" Subject: Re: Problems opening files from run menu Date: Wed, 19 Oct 2005 17:21:50 +0200 Lines: 36 Message-ID: References: <20051019145018 DOT GD3521 AT trixie DOT casa DOT cgf DOT cx> X-IsSubscribed: yes "Christopher Faylor" skrev i en meddelelse news:20051019145018 DOT GD3521 AT trixie DOT casa DOT cgf DOT cx... > On Wed, Oct 19, 2005 at 04:38:43PM +0200, Paminu wrote: >>I have a xfig file in: >> >>c:\cygwin\home\test\test.fig >> >>I can open this xfig file from the run menu like: >>bash --login -e startxprog xfig c:/cygwin/home/test/test.fig >> >>I also have a .dvi file in: >>c:\cygwin\home\test\test.dvi >> >>But when I type: >>bash --login -e startxprog xdvi c:/cygwin/home/test/test.dvi >> >>Nothing happens. Why is it possible to open a file like this with xfig but >>not with xdvi??? > > How about using UNIX-like paths rather than Windows paths, that being > one the main reasons for Cygwin's existence? > > bash --login -e startxprog xdvi /home/test/test.dvi That works fine. But the problem is when I execute xdvi from emacs. Then this gets inserted: c:/cygwin/home/test/test.dvi if I could just get emacs to only type /home/test/test.dvi it would work. But I think it is wierd that xfig accepts the full path while xdvi only accept the path excluding c:/cygwin, but maybe its a bug in xdvi. -- 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/