[zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]

[zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]

[Richard Stallman]

Would someone please DTRT then ack?

------- Start of forwarded message -------
X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY 
	autolearn=failed version=3.1.0
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-disposition:message-id:content-type:content-transfer-encoding;
	b=Jn5rqEqL21IvkbVEcnf/wroXN8AD9SB0vuddjJMz07QDAkSI6nwER0E5kebZtZ9e3TBzNmr0hDmRfyip9iRkUArPe/4kqC99vvwaXXfIXXFqysLnqeCvUWn6inBK6IFcticKs6dOFFXNO9Vi7XKjqAZMS3taYxtH0yhcii2MBZM=
From: Levin <zslevin@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Date: Fri, 3 Aug 2007 11:29:05 +0800
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="gb18030"
Subject: [Bug] Emacs frozen in python mode with which-func & narrow

Start emacs with 'emacs -Q', open a python file with content below:
- --8<--8<--
#This is a comment

def f():
    print "Hello world"
- --8<--8<--

Then narrow region to avoid display of comment:
- --8<--8<--

def f():
    print "Hello world"
- --8<--8<--

OK, now `M-<', `M-x which-func-mode', `M-x indent-relative'.

Then emacs will froze. `C-g' has no effect.

- --
Levin


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------

Re: [zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]

[Paul Pogonyshev]

Richard Stallman wrote:
> Would someone please DTRT then ack?
> 
> ------- Start of forwarded message -------
> [...]
> Subject: [Bug] Emacs frozen in python mode with which-func & narrow

I believe this is already fixed by this change (at least I cannot
reproduce):

2007-07-31  Paul Pogonyshev  <pogonyshev@gmx.net>

	* progmodes/python.el (python-current-defun): Adjust to never fall
	into infinite loop.

Levin, can you please test with latest CVS copy?

Paul

Re: [zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]

[Levin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 806 bytes --]

Yes, it has been fixed with the latest CVS copy. Thanks.

On Saturday 04 August 2007 23:36:54£¬Paul Pogonyshev Wrote£º
> Richard Stallman wrote:
> > Would someone please DTRT then ack?
> >
> > ------- Start of forwarded message -------
> > [...]
> > Subject: [Bug] Emacs frozen in python mode with which-func & narrow
>
> I believe this is already fixed by this change (at least I cannot
> reproduce):
>
> 2007-07-31  Paul Pogonyshev  <pogonyshev@gmx.net>
>
> 	* progmodes/python.el (python-current-defun): Adjust to never fall
> 	into infinite loop.
>
> Levin, can you please test with latest CVS copy?
>
> Paul
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel


Levin

Re: [zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]

[Paul Pogonyshev]

Levin wrote:
> Yes, it has been fixed with the latest CVS copy. Thanks.

Hm, it stroke me suddenly that your bug report might have been
about stable Emacs release (22.1.)  Is that the case?  Because
the patch wouldn't apply cleanly to 22.2 branch, so then it's
needed to backport it.

Paul

Re: [zslevin@gmail.com: [Bug] Emacs frozen in python mode with which-func & narrow]:

[Levin]

Paul Pogonyshev Wrote:
> Levin wrote:
> > Yes, it has been fixed with the latest CVS copy. Thanks.
>
> Hm, it stroke me suddenly that your bug report might have been
> about stable Emacs release (22.1.)  Is that the case?  Because
> the patch wouldn't apply cleanly to 22.2 branch, so then it's
> needed to backport it.
>
> Paul

I'm using CVS copy. But I try 22.1 version just now: which-func-mode is not 
available in python mode (I toggle it, but nothing displayed), and the bug 
does not exist.

Levin