From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv --list output in braces
Date: Fri, 16 Dec 2022 13:21:54 +0100 [thread overview]
Message-ID: <87o7s335el.fsf@Otto.invalid> (raw)
In-Reply-To: <1503426351.20221216141527@yandex.ru> (Andrey Repin via Cygwin's message of "Fri, 16 Dec 2022 14:15:27 +0300")
Andrey Repin via Cygwin writes:
> The question is a proverbial one: Who's guilty and what to do?
You have more than one Cygwin installation (cygwin1.dll) and the path is
different in different environments.
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
next prev parent reply other threads:[~2022-12-16 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:15 Andrey Repin
2022-12-16 12:21 ` ASSI [this message]
2022-12-16 12:30 ` Andrey Repin
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=87o7s335el.fsf@Otto.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).