Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=buckeyemailosu.onmicrosoft.com; s=selector1-buckeyemail-osu-edu; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5rhXZ1z6aQPS81OTjdoPZLZfE3mHsy34wuBaQB/uFLY=; b=lZIxd25AqVB3CGqt0rMgOC+oxsuAgRuKHULof2aHB2OAhAsY2ketRO8BLGUhkl9dIxUo7SOfUfBXUGohw2L6MEvYTwVwYrpxN8mWhzC+P7zrIS6JVOU6tHR/dCMyEWXsdHCDYa7GY/owUSvt9VdR+NhNnn76KwGKdp9bgW8AoOk= From: "Moore, Brandon A." To: "zsh-workers@zsh.org" Subject: Re: Bug report: `> filename` doesn't exit Thread-Topic: Bug report: `> filename` doesn't exit Thread-Index: AQHRox6rwVup8SsLcUuycTDrEixJ2p+i+uKL Date: Sat, 30 Apr 2016 20:42:22 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: zsh.org; dkim=none (message not signed) header.d=none;zsh.org; dmarc=none action=none header.from=buckeyemail.osu.edu; x-originating-ip: [2602:306:b843:96c0::40] x-ms-office365-filtering-correlation-id: 68fb71cd-e097-4cda-432a-08d37137ee8e x-microsoft-exchange-diagnostics: 1;BN3PR0101MB0947;5:3DwpIMbxg04DbrCf+hhW1atg/ZkfP1U+zbfssu5eiWQvUmKHHDafuFL5rTWJGq8OYihUrYBZsuzoX95SjmRt8a17AsxL6SQhHTA6A+GT3T7EnE4VnWOI4DRZnx9FqFSshziIkHCgJTzDfhP1rCBf6Q==;24:o413ykFAIKAMCJZAFS5ItAExVVoXTOPMPhruNSiK02AbC951cu8Ba35HbN1ymwyA0HhNSfFNfNMmG4PZ8mAc50Mycxz6Lidfes7imvP2c/o=;7:PF1bHJsKmudGbr5tw0w2KzoRBbokAz6DS/5c56x5ysNLFt+Qydw5+FHAcugEZbBQQe7HCgOmmfZwi+zoxyXizWBSGuCRssXHOnXtnYO/EEeU2+tSB8ilXX6F7iHB6Ly7QhUrYKZLgmMJFbPumYMwZvtTbTRSMW3TGciK2eAzjkiOGFZHJtTwNGPKGmfXbfpB;20:jDrE3HjbcQNHtt9YypP0dIhoBEXLXgseimVzFW4aFxizCpzBudz2EWPRXbPsdnummexTdy9egYm5ItTx6/lvGITlMHup4/JZmwHpaioqgtL3mLD5w8OfuQ/N6udrk3VMWBeZyt32P4yPFEDrmCw7+jS22NYwmB8LE9aXwnMxiEU= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR0101MB0947; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(9101521072)(2401047)(8121501046)(5005006)(3002001)(10201501046);SRVR:BN3PR0101MB0947;BCL:0;PCL:0;RULEID:;SRVR:BN3PR0101MB0947; x-forefront-prvs: 0928072091 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(377454003)(52044002)(3280700002)(9686002)(92566002)(189998001)(5640700001)(11100500001)(76176999)(86362001)(19627405001)(106116001)(2351001)(122556002)(5004730100002)(54356999)(50986999)(16236675004)(2900100001)(2950100001)(5002640100001)(33656002)(2906002)(107886002)(15975445007)(5008740100001)(81166005)(19617315012)(2501003)(19580395003)(88552002)(110136002)(10400500002)(5003600100002)(19625215002)(1096002)(77096005)(450100001)(3660700001)(1220700001)(74316001)(586003)(6116002)(87936001)(19580405001)(102836003)(81973001)(3826002);DIR:OUT;SFP:1102;SCL:1;SRVR:BN3PR0101MB0947;H:BN3PR0101MB0945.prod.exchangelabs.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_BN3PR0101MB0945E267D682E484E8D45270D9670BN3PR0101MB0945_" MIME-Version: 1.0 X-OriginatorOrg: buckeyemail.osu.edu X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Apr 2016 20:42:22.7562 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: eb095636-1052-4895-952b-1ff9df1d1121 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0101MB0947 X-Seq: zsh-workers 38380 --_000_BN3PR0101MB0945E267D682E484E8D45270D9670BN3PR0101MB0945_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable As a quick addendum to the bug report, the link to the issue on Github is h= ere: https://github.com/robbyrussell/oh-my-zsh/issues/5046. After sending m= y original email I investigated a bit more and noted that this behaviour ma= y be a feature and not a bug. Brandon Moore President OpenSource Club 2016-2017 ________________________________ From: Moore, Brandon A. Sent: Saturday, April 30, 2016 4:35:17 PM To: zsh-workers@zsh.org Subject: Bug report: `> filename` doesn't exit I am uncertain if the mailling list is the correct spot for a bug report. F= eel free to notify me if it is not, but note that I am not on the mailing l= ist. Bug description: A user noted on 'oh-my-zsh's Github that the shorthand `> filename` will cr= eate a file by the given filename (or empty said file if it already exists)= as it does in most shells, but it does not exit. This leads to the user ne= eding to terminate said command with c-C or c-D. This is atypical compared= to other shells that will execute this command and go to the next line. Reproducing the bug: run `$ > file` p.s. please note that I personally do not use or suggest using this as a sh= ortcut for the touch command, and am simply passing on this bug on behalf o= f the user who reported it. Sincerely, Brandon Moore President OpenSource Club 2016-2017 --_000_BN3PR0101MB0945E267D682E484E8D45270D9670BN3PR0101MB0945_--