From: "Paminu" <fedevaps@yahoo.dk>
To: cygwin@cygwin.com
Subject: Re: Problems opening files from run menu
Date: Wed, 19 Oct 2005 15:28:00 -0000 [thread overview]
Message-ID: <dj5oac$2li$1@sea.gmane.org> (raw)
In-Reply-To: <20051019145018.GD3521@trixie.casa.cgf.cx>
"Christopher Faylor" <cgf-no-personal-reply-please@cygwin.com> skrev i en
meddelelse news:20051019145018.GD3521@trixie.casa.cgf.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/
next prev parent reply other threads:[~2005-10-19 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 14:45 Paminu
2005-10-19 14:50 ` Christopher Faylor
2005-10-19 15:28 ` Paminu [this message]
2005-10-19 15:37 ` Christopher Faylor
2005-10-21 2:47 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dj5oac$2li$1@sea.gmane.org' \
--to=fedevaps@yahoo.dk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).