GNU bug report logs - #29608
python.el movement functions

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Alex Branham <alex.branham <at> gmail.com>
Cc: Glenn Morris <rgm <at> gnu.org>, 29608 <at> debbugs.gnu.org
Subject: bug#29608: python.el movement functions
Date: Sat, 26 Jun 2021 16:13:12 +0200

Alex Branham <alex.branham <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.