all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 33054@debbugs.gnu.org
Subject: bug#33054: 25.2; diff-model: M-k kills wrong hunk
Date: 16 Oct 2018 18:26:37 -0000	[thread overview]
Message-ID: <20181016182637.4367.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.2215.1539636970.1284.bug-gnu-emacs@gnu.org>

Hello, Dima:

In article <mailman.2215.1539636970.1284.bug-gnu-emacs@gnu.org> you wrote:
> [-- text/plain, encoding 7bit, charset: US-ASCII, 14 lines --]

> I'm using a very recent build: e4896856172

Very recent?  That was from September 8th, over a month ago.  ;-)

> Steps to reproduce bug:

> - Open attached diff. Emacs should open it in diff-mode
> - Put point on 'd' in the second "diff": (goto-char 98)
> - M-k

> This should kill the hunk we're on.

It does that for me.

> We are unambiguously sitting on the second hunk, but the latest
> diff-mode is confused, thinks we're on the first hunk, and kills that
> instead. Kinda. Moving the point even one character forward makes it
> work.

It works for me anyway (With a build updated at most a day ago).  I've
looked at the git log for diff-mode.el, and nobody's changed anything
relevant, that I can see, since early September.

What's your environment?  Operating system, and so on?

Or, maybe something really wierd is happening, and it would stop
happening on an up to date snapshot of Emacs.

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2018-10-16 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 20:56 bug#33054: 25.2; diff-model: M-k kills wrong hunk Dima Kogan
     [not found] ` <mailman.2215.1539636970.1284.bug-gnu-emacs@gnu.org>
2018-10-16 18:26   ` Alan Mackenzie [this message]
2018-10-16 19:06     ` dima
2018-10-16 19:27       ` Alan Mackenzie

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

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

  git send-email \
    --in-reply-to=20181016182637.4367.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=33054@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.