what about a symlink for chirpc -> chirp.py ? From: Kosta Arvanitis kosta@alumni.uvic.ca To: "chirp_devel@intrepid.danplanet.com" chirp_devel@intrepid.danplanet.com Sent: Wednesday, February 25, 2015 2:53 AM Subject: Re: [chirp_devel] [PATCH 2/9] Rename chirp.py as chirpc (#2343)
Is 'chirpc' a compiler?
----------------------------------------
Date: Wed, 25 Feb 2015 00:34:21 -0800 From: zach@mandolincreekfarm.com To: chirp_devel@intrepid.danplanet.com Subject: Re: [chirp_devel] [PATCH 2/9] Rename chirp.py as chirpc (#2343)
On 02/25/2015 12:29 AM, Kosta Arvanitis wrote:
Not really keen on this change; its not as intuitive to me as the original. %> python chirp.py Feels pretty good.
My intention is to clean up the CLI tool such that it can be installed alongside chirpw (e.g. in /usr/bin). At that point, you would simply run 'chirpc', and that sounds a lot more polished than 'chirp.py'.
-- Zach Welch Mandolin Creek Farm www.mandolincreekfarm.com farm: 541-453-4131 cell: 541-740-3410 _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
_______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers