From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-users-return-23736-ml=inbox.vuxu.org@zsh.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,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 98ce31d3 for ; Tue, 30 Oct 2018 15:20:15 +0000 (UTC) Received: (qmail 21488 invoked by alias); 30 Oct 2018 15:19:57 -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: 23736 Received: (qmail 19404 invoked by uid 1010); 30 Oct 2018 15:19:57 -0000 X-Qmail-Scanner-Diagnostics: from mail-it1-f170.google.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(209.85.166.170):SA:0(-2.0/5.0):. Processed in 1.658298 secs); 30 Oct 2018 15:19:57 -0000 X-Envelope-From: julien.nicoulaud@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LZa32n8T1cVg2ySXSw//z1g3LhWGpTEBLw6yTzyE6Xg=; b=AQKdRxk8usUbDf6ZuBsPhcnjwvBxWF09aaNpgVDGNR5Bh/X3bS7C+EEymAI9OpToR5 hkJbsmGr2oT+k6oGgKoyeuA1LEdh8JmXdintjBaY+IGFpQd9+RbwF2H96YwCQvh9i1wj HeVwxJXtxJuFxEE5NrhmxWxCX+LXnbDV4SKZQ06AnwvxCff5Zdvr4N37+I7TbB187WD2 v8LsHU1vdvUxVZYHFW/SwVnTriE8QmSgX1/f1IGvlKN6Sp5WJL/fJ7rRnXCfKrmWppjT hnBHwf4ca2z7X3pWV8liFbaZcBAdJZKmLnKkhqjKECQwDWlgrn0tqXkpYyIAij6e3IOT LNpQ== 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=LZa32n8T1cVg2ySXSw//z1g3LhWGpTEBLw6yTzyE6Xg=; b=BfxrIe7Dca+LJ8+C5nl21CjpkQEOFb6sNy0SlWKzw/emdT7bPFJzpEF1COjhB5Ah5Z pn//sLpKXUE7jEDisuYq+gO6sipnOYhmkCM/4Oz4GYAF4vHREb36bAL4BrXrnWNqHoj4 AdRr0Nt5/UGhxo/pYfPyeR3OEY4S1k4ZDNivarfYyYGb5k31Gq+RCK5/eYhl9KGQSaPX CpUcH/HKubV1T+yxvFSD8Qz/1k02g7rgh6SIKIbtQLeMHISofm4c3eIImaad7sAkNmMq 6Fg/esy4j2QekFNy5LIYO41p4coM05bFI7vxcIBFnxrhm9yDIzxnPjV9CAvHSwGB6EQL //Dw== X-Gm-Message-State: AGRZ1gIH4+qNFHZFMPIELZT/EnzeRFCfNmYvG/93l/2LOsW/bEJHXbMw PFUiQn05wmbeljB8XWY64lcn+qtxz9/9DBalFfq/bzGt X-Google-Smtp-Source: AJdET5eP7RgVbMtgDFOQVAG+vHS+QdvFQh2mSEthx9TQ5UH1Z0JRVOgbildW+h5kbxSYmiJ4xTlJerghudRF1uv+1mo= X-Received: by 2002:a24:ce03:: with SMTP id v3-v6mr1576840itg.19.1540912793441; Tue, 30 Oct 2018 08:19:53 -0700 (PDT) MIME-Version: 1.0 References: <20181026145522eucas1p245580c8ddf13dca70b5eae45af9a0205~hMFzZ7wLw1740617406eucas1p2G@eucas1p2.samsung.com> <20181028042041.GA21249@osmium.pennocktech.home.arpa> In-Reply-To: <20181028042041.GA21249@osmium.pennocktech.home.arpa> From: Julien Nicoulaud Date: Tue, 30 Oct 2018 16:19:16 +0100 Message-ID: Subject: Re: Completion issue when zsh is not the default shell To: zsh-workers+phil.pennock@spodhuis.org Cc: Mailing-list zsh-users Content-Type: multipart/alternative; boundary="000000000000aeef98057973b7cb" --000000000000aeef98057973b7cb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, I completely missed that, I should have RTFM better (as always) :) For what it's worth, I ended up with: autoload -U zrecompile && zrecompile -p $MAIN_USER_HOME/.zshenv -- \ $MAIN_USER_HOME/.zshrc -- \ $MAIN_USER_HOME/.profile -- \ $MAIN_USER_HOME/.zcompdump \ 1>/dev/null Which will only print messages if these files are missing or byte compilation fails. Le dim. 28 oct. 2018 =C3=A0 05:20, Phil Pennock < zsh-workers+phil.pennock@spodhuis.org> a =C3=A9crit : > On 2018-10-26 at 20:49 +0200, Julien Nicoulaud wrote: > > suspect this is related to bytecode compilation, I have this snippet at > the > > end of my zshrc: > > autoload -U zrecompile && zrecompile -p > $MAIN_USER_HOME/.{zcompdump,zshrc} > > &>/dev/null > > My understanding is that << zrecompile -p FOO >> passes FOO through as > arguments to zcompile, so you're invoking: > > zcompile $MAIN_USER_HOME/.zcompdump $MAIN_USER_HOME/.zshrc > > which is the "zcompile file [ name ... ]" form, so you're compiling > .zshrc into the file .zcompdump (instead of .zshrc.zwc). > > I think that just removing the "-p" should work. (But I've not tried to > reproduce your breakage). > > > What happens if fpath is broken and zrecompile can't be autoloaded? > What if you fixed such a breakage in .zshrc, but you're not recompiling > and the old fpath is still being used from the binary file, even while > the source files are correct? > > This should be "zsh -e" safe, while still giving you more clues what's > failing if things fail: > > if ! autoload -U zrecompile ; then > print -u2 ".zshrc: warning: failed to autoload zrecompile, is fpath > okay?' > else > zrecompile $MAIN_USER_HOME/.{zcompdump,zshrc} || ev=3D$? > if (( ev )); then > print -u2 ".zshrc: warning: zrecompile failed, exiting $ev" > fi > fi > > --000000000000aeef98057973b7cb--