public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Berek <berek@usa.net>,
	sourcenav@sources.redhat.com,
	John Smyder <jwsmyder@wysoft-tech.com>
Subject: Re: Command Line Problem with Source Navigator and EditPad Pro
Date: Thu, 08 Mar 2001 14:58:00 -0000	[thread overview]
Message-ID: <3AA80E7B.CD39A0B6@redhat.com> (raw)
In-Reply-To: <3AA7FBC9.F068BE3C@redhat.com>

Something I should have say at the start.

If you set the environment variable SN_DEBUG to
9, and then run Source-Navigator you will get
a log file zznavig01.log (or something like that).

If you grep the log file for the string "Editor command"
you will get the command line of that SN is using
to launch the external editor.

Ian.




Ian Roxborough wrote:
> 
> 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" <jwsmyder@wysoft-tech.com>
> > To: <support@editpadpro.com>; <sourcenav@sources.redhat.com>
> > 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
> > >
> > >

  reply	other threads:[~2001-03-08 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07  8:26 John Smyder
2001-03-07  9:08 ` Berek
2001-03-07  9:21   ` Ian Roxborough
2001-03-08 13:38   ` Ian Roxborough
2001-03-08 14:58     ` Ian Roxborough [this message]
2001-03-07  9:20 ` Ian Roxborough

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=3AA80E7B.CD39A0B6@redhat.com \
    --to=irox@redhat.com \
    --cc=berek@usa.net \
    --cc=jwsmyder@wysoft-tech.com \
    --cc=sourcenav@sources.redhat.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).