From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id b0350755 for ; Thu, 24 Jan 2019 19:12:53 +0000 (UTC) Received: (qmail 22302 invoked by alias); 24 Jan 2019 19:12:39 -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: List-Unsubscribe: X-Seq: 23845 Received: (qmail 11571 invoked by uid 1010); 24 Jan 2019 19:12:39 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f175.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25112. spamassassin: 3.4.2. Clear:RC:0(209.85.208.175):SA:0(-1.9/5.0):. Processed in 2.76583 secs); 24 Jan 2019 19:12:39 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qV90EeAQxW9gEzIXjRD/JVCQjt5syDrRJl/cuhc8fFY=; b=dRY4QyeIhDwlUAy3lFSDCa8jG3vu3yaelJh5Fbk3KTUh53unuPDBzbl6wqzJcKOe/D sbF9CAZpbu2RoYA92Cp6dZpof/QlMEw3MxZN/y7Kyv7v4QP85lytXzHNBRL+nPg3Wvl2 4DPo/tEIIluaJn+eBqheBjWtVFsY8+VWJRABDCjHRlMtjj5BciFqAZkE7RGzh5yL5zBl OGCEJ8k3DC1yoM9QQsgAkergcYargTSvZ57FJE24uF+c7bYgFPgXT61JeL9blRZtxDrA BoPyg32bx32FXLcKffmGBeWkx4cPLV+asn3i4+bnTnZQg3/n2PGJvgc1m7hWDP9HKPxf UsSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qV90EeAQxW9gEzIXjRD/JVCQjt5syDrRJl/cuhc8fFY=; b=WD6UWRY0TyvCwzPY5IH2t9Ob3Z7ujNQS1rFaoifJ9cNjXBSLfZWQBsepA9NPyBySO4 gCnX1UX0ayLvRkUm+BvgCY3fQpWD0QzCwdhpLlnV5J3NCfyvsrdZ2chO3chZ/JniFCQQ SWIDLgOlsiEliMA/45RKF5sp9Glwkl8ypWKTYuDCGWQYmXN9WIRIYClUrVMF8KSmK4TC T4CQHiAdSgx10EnHPTF5HH52Y1srflOa1msWJUeRjGmTKw4j6Nx7E639jiX2vEbwiDBF Xig96I8USJ9dZfkjeStoK/Q0W4K6E0wO0ee83ckM0wV9xRuVb3IJqlhEH4yeHp871hCT gwVg== X-Gm-Message-State: AJcUukfLltUboiA5ggYD4euufjpz3wHoourW5jRXN5y3qZEjDJVmEe0m NAfFEFQa2EOoCOeR50LSUbAXvODhJZyL9CtzBkH+pn0rHH0= X-Google-Smtp-Source: ALg8bN4hy6BCgOMfHYQZsvzLTcwQsw1S5ELl7w4cYi/n0bxpc8pfUzUBx3E3EX7mx3iEbT7wuE8k1Ojx04rKQWT5j7I= X-Received: by 2002:a2e:9694:: with SMTP id q20-v6mr6445770lji.173.1548357152524; Thu, 24 Jan 2019 11:12:32 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Thu, 24 Jan 2019 14:12:20 -0500 Message-ID: Subject: Re: Do you recognize this zshrc.d naming scheme? To: Robert Spencer Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Fri, Jan 18, 2019 at 4:14 AM Robert Spencer wrote: > > I've started working on an in-house project (awit-zsh-superawesome) that > uses it, regrettably my boss can't remember where he got it from. > > I'd like to find the upstream source, so I can document the naming scheme. > Unfortunately so far I've had no luck finding references online. I've been traveling/busy so have only peripherally paying attention to this thread ... but so far I've only seen people describing their own similar setups. I strongly suspect that's because there is no "upstream source" for this; this sort of file naming is a common idiom in unix/linux used for forcing an ordering on configuration files that are read from a directory, without having to name the individual files in some sort of control script. So this particular ordering was probably invented by the original author of your in-house project. A typical extension of this would be to add another tag in each file name so that they could be divided into files read for all shells / interactive shells / login shells.