emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#33054: closed (25.2; diff-model: M-k kills wrong h


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#33054: closed (25.2; diff-model: M-k kills wrong hunk)
Date: Tue, 16 Oct 2018 19:07:01 +0000

Your message dated Tue, 16 Oct 2018 12:06:10 -0700
with message-id <address@hidden>
and subject line Re: bug#33054: 25.2; diff-model: M-k kills wrong hunk
has caused the debbugs.gnu.org bug report #33054,
regarding 25.2; diff-model: M-k kills wrong hunk
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
33054: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33054
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.2; diff-model: M-k kills wrong hunk Date: Mon, 15 Oct 2018 13:56:27 -0700
I'm using a very recent build: e4896856172

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. 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.

diff --git a/111.py b/111.py
--- a/111.py
+++ b/111.py
@@ -154,3 +154,3 @@
 
-    aaa
+    bbb
 
diff --git a/222.py b/222.py
--- a/222.py
+++ b/222.py
@@ -224,3 +230,3 @@ writemodel(m_to)
     asdf
-    21234
+    345
     zxcv

--- End Message ---
--- Begin Message --- Subject: Re: bug#33054: 25.2; diff-model: M-k kills wrong hunk Date: Tue, 16 Oct 2018 12:06:10 -0700 User-agent: mu4e 0.9.17; emacs 27.0.50
Alan Mackenzie <address@hidden> writes:

>> 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.

Hi Alan. Thanks for the response. I was consistently seeing the problem,
but poked around a bit more after seeing your comment. I found the
issue: I was doing something wrong (specifics completely uninteresting).
There is no issue, and I'm closing the bug. Sorry for the noise.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]