unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Robert Cochran <robert-emacs@cochranmail.com>
Cc: 24427@debbugs.gnu.org
Subject: bug#24427: 25.1.50; end-of-defun jumps too far
Date: Thu, 22 Sep 2016 12:35:22 +0200	[thread overview]
Message-ID: <87r38cw7bp.fsf@mbork.pl> (raw)
In-Reply-To: <87twd9vxaj.fsf@mbork.pl>


On 2016-09-21, at 21:59, Marcin Borkowski <mbork@mbork.pl> wrote:

> On 2016-09-20, at 20:31, Robert Cochran <robert-emacs@cochranmail.com> wrote:
>
>> Ping!
>>
>> Has anyone had the opportunity to look over this?
>
> Hi,
>
> I'm extremely busy right now, but I looked into it and it seemed to
> break some other tests of mine.  I haven't yet found the problem (or
> even confirmed it), but I expect to have some time for it in the next
> few days.

OK, so here's the problem I found when running my personal tests for my
`mark-defun'.

Consider this Elisp buffer:

--8<---------------cut here---------------start------------->8---
;; Comment header

(defun func-1 (arg)
  "docstring"
  body)
-!-
;; Comment before a defun
(defun func-2 (arg)
  "docstring"
  body)

(defun func-3 (arg)
  "docstring"
  body)
(defun func-4 (arg)
  "docstring"
  body)

;; end
--8<---------------cut here---------------end--------------->8---

where -!- means the point location.  Now press C-u 2 C-M-e, and you
moved by one defun instead of two.

Best,

-- 
Marcin Borkowski





  reply	other threads:[~2016-09-22 10:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 12:53 bug#24427: 25.1.50; end-of-defun jumps too far Marcin Borkowski
2016-09-13 20:26 ` Robert Cochran
2016-09-13 20:30   ` Robert Cochran
2016-09-20 18:31     ` Robert Cochran
2016-09-21 19:59       ` Marcin Borkowski
2016-09-22 10:35         ` Marcin Borkowski [this message]
2016-10-02  5:12           ` Robert Cochran
2018-06-17 17:50             ` Noam Postavsky
2020-08-11 14:03               ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r38cw7bp.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=24427@debbugs.gnu.org \
    --cc=robert-emacs@cochranmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).