[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29608: python.el movement functions
From: |
Lars Ingebrigtsen |
Subject: |
bug#29608: python.el movement functions |
Date: |
Sat, 26 Jun 2021 16:13:12 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Alex Branham <alex.branham@gmail.com> writes:
> Shouldn't python-nav-forward-block actually navigate forward, though?
> And if we're on the last block in the buffer, just leave point at the
> end?
Well, the `M-e' doc string says "Move forward to next block of code.",
so if there is no next code block, then there's nothing to move to. So
I think it's working as intended, I guess? It does seem slightly
eccentric -- I'd also expect it to move to the end of the current block,
but then there's `python-nav-end-of-block' for that.
But I don't think there's anything to fix here, so I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#29608: python.el movement functions,
Lars Ingebrigtsen <=