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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 78cb18ad for ; Tue, 30 Jul 2019 21:01:00 +0000 (UTC) Received: (qmail 20776 invoked by alias); 30 Jul 2019 20:00:00 -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: List-Unsubscribe: X-Seq: 44606 Received: (qmail 8266 invoked by uid 1010); 30 Jul 2019 20:00:00 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk1-f179.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25524. spamassassin: 3.4.2. Clear:RC:0(209.85.221.179):SA:0(-2.0/5.0):. Processed in 3.009498 secs); 30 Jul 2019 20:00:00 -0000 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.221.179 as permitted sender) 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:content-transfer-encoding; bh=wMeu9Kwu6c9puU3ey5a0a7N7Ou6Ccv9LSusRDUafO3c=; b=UPmVYrxZ3TSi/hNpoArf/TG7TFb10KnSh/hZr0I09B8yKO/CXNHK0fQMP1Kx7ERK+A 8/T6MrRqrRZMgAOSCNhK4mn5WJ4D4YBjM8RT5uGnVQBPnWqStjq5KdbOgy3mT3CVjwgi n3EPx4AtcQck++O8Sdwd/tq9+CM/JXWHeXdxlak08GIE8oUVuP5sQAsdnKWp+UY9fyhM 4s3A4NCbNM3JA/5v/Ds8OgrYqxP+Z/8M5orkgzozUQttD6r9cmFDfInfGdj1kFEZWRkl x39C5d5lM8aMB3lETCK3APzz60V2iusk8c+n77uswx+IPi3//0orSavEgIS/IQV7+d0P o4TA== 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:content-transfer-encoding; bh=wMeu9Kwu6c9puU3ey5a0a7N7Ou6Ccv9LSusRDUafO3c=; b=LmFTavKPZSgy7TheVl65MrurS0INqB9tRFMLK5DRiWOlS4uWAs8XcrOJQP+1+EXShI pMM71o5au7Xtz1qDvKmEZ5EikSotKFlXzy6hZUPvcjXKN0HeR77FF55iPDE3c2/Ng5Av Zoqj62oICkN7mP5U7W0BXXh2Rgw9QyRU3MnDueJtLWBdX9c0CBwM2EXx9Ut3hVaA9Ios KO4ISFZXLANWmji24J8uDIXY8a4RmaXSTBopGtkplaLSf6v29CDyWx6x5hHDFECZMXZC EhAzs4EawnstkzeJnM2sRaaxrYuRZY3J+maEVgT7OQgze8w0Py2SclqL4oNpUAycJiS/ gfmw== X-Gm-Message-State: APjAAAU3XyBszq3XzjLRL/Rp4KYwefiPIFcM75shakRGnq66PIOQuoVk lAj87DED6SWVSoUb/TFdX4/v3wpwz5IQ2svaYrA= X-Google-Smtp-Source: APXvYqxHIzOzKwZouPMF46LCcyA2GNcCvluKA1iQdw1DGpVLnSHhlQX89tb/LVkAdrIjNeLQSFA4uHggPQkMGmcWThY= X-Received: by 2002:a1f:6d85:: with SMTP id i127mr46035274vkc.7.1564516763642; Tue, 30 Jul 2019 12:59:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sebastian Gniazdowski Date: Tue, 30 Jul 2019 21:59:12 +0200 Message-ID: Subject: =?UTF-8?Q?Re=3A_A_serious_bug_in_execution_=E2=80=93_where_to_debug=3F?= To: Roman Perepelitsa Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 30 Jul 2019 at 21:42, Roman Perepelitsa wrote: > > On Tue, Jul 30, 2019 at 9:34 PM Sebastian Gniazdowski wrote: >> >> On Tue, 30 Jul 2019 at 21:24, Roman Perepelitsa >> wrote: > I think we are in agreement. If there is a public function to unload, you= can call it. If there isn't, it's a missing feature that cannot be provide= d by anyone other than the code's author. it's not possible to safely unloa= d code as a blackbox without knowing all of its implementation details. Yes, but that's in general. I have very positive experiences with unloading of prompts. Currently in my setup by setting parameter MYPROMPT=3D1..8 I can choose the prompt that's active, as described in: http://zdharma.org/zplugin/site/Multiple-prompts/. In general it is like you've said, e.g. syntax-highlighting plugin's won't unload correctly, but only due to a final glitch and as I tested now, it *did* unload correctly (due to changes in my setup, most probably). But in general yes, plugins often do not unload fully clean, so I think that we are in agreement. > Both gitstatusd and p10k do provide public functions for unloading. You a= re welcome to call them. They guarantee that repeated load+unload won't lea= k resources. That is, as long as you don't unset any of their internal vari= ables. They do leave a handful of global parameters after unloading; withou= t them they cannot be loaded correctly again. Could the function powerlevel10k_unload_plugin() be provided? I could deduce it from the plugin's name and call it in a general manner. --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org