From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117772 invoked by alias); 23 Oct 2016 22:20:20 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 117753 invoked by uid 89); 23 Oct 2016 22:20:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=fish, H*Ad:D*gov, heck, H*r:Unknown X-HELO: blaine.gmane.org Received: from Unknown (HELO blaine.gmane.org) (195.159.176.226) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 23 Oct 2016 22:20:09 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1byR7J-0000oE-Ge for cygwin@cygwin.com; Mon, 24 Oct 2016 00:19:45 +0200 To: cygwin@cygwin.com From: Andrew Schulman Subject: Re: bc version has issue with \r when run from cmd Date: Mon, 24 Oct 2016 06:13:00 -0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00259.txt.bz2 > >From: "L. A. Walsh" > >Date: Sat, 22 Oct 2016 15:52:42 -0700 > > To L.A. Walsh. > > I understand all that but what i'm saying is that version 1.06 (not > 1.06.95, which cygwin is using, but 1.06, which Gow uses), So, version > 1.06 Doesn't have a problem with the fact that cmd sends a \r So, > if one doesn't want to call it a bug, then one can call it a lost > feature, useful feature of 1.06 (allowing bc to conveniently also be > used from cmd), and that beneficial flexible feature was lost in > 1.06.95 Hi. I adopted the bc package about a year ago, since fish uses it and I maintain fish for Cygwin. I think L.A. is right that because this is an issue of integration between Cygwin and cmd, it's in the category of a nice-to-have feature. But I get that it would be useful for you, and maybe for others too. I haven't looked at the bc source code. It could take some time to find where the issue is. A place to start would be to compare the code archives: http://ftp.gnu.org/gnu/bc/bc-1.06.tar.gz http://alpha.gnu.org/gnu/bc/bc-1.06.95.tar.bz2 If you were to localize the problem in the source code and even propose a patch, that would make it a lot more likely to get the problem fixed. Heck, you might even get a gold star. I maintain the gold star page too :) Andrew -- 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