From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Roxborough To: Berek Cc: sourcenav@sources.redhat.com, John Smyder Subject: Re: Command Line Problem with Source Navigator and EditPad Pro Date: Thu, 08 Mar 2001 13:38:00 -0000 Message-id: <3AA7FBC9.F068BE3C@redhat.com> References: <5.0.2.1.0.20010307111513.00a62e40@mail.clarityconnect.com> <000e01c0a729$3387a800$3e6410ac@concord.com> X-SW-Source: 2001-q1/msg00204.html Hi, So I was looking into this problem, and I've not been able to reproduce it. This is probably because the real problem is going to be completely unrelated. So, what I really need are step by step instructions on reproducing this. It kind of sounds like it's something to do with path names at creation time, so please include the steps you use when creating the project (which files and their path names will probably be important also). I tried this with notepad and Xemacs. (Of course I'm assuming that this is an SN bug.) Ian. Berek wrote: > > I have the same problem with SN and NT 4.0. > > ----- Original Message ----- > From: "John Smyder" > To: ; > Sent: Wednesday, March 07, 2001 11:26 > Subject: Command Line Problem with Source Navigator and EditPad Pro > > > I just received my license for EditPad Pro Ver. 4.1.3 and I have plans of > > using it with Red Hat's "Source Navigator" version 4.5.2. However, I am > > noticing a small anomaly when setting up the Source Navigator to call > > EditPad Pro in a Windows 2000 environment. When Source Navigator makes a > > call to EditPad Pro it passes the file name and path to open. In Win 98 > > this all works perfectly. In Win 2000 EditPad Pro receives only the > > projects root path and not the sub-directory that my C file is in (i.e. > > c:\firware4_2\snacc.c instead of c:\firmware4_2\app\snacc.c). > > > > Like I said this works perfectly in Win 98 and I'm sending this email to > > the Red Hat team too. I'm not sure if the problem lies with EditPad Pro, > > Source Navigator or Windows 2000. But I have my suspicions (windows). > > > > Just thought you might want to know about this behavior. > > > > Regards, > > > > John W. Smyder > > > >