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: Fri, 16 Jun 2017 18:27:00 -0000	[thread overview]
Message-ID: <87y3srvld2.fsf@Rainer.invalid> (raw)
In-Reply-To: <e9c7af6c-19e6-04af-dd3d-db15291710e6@cornell.edu> (Ken Brown's	message of "Thu, 15 Jun 2017 17:48:40 -0400")

Ken Brown writes:
> Your original report, written on February 22, said that the problem
> started after the latest Cygwin update.  That means you would have
> installed emacs-25.1, if Emacs was updated at all.

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.

> But I've just checked that the problem already exists in emacs-24.5.
> So maybe the problem was triggered by an update of some package other
> than Emacs, Mintty being the most obvious guess.  Can you check your
> /var/log/setup.log to see what was updated around February 22?

The only other two things that were updated that day (along with some
perl distributions that can't possibly be related, if only because I've
locally updated them before I got them back from the offical Cygwin
packages) was coreutils and vim.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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-16 18:27 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 [this message]
2017-06-16 23:46             ` Ken Brown
2017-06-17  8:20               ` Achim Gratz
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=87y3srvld2.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).