unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mutiny " <mutiny.mutiny@rediffmail.com>
To: <26394@debbugs.gnu.org>
Cc: npostavs@users.sourceforge.net
Subject: bug#26394: 26394
Date: 8 Apr 2017 19:06:02 -0000	[thread overview]
Message-ID: <20170408190602.18206.qmail@f6mail-235-206.rediffmail.com> (raw)
In-Reply-To: <20170407194540.8601.qmail@f6mail-235-77.rediffmail.com>

[-- Attachment #1: Type: text/plain, Size: 92 bytes --]

with the patches 88532ae..b7d6160 ediff behaves normal again. Thanks a lot for your support!

[-- Attachment #2: Type: text/html, Size: 96 bytes --]

      parent reply	other threads:[~2017-04-08 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 19:45 bug#26394: 26.0.50; ediff file-local-copy: Wrong type argument: stringp, nil Mutiny 
2017-04-07 20:41 ` Noam Postavsky
2017-04-08 19:06 ` Mutiny  [this message]

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=20170408190602.18206.qmail@f6mail-235-206.rediffmail.com \
    --to=mutiny.mutiny@rediffmail.com \
    --cc=26394@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.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 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).