From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4759 invoked by alias); 14 Dec 2014 16:52:52 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19529 Received: (qmail 5881 invoked from network); 14 Dec 2014 16:52:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=D9vw8UVm c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=riTnFKaYKgqXicgwsksA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141214085310.ZM23615@torch.brasslantern.com> Date: Sun, 14 Dec 2014 08:53:10 -0800 In-reply-to: Comments: In reply to Mikael Magnusson "Re: umount completion context and tags" (Dec 14, 4:15pm) References: <20141214131541.GB1489@rikku> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh Users Subject: Re: umount completion context and tags MIME-version: 1.0 Content-type: text/plain; charset=us-ascii [Sticking with zsh-users for now but this maybe should move to -workers] On Dec 14, 4:15pm, Mikael Magnusson wrote: } Subject: Re: umount completion context and tags } } > umount u } > umount udev (!!!) } } That's weird in at least two ways. I get the style to work only if i } make it ":completion:*". See previous message about :(u|)mount: ...? } Secondly, those are filesystem types, not labels, and are only valid } after -t afaik(?), and umount -t produces a broken completion. Hmm. On the latter point, "umount -t" works for me: torch% umount -t adfs eventpollfs iso9660 qnx4 selinuxfs usbdevfs autofs ext2 minix ramfs sockfs usbfs bdev ext3 mqueue reiserfs swap vboxsf bfs futexfs nodev relayfs sysfs vfat binfmt_misc hfs ntfs romfs tmpfs vxfs cramfs hpfs pipefs rootfs udf xfs devpts hugetlbfs proc rpc_pipefs ufs xiafs (same zsh session as my previous reply, with the '! device-labels' in the tag-order). In what more specific way is it broken for you? Which branch of the 'case "$OSTYPE"' is taken in _mount on your host? On the former point, I get: torch% umount u torch% umount usbfs Looking at _complete_debug output, usbfs is being completed as a device label because there are no matches to "u" for either device-paths or directories. The tag-order '!' style only applies when the other tags do have possible matches. Now, as to WHY it's being completed as a label, it's because /etc/mtab has the line usbfs /proc/bus/usb usbfs rw 0 0 so _mount assigns dev_tmp=( /dev/hda2 usbfs /dev/hda1 sunrpc ) which subsquently interprets everything that doesn't start with a slash as a device label. -- Barton E. Schaefer