From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29473 invoked by alias); 25 Apr 2015 01:01:19 -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: 34959 Received: (qmail 9956 invoked from network); 25 Apr 2015 01:01:17 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=R9dlhM76G7HDPQOmg0tfjHh6lSdcOm7VY7x4skLkv3o=; b=WRwueeb9Vg5pNFpbIdfxfBTKgOyWX2j3f30RD/fwsfB4Zx64wH/s3W+3gV/L4lSG8S XSwqiGDjwkAo1ty9LZ0h/j61JNa5YASErmaN8Ifdlu0Na7vtqfBJXVN5CXYcu5nZNlF/ BruI/JxQ0w0afyGmYXFLc0XxT96s1BMm7u28dwHvojdUS1pz2k3gt4ZQumTXZNmI8saR WSqZAFuDrBQ11JwAPHmIMSKvNxd7e5JSo+SMv+eaLBdKULbnijx88ZcI4JjLhuacCHnM Wh5Bp/cX106+0/1OMF4gD4iF/p0EFnCq6G7PiJWCU3y688LFnGJmS25FAyNEvVVG1ejc nZqw== X-Gm-Message-State: ALoCoQmiULrs79BYJUegEnI7JH/GrJ9U6sUVA9ulgHLtahVtdd3IOIpdpVOxO/RFmqVDED1ouv2M X-Received: by 10.202.104.88 with SMTP id d85mr878762oic.37.1429923672767; Fri, 24 Apr 2015 18:01:12 -0700 (PDT) From: Bart Schaefer Message-Id: <150424180109.ZM29158@torch.brasslantern.com> Date: Fri, 24 Apr 2015 18:01:09 -0700 In-Reply-To: <20150425001719.GA12262@xvii.vinc17.org> Comments: In reply to Vincent Lefevre "Filename generation: sorting by inode number" (Apr 25, 2:17am) References: <20150425001719.GA12262@xvii.vinc17.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Filename generation: sorting by inode number MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 25, 2:17am, Vincent Lefevre wrote: } Subject: Filename generation: sorting by inode number } } With the "o" glob qualifier for filename generation, it is not possible } to sort by inode number. Such a feature could be very useful to speed up } file reading on an ext3 file system when the files are not in the cache. Hrm. Does the inode ordering also affect stat() times? This sounds less like something to expose as a sort ordering for the o/O qualifiers and more like something to hide under the covers, e.g., so that "oN" (unsorted) actually produces order by inode, instead of the apparently pseudo-random order of readdir(). How close does "oc" get you to this?