headers
Surendra Singhi | 1 Jun 2005 09:23
Face

buffer not set for parsing(Error)

Hello,
  When I try to use semantic with java-mode(cc-mode 5.30.10 not JDE) on XEmacs 
I get the error with the backtrace (given below). In particular when I try to
do "senator-minor-mode".
I am using XEmacs 21.4.13 and cedet 1.0pre2.

How can I set the buffer for parsing? In c-mode, I in fact don't need to do
anything and the senator starts up automatically.

Any help on this is appreciated. Thanks in advance.

Debugger entered--Lisp error: (error "Buffer temp.java was not set up for parsing")
  signal(error ("Buffer temp.java was not set up for parsing"))
  cerror("Buffer %s was not set up for parsing" "temp.java")
  apply(cerror "Buffer %s was not set up for parsing" "temp.java")
  error("Buffer %s was not set up for parsing" "temp.java")
  (progn (setq senator-minor-mode nil) (error "Buffer %s was not set up for parsing" (buffer-name)))
  (if (not (and ... ...)) (progn (setq senator-minor-mode nil) (error "Buffer %s was not set up for parsing"
...)) (if (featurep ...) (easy-menu-add senator-minor-menu senator-mode-map))
(semantic-make-local-hook (quote semantic-after-toplevel-cache-change-hook)) (add-hook (quote
semantic-after-toplevel-cache-change-hook) (quote senator-completion-cache-flush-fcn) nil t)
(semantic-make-local-hook (quote semantic-after-partial-cache-change-hook)) (add-hook (quote
semantic-after-partial-cache-change-hook) (quote senator-completion-cache-flush-fcn) nil t))
  (if senator-minor-mode (if (not ...) (progn ... ...) (if ... ...) (semantic-make-local-hook ...)
(add-hook ... ... nil t) (semantic-make-local-hook ...) (add-hook ... ... nil t)) (if (featurep ...)
(easy-menu-remove senator-minor-menu)) (remove-hook (quote
semantic-after-toplevel-cache-change-hook) (quote senator-completion-cache-flush-fcn) t)
(remove-hook (quote semantic-after-partial-cache-change-hook) (quote
senator-completion-cache-flush-fcn) t) (setq senator-isearch-semantic-mode nil))
  senator-minor-mode-setup()
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nicholas Sandow | 4 Jun 2005 13:10
Favicon

running CEDET from CVS

How do I run CEDET after doing a fresh checkout?

When I type `make', I get:

make[1]: Entering directory `/home/njsand/tmp/cedet/common'
Makefile is out of date! It needs to be regenerated by EDE.
If you have not modified Project.ede, you can use touch to update the 
Makefile time stamp.
make[1]: *** [Makefile] Error 1
make[1]: Leaving directory `/home/njsand/tmp/cedet/common'
make: *** [common] Error 2

The solutions racing in my mind are "just use touch on the Makefiles" or 
"load up 1.0pre2 and regenerate the Makefile as requested", but I 
thought I'd ask anyway...

The reason I'm going to this trouble is simply that I've found a bug and 
I wanted to test with the latest code before reporting it.  Well, now's 
my chance to report it:

With cedet-1.0pre2 I encountered a bug when using Sticky Func mode in 
some Java files.

1. Select "Sticky Func / In This Buffer".  This works fine.

2. Select "Sticky Func / Globally". This works fine

3. Select "Sticky Func / Globally" again to toggle the mode off. 
Nothing happens, though. The header line is still there.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joakim Verona | 4 Jun 2005 14:33
Picon
Gravatar

idea for cedet and bugtracker integration

I have a small idea for a new feature.

I use a bugtracker called "trac" for a java project.

It would be nice if one could write in the source,
"see #211 for details about this change"

Where #211 would refer to bug 211 in the trac instance for this
project.

The #211 would be interpreted as a url, and you would wind up inside
emacs-w3m pointing at the correct trac bug in the project the source
file was in.

That would mean that one would have to store the trac instance url
inside a project file, that cedet would have to know about, like the
jde project file.

Cedet doesnt really have its own project file does it? 

Anyway, this was just a random idea, thanks for listening.

If the idea were ever to be implemented, one could of course think up
a plugin system to use savannah or sourceforge as bugtracker backends
and so on. 

--

-- 
Joakim Verona
www.verona.se
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eric M. Ludlam | 4 Jun 2005 15:25
Gravatar

Re[1]: running CEDET from CVS

>>> Nicholas Sandow <njsand <at> internode.on.net> seems to think that:
>How do I run CEDET after doing a fresh checkout?
>
>When I type `make', I get:
>
>make[1]: Entering directory `/home/njsand/tmp/cedet/common'
>Makefile is out of date! It needs to be regenerated by EDE.
>If you have not modified Project.ede, you can use touch to update the 
>Makefile time stamp.
>make[1]: *** [Makefile] Error 1
>make[1]: Leaving directory `/home/njsand/tmp/cedet/common'
>make: *** [common] Error 2
>
>The solutions racing in my mind are "just use touch on the Makefiles" or 
>"load up 1.0pre2 and regenerate the Makefile as requested", but I 
>thought I'd ask anyway...

Yes, touch is a reasonable way to fix this problem from CVS.  I try to
check in Project files first, then Makefile, but sometimes it happens
in the other order.

>The reason I'm going to this trouble is simply that I've found a bug and 
>I wanted to test with the latest code before reporting it.  Well, now's 
>my chance to report it:
>
>
>With cedet-1.0pre2 I encountered a bug when using Sticky Func mode in 
>some Java files.
>
>1. Select "Sticky Func / In This Buffer".  This works fine.
(Continue reading)

Permalink | Reply | 0 comments |
headers
David PONCE | 6 Jun 2005 11:12
Picon

Re: running CEDET from CVS

Hello,

[...]
>>The reason I'm going to this trouble is simply that I've found a bug and 
>>I wanted to test with the latest code before reporting it.  Well, now's 
>>my chance to report it:
>>
>>
>>With cedet-1.0pre2 I encountered a bug when using Sticky Func mode in 
>>some Java files.
>>
>>1. Select "Sticky Func / In This Buffer".  This works fine.
>>
>>2. Select "Sticky Func / Globally". This works fine
>>
>>3. Select "Sticky Func / Globally" again to toggle the mode off. 
>>Nothing happens, though. The header line is still there.
>>
>>In fact, after (3), it seems impossible to turn off sticky func mode via 
>>the menu or with M-x semantic-stickyfunc-mode.
>>
> 
>   [ ... ]
> 
> Hmmm, I see that using "Globally" turns it off ok, but once global is
> on, turning it off locally does not.  Seems to require some
> investigation.

Could you please try the following patch.  It gives good result for
me.  If it solves the problem I will commit it.  It is a shame that
(Continue reading)

Permalink | Reply | 1 comment |
headers
klaus.berndl | 7 Jun 2005 15:09
Picon

RE: [ECB-list] ECB-2.31 -- save-buffer issue - problem report

Hi Jeff,

In the backtrace i see that ad-Orig-re-search-forward causes the error.
Seems that a package has adviced re-search-forward which causes this error.
I can only say that ECB does not advice this function. But you can easily test
if the problem is an ECB-problem: Just try if the error also occurs with
deactivated ECB! 

 <at> cedet-guys: Do you advice this function? Maybe senator.....

 <at> Jeff: perform a grep in all your lisp-file you load into emacs if there
Is a:

(defadvice re-search-forward...)

I have forwarded your report to the CEDET-list....

Ciao,
Klaus

Rancier, Jeff wrote:
> To: ecb-list <at> lists.sourceforge.net
> Subject: ECB-2.31 -- save-buffer errors
> X-Reporter-Void-Vars-Found: ecb-max-lisp-eval-depth-old
> ecb-max-specpdl-size-old ecb-use-semantic-grouping
> --text follows this line--
> 
> Please enter the details of your bug report here
> 
> I don't know if this is exactly an ECB issue or not, the backtrace is
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rancier, Jeff | 7 Jun 2005 15:30

RE: [ECB-list] ECB-2.31 -- save-buffer issue - problem report

I think it may be in sgml-mode.el.  There's a few FIXME: lines in some of
the re-search-forward's.  I see if James Clark has a more updated version.
Thanks.

| -----Original Message-----
| From: klaus.berndl <at> sdm.de [mailto:klaus.berndl <at> sdm.de] 
| Sent: Tuesday, June 07, 2005 9:09 AM
| To: Rancier, Jeff; Ecb-List <at> Lists.Sourceforge.Net
| Cc: Cedet-devel <at> lists.sourceforge.net
| Subject: RE: [ECB-list] ECB-2.31 -- save-buffer issue - problem report
| 
| 
| Hi Jeff,
| 
| In the backtrace i see that ad-Orig-re-search-forward causes 
| the error.
| Seems that a package has adviced re-search-forward which 
| causes this error.
| I can only say that ECB does not advice this function. But 
| you can easily test
| if the problem is an ECB-problem: Just try if the error also 
| occurs with
| deactivated ECB! 
| 
|  <at> cedet-guys: Do you advice this function? Maybe senator.....
| 
|  <at> Jeff: perform a grep in all your lisp-file you load into 
| emacs if there
| Is a:
|
(Continue reading)

Permalink | Reply | 0 comments |
headers
David PONCE | 7 Jun 2005 15:50
Picon

Re: RE: [ECB-list] ECB-2.31 -- save-buffer issue - problem report

Hi Klaus,

> In the backtrace i see that ad-Orig-re-search-forward causes the
> error.  Seems that a package has adviced re-search-forward which
> causes this error.  I can only say that ECB does not advice this
> function. But you can easily test if the problem is an ECB-problem:
> Just try if the error also occurs with deactivated ECB!
> 
>  <at> cedet-guys: Do you advice this function? Maybe senator.....
[...]

Yes `re-search-forward' is advised in senator to implement
`senator-isearch-semantic-mode'.  However it is not the problem as
your backtrace shows that the built-in `re-search-forward' is executed
through `ad-Orig-re-search-forward'.

If fact it appears to be a bug in `semantic-html.el' in semantic 2.0beta3,
in the function `semantic-html-extract-section-name', which seems to have
been fixed by Eric in current CVS version (semantic 2.0pre2).

Sincerely,
David

-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
Permalink | Reply | 2 comments |
headers
Eric M. Ludlam | 8 Jun 2005 18:01
Gravatar

Re[1]: Parent classes aren't jump-able

>I am in the process of writing a new language grammar for semantic,
>mostly for use with ECB. At this point I can show all pertinent
>information in the methods-buffer -- classes, modules, methods,
>etc. Each class has a "Parents" sub-tab if it has a superclass, but
>the classes under the "Parents" tab are non-jump-able, i.e.  nothing
>happens when I click on one in the methods-buffer, even if the
>superclass is defined in the same file. How do I fix this?
>
>Also, is there anything I should do with regard to ECB when
>implementing a new language, or is telling Semantic about the language
>all I need to do?
  [ ... ]

Hi,

  If I remember rightly, ECB uses the semantic library function
`semantic-adopt-external-members' to build the methods table.  This
will allow methods defined outside the physical character bounds of a
class definition to be grouped logically together.

  When this happens, that parent moniker is a faux tag, and not
jumpable unless semantic can also find the original parent tag by
name, in which case it is substituted in.

  Knowing more about the language you are parsing and what semantic
features you have overridden would assist in better answering your question.

Eric

--

--
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eric M. Ludlam | 8 Jun 2005 19:25
Gravatar

Re[2]: [ECB-list] Parent classes aren't jump-able

>>> Daniel Debertin <airboss+ecb <at> nodewarrior.org> seems to think that:
>Hi,
>
>"Eric M. Ludlam" <eric <at> siege-engine.com> writes:
>
>>   Knowing more about the language you are parsing and what semantic
>> features you have overridden would assist in better answering your question.
>
>I neglected to mention it -- the language I'm parsing is Ruby. At
>present I haven't defined any overrides; I'm still at the stage of
>getting the grammar and lexer working properly. This is the sort of
>code I'm parsing:
>
>module FooMod   
>  class FooClass
>    def thingy()
>      d
>    end
>  end
>
>  class BarClass < FooClass    # '<' denotes inheritance
>    def foo(arg)
>      z
>    end
>  end
>end
>
>(I'm using TYPE-TAG for both modules and classes.)
>
>Oddly enough, if I remove the module definition (comment out "module
(Continue reading)

Permalink | Reply | 1 comment |

Gmane