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: Wed, 07 Mar 2001 09:21:00 -0000 Message-id: <3AA66E0F.17D080B7@redhat.com> References: <5.0.2.1.0.20010307111513.00a62e40@mail.clarityconnect.com> <000e01c0a729$3387a800$3e6410ac@concord.com> X-SW-Source: 2001-q1/msg00202.html Berek wrote: > > I have the same problem with SN and NT 4.0. Well then, that makes it a little easier. Ian. > ----- 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 > > > >