Re: ECB-2.40 -- error in ecb-select-source when opening file - FIXED!

Hi Nate,

Sorry for the late answer but i'm very busy these days...

Hmm, i don't believe that this is the root of the problem, simply because
ECB has nothing like the-semantic-variable-that-ECB-looks-at !!
ECB doesn't take into account any semantic- or ede-variables for ist
ecb-source-path!

But there is a variable ecb-source-path-function. What is the value?
And last but not least there are:
Command ecb-jde-update-ecb-source-paths ()
Option: ecb-jde-set-directories-buffer-to-jde-sourcepath

Can they be the root of the problem?

Ciao,
KLaus

-----Ursprüngliche Nachricht-----
Von: Nate Schley [mailto:[email protected]] 
Gesendet: Mittwoch, 13. Januar 2010 17:36
An: Berndl, Klaus
Betreff: Re: [ECB-list] ECB-2.40 -- error in ecb-select-source when opening file - FIXED!

Klaus,

I believe I'd mentioned seeing ECB show duplicate entries in the
directory window, and you had no idea why.

I think I have a clue.
in my .emacs, I have
|     (setq ecb-source-path semanticdb-project-roots)

so that in a freshly started emacs, the 2 variables are as follows:
|     ecb-source-path
|     ("W:/spw_st/st/src" "W:/spw_st/st/up")
|
|     semanticdb-project-roots
|     ("W:/spw_st/st/src" "W:/spw_st/st/up")

However, the directory buffer displays the following:
|     [+] w:/spw/system/mpack
|     [+] w:/spw_st/st/up
|     [+] w:/spw_st/st/src
|     [+] w:/spw_st/st/src
|     [+] w:/spw_st/st/up

So 2 directories are duplicated, but where does the 3rd come from?
A:  my .emacs also has the following (abridged, for brevity):
|  (ede-cpp-root-project
|   ...
|   :file (concat canon-root "spw_st/st/src/Makefile")
|   ...)
|  (ede-cpp-root-project
|   ...
|   :file (concat canon-root "spw_st/st/up/makefile")
|   ...)
|  (ede-cpp-root-project
|   ...
|   :file (concat canon-root "spw/system/mpack/setup.ksh")
|   ...)

(Note:  canon-root is "w:/")

Conclusion:  the ECB directories buffer is displaying both
1 - the directories indicated by ecb-source-path, *and*
2 - the directories indicated by the collection of
ede-cpp-root-projects (which I guess percolates to some other
cedet/semantic variable that ECB looks at -- unfortunately, semantic
doesn't give a bug-report dump like ECB does)

So, I think at a minimum the documentation for ecb-source-path should
be updated to clarify that ecb-source-path need not be set if
the-semantic-variable-that-ECB-looks-at is adequate.

As an uber-step, the directory-buffer should display the
(mathematical) "union" of directories indicated by ecb-source-path and
 the-semantic-variable-that-ECB-looks-at.  i.e. it should filter out
duplicate directories.

Finally, a strangeness that's not an issue, just perplexing to someone
trying to figure out what's up with ecb-source-path:  if I open up a
file in c:\temp, then the directories buffer shows c:/temp, but the
ecb-source-path now has the following value (formatted for
readability:)

|    ecb-source-path
|    ("W:/spw_st/st/src"
|     "W:/spw_st/st/up"
|     (#("c:/temp" 0 7
|        (help-echo "Mouse-2 toggles maximizing, mouse-3 displays a
popup-menu"))
|      #("c:/temp" 0 7
|        (help-echo "Mouse-2 toggles maximizing, mouse-3 displays a
popup-menu"))
|      )
|     )

The list entry for c:/temp doesn't agree with the documentation for
ecb-source-path (but everything I've tried associated with that entry
in ECB works fine, for example directory expansion, etc.)

Alles gute im neuen Jahr!

Nate

2009/6/9  <[email protected]>:
> Hi Nate,
>
> the bug is now fixed! Please remove any duplicates from ecb-source-path by
> hand and store for future sessions. Please update your ECB, either from CVs
> or with the updated CVS-snapshot. Now the history should work correctly.
> Please report if ECB adds duplicates to ecb-source-path or if now all is
> working fine for you...thanks for detecting this - was only a very small bug
> but with annoying consequences.....;-)
>
> Klaus
>



-- 
Thanks,

Nate

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev