From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2820 invoked by alias); 7 Mar 2017 11:31:33 -0000 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-Seq: 40786 Received: (qmail 1407 invoked from network); 7 Mar 2017 11:31:33 -0000 X-Qmail-Scanner-Diagnostics: from out1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.25):SA:0(-0.7/5.0):. Processed in 1.573996 secs); 07 Mar 2017 11:31:33 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=Lun+OecH9KVzXsp eAilSmxw0/G8=; b=KNI9d4t8uVxK3gzNjf4s3Sfk37/7IAFmEfzUlpxkTRkC93M bwsmhDAjeErQINBo2jX3VPvIT5aNgEdS11craOcy3e09GFVzWkk2GJJ9Y1inHncP lu27SurfMvI4/wF6SvJjRwO+9hX18i2r5L3JzObzngn5X8YfOrib2zJ96QLg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=Lun+OecH9KVzXs peAilSmxw0/G8=; b=B81olp633SgKQFItwnOPcK1o0w9XYM/vy11KipUSfxgiJv mef1ZzkTof4UIiFHdNFlqpQ+BOJ8xphO8WdHlFcFLhuyf1DmiNmJNteuQ1WSzwSa aodBq1rXlJU3Hj22CeKbESz7XuQ1jkS+s5j2qtS/rHIcSNGfL+nffX8S/1Rdk= X-ME-Sender: X-Sasl-enc: q+C6UY61B9J0f+RPp3YDIb8RfwJ4s3hFcxC5s+yzn+Z+ 1488885850 Date: Tue, 7 Mar 2017 11:19:16 +0000 From: Daniel Shahaf To: zsh-workers@zsh.org Cc: Ferdinand Thiessen Subject: Re: [BUG] umount mountpoint completion Message-ID: <20170307111916.GA5002@fujitsu.shahaf.local2> References: <8b983c55-f23e-2829-0131-c9970ec9b46b@gmx.de> <170305200130.ZM31787@torch.brasslantern.com> <39bf9cbd-8082-3fd6-54f9-8d1a3f498095@gmx.de> <170306151030.ZM18800@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <170306151030.ZM18800@torch.brasslantern.com> User-Agent: Mutt/1.5.23 (2014-03-12) Bart Schaefer wrote on Mon, Mar 06, 2017 at 15:10:30 -0800: > The fancy substitution that cleaned up this mess was then replaced by a > simpler one that works NEARLY all the time; except it breaks when the > aforementioned \040 for space is followed by ANOTHER digit. In that > case the simplfied substitution treats (in Ferdinand's example) \0400 > as a single octal number and turns it into $'\C-@' instead of " 0". Good find. > However, one question remains. Ferdinand, in your original message on > this thread you said: > > } > % sudo umount "/tmp/a\ 0" > } > } Which is of course invalid. > > Could you please explain why you consider this to be invalid? Because if > all we do is revert 33963, the above is what you're going to get again, > and I don't immediately see what's wrong with it. umount's argv would include the backslash literally, and there is no mount point called '/tmp/a\ 0', only '/tmp/a 0'.