public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Latest Cygwin update and Emacs in Mintty
Date: Sat, 17 Jun 2017 08:20:00 -0000	[thread overview]
Message-ID: <87d1a36n5n.fsf@Rainer.invalid> (raw)
In-Reply-To: <0367a274-06fb-90bb-0ac0-35c0c804c8af@cornell.edu> (Ken Brown's	message of "Fri, 16 Jun 2017 19:46:21 -0400")

Ken Brown writes:
>> No, it really was a Cygwin update (to 2.7.0-1).  The Emacs update was
>> before that and it had worked right up to that update.
>
> Sorry, I misunderstood what you meant by "Cygwin update".  I
> understand now.  I'll try to do a bisection of the Cygwin sources.  It
> may be a few days before I get to this.

It may be possible that the coreutils update messed up things in a way
that I don't understand, but that's unlikely.  Or vim might have
delivered a file that conflicts with something from Emacs, but Emacs has
since been updated again and so that conflict would have flipped in
favor of Emacs at those times, which I didn't observe (and no such
conflicts seem to exist in the package file listings at the current
moment).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-06-17  8:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 17:47 Achim Gratz
2017-06-14 19:00 ` Achim Gratz
2017-06-15 10:47   ` Ken Brown
2017-06-15 13:35     ` Ken Brown
2017-06-15 18:43       ` Achim Gratz
2017-06-15 21:48         ` Ken Brown
2017-06-16 18:27           ` Achim Gratz
2017-06-16 23:46             ` Ken Brown
2017-06-17  8:20               ` Achim Gratz [this message]
2017-06-17 12:58                 ` Ken Brown
2017-06-17 14:38                   ` Achim Gratz
2017-06-17 17:54                     ` Ken Brown
2017-06-17 21:04                       ` Achim Gratz
2017-06-27 18:55                         ` Achim Gratz
2017-06-15 18:43       ` Brian Inglis

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=87d1a36n5n.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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.
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).