all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 29916@debbugs.gnu.org
Subject: bug#29916: 26.0.90; CRLF in diff-command output breaks smerge hunk header parsing
Date: Mon, 1 Jan 2018 11:51:51 +0000	[thread overview]
Message-ID: <CAPM58ogDb7G8k8kSAX1ADZz8QpvFZ3_kJ3f_EMb_7RVKb+xEHQ@mail.gmail.com> (raw)
In-Reply-To: <CAPM58oi-mcMeF+ngNn1-vA7BSB9553PYgvvO-ZZufx44aw2Y_A@mail.gmail.com>

On 1 January 2018 at 11:02, Richard Copley <rcopley@gmail.com> wrote:
>> What am I missing?  Why do we get different results both for the
>> command binding and for the recipe?
>
> Read-only mode. For some reason, my copy of the patch file has
> the read-only attribute set. Sorry, I hadn't noticed that.

(But that doesn't explain why we're getting different results from
diff-goto-source.)

By the way, I can also trigger the error at the top level (i.e., not inside
a timer callback) by doing "diff-refine-hunk" interactively instead of
"diff-goto-source".





  reply	other threads:[~2018-01-01 11:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-31 18:33 bug#29916: 26.0.90; CRLF in diff-command output breaks smerge hunk header parsing Richard Copley
2017-12-31 19:06 ` Eli Zaretskii
2017-12-31 21:13   ` Richard Copley
2018-01-01  4:37     ` Eli Zaretskii
2018-01-01 11:02       ` Richard Copley
2018-01-01 11:51         ` Richard Copley [this message]
2018-01-01 16:39           ` Eli Zaretskii
2018-01-01 16:37         ` Eli Zaretskii
2018-01-01 23:23   ` Stefan Monnier
2018-01-02 21:41     ` Richard Copley
2018-01-03 15:18       ` Eli Zaretskii
2018-01-05  9:23         ` Eli Zaretskii

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=CAPM58ogDb7G8k8kSAX1ADZz8QpvFZ3_kJ3f_EMb_7RVKb+xEHQ@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=29916@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.