[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22934: 24.5; python-mode: evaluating whole buffer after edit gives r
From: |
Lars Ingebrigtsen |
Subject: |
bug#22934: 24.5; python-mode: evaluating whole buffer after edit gives right lines in error stack trace but quick navigation doesn't lead to correct lines (offset corespodnce to number of added lines) |
Date: |
Thu, 03 Dec 2020 10:21:45 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> I see:
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/home/user/tmp/my.py", line 8, in <module>
> hello(True)
> File "/home/user/tmp/my.py", line 6, in hello
> raise Exception("xxx")
>
> and line:
>
> File "/home/user/tmp/my.py", line 6, in hello
>
> is clickable and leads to line **7** in a file. But actually error in line 6
> as reported by Python inferior process. Just add more lines to better see
> effect.
This should now be fixed in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#22934: 24.5; python-mode: evaluating whole buffer after edit gives right lines in error stack trace but quick navigation doesn't lead to correct lines (offset corespodnce to number of added lines),
Lars Ingebrigtsen <=