bug#20329: 25.0.50; Loading semantic breaks imenu

bug#20329: 25.0.50; Loading semantic breaks imenu

[Andreas Politz]

emacs -Q foo.py

(require 'semantic)
(normal-mode)
(call-interactively 'imenu)
  
=> (user-error "No items suitable for an index found in this buffer")

Merely loading semantic should not modify imenu-create-index-function in
all sorts of buffers.  It is also not so easy to get rid of it again.
One would have to either remove the semantic function from the various
mode hooks or install another function which runs *after* semantic's and
which would reinstall the regular imenu-create-index-function.

-ap

bug#20329: Acknowledgement (25.0.50; Loading semantic breaks imenu)

[Andreas Politz]

It seems that is only occuring with python-mode.

-ap

bug#20329: 25.0.50; Loading semantic breaks imenu

[Lars Ingebrigtsen]

Andreas Politz <politza@hochschule-trier.de> writes:

> emacs -Q foo.py
>
> (require 'semantic)
> (normal-mode)
> (call-interactively 'imenu)
>
> => (user-error "No items suitable for an index found in this buffer")

(I'm going through old bug reports that unfortunately got no response at
the time.)

I tried this recipe (in Emacs 28), with or without requiring semantic,
and I get the same error message no matter what.  So loading semantic
doesn't seem to affect anything.

But I'm not an imenu user, so I'm not sure what's supposed to happen
here.

Is this a problem that's gone away in the years since it was reported?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#20329: 25.0.50; Loading semantic breaks imenu

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Is this a problem that's gone away in the years since it was reported?

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#20329: 25.0.50; Loading semantic breaks imenu

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> More information was requested, but no response was given within a
> month, so I'm closing this bug report.  If the problem still exists,
> please respond to this email and we'll reopen the bug report.

Sorry; I hit the wrong button here -- the bug report has not been closed,
and I got a reply to my question.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#20329: 25.0.50; Loading semantic breaks imenu

[Stefan Kangas]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> More information was requested, but no response was given within a
>> month, so I'm closing this bug report.  If the problem still exists,
>> please respond to this email and we'll reopen the bug report.
>
> Sorry; I hit the wrong button here -- the bug report has not been closed,
> and I got a reply to my question.

I don't see anything in the bug tracker?  Did you get the reply
privately perhaps?

bug#20329: 25.0.50; Loading semantic breaks imenu

[Lars Ingebrigtsen]

Stefan Kangas <stefan@marxist.se> writes:

> I don't see anything in the bug tracker?  Did you get the reply
> privately perhaps?

I've had a look around, and apparently not...  So I don't know what I
was referring to.

So, since I can't reproduce the problem, and there apparently wasn't any
response here, I'm closing the bug now.  (If this problem is still
present, please respond to the debbugs address and we'll reopen.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#20329: 25.0.50; Loading semantic breaks imenu

[Stefan Kangas]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So, since I can't reproduce the problem, and there apparently wasn't any
> response here, I'm closing the bug now.  (If this problem is still
> present, please respond to the debbugs address and we'll reopen.)

Thanks.

For posterity, I'll also point out that the email to the original poster
bounced.