From mboxrd@z Thu Jan 1 00:00:00 1970 From: Merlyn Cousins To: Ian Roxborough , sourcenav@sources.redhat.com Subject: include file problems Date: Sat, 28 Oct 2000 10:26:00 -0000 Message-id: <39FB0C26.70804@dialisdn.com> X-SW-Source: 2000-q4/msg00161.html Ok..first i'd like to thank you for responding. In answer to your questions...I'm a linux man I'm using SuSE 6.1 (with compiled version of snavigator) I had no errors during the compilation. everything else seems to work but the include stuff. Which really gives me problems for obvious reasons. as far as double clicking on include files..yes i do that and the Prog responds with (file not found) but it's there. It seems to do this anytime the syntax of #include is used. also a quick question for you... Why do you have to click on the include files to bring them into the project? this can be a real pain!! shouldn't there be a option of some sort that Snav does a recursive search and auto loads the #include files? I mean if these files were in the directory or a subdirectory of the current project and a new project was created, would not Snav auto bring them in? having to double click through the tree is a real time waster. So anyway thanxs again.. If i can get these points points worked out Snav along with gvim will be a GREAT aid to me in helping to Understand (reverse engineer) source code. Hi, I'm assuming that you are double clicking on the include file in the include browser. (?) What OS are you running on? I've heard of this bug before but haven't managed to reproduce it on my Red Hat 6.2 box. (This is meant to problems on Windows version also.) Ian. "Merlyn(root)" wrote: > > Perhaps someone can help me with a problem I am having using snavigator. > when I'm trying to work with include files that use the form > #include for example (where a directory below the include > directory is used ..i.e let's say /usr/include) snavigator says (file not > found) now the file is there...and /usr/include is specified in the path for > the include file search. so why doesn't it work? > > if anyone can help I would great accpreciate it > > thanks > > merlyn