From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19086 invoked by alias); 27 Oct 2012 20:44:46 -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: 30761 Received: (qmail 14556 invoked from network); 27 Oct 2012 20:44:34 -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.6 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_LOW, T_DKIM_INVALID,T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 74.125.83.43 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=SqifFU9FRZvUqjAjaynYVDB73YuTq5m7BvXZt2I3ioE=; b=NR9r7/BpyjWirF1ODfrg5x46yN6dVSFlccElCoyDxhZE9jWsEnhUgYDICmgawMR+I9 DLVDmkrFkAQD5YXW0jPx9irv0vo0eJ+tz6x+IFRjlriZJlc7Du70orMFoVy9tluMg/K7 kK5EsmPsg4Tu3NVwsDvNcS+sHSc/vgVAEXdOt5N77aaN9cWmaocftWRNd8aTkq1u8jXu wNotO0r3jtI163QwNw7jhVglUQdyWXw0MPara8Xvp0DkdQu7yy7/EOidW2E9dz0TQKpF rVLc43rqFAfQ6OR+7H6oAU76vffdYCvoQARvlI4hENlAGGU2rSuRovJuueLpClJtqDEV DKKw== MIME-Version: 1.0 In-Reply-To: References: From: Denis Kasak Date: Sat, 27 Oct 2012 22:43:48 +0200 Message-ID: Subject: Re: systemd completion (loginctl completion no longer works) To: zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 On 27 October 2012 22:29, Denis Kasak wrote: > Hello, > > loginctl completion no longer works in zsh with new versions of > systemd since "systemd-loginctl" was renamed to just "loginctl". I'll > send a patch to fix this but I was wondering what the preferred > resolution would be: to make it compatible with both binary names (for > compatibility with earlier systemd versions) or to simply change it to > the new name? Nevermind, I just noticed Daniel Wallace's post from a few days ago (which I somehow managed to miss...). He presumably fixed this issue in his patches. -- Denis Kasak