From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin64 gnuplot 5.4 patchlevel 0 -all sciripts written for gnuplot 4.6 do not run.
Date: Wed, 02 Dec 2020 21:33:00 +0100 [thread overview]
Message-ID: <874kl4eyo3.fsf@Rainer.invalid> (raw)
In-Reply-To: <ce3bd72834ec47a492ac712d23741ed6@boeing.com> (Kramer Leonard via Cygwin's message of "Thu, 12 Nov 2020 21:35:40 +0000")
Kramer (US), Leonard via Cygwin writes:
> However, in gnuplot-base (5.4 patchlevel 0) The '$1' persistently
> translates to the second gnuplot-base command line argument (ie:
> ARG2). It is not supposed to be assigned to anything as far as I
> know. I have a work around but this appears to be a very severe bug.
The just released gnuplot 5.4.1 should have a bugfix for this, please test.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2020-12-02 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 21:35 Kramer (US), Leonard
2020-11-13 21:25 ` Achim Gratz
2020-12-02 20:33 ` Achim Gratz [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kl4eyo3.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).