Zsh Mailing List Archive
Messages sorted by:
Re: A serious bug in execution – where to debug?
- X-seq: zsh-workers 44606
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Roman Perepelitsa <roman.perepelitsa@xxxxxxxxx>
- Subject: Re: A serious bug in execution – where to debug?
- Date: Tue, 30 Jul 2019 21:59:12 +0200
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- 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==
- In-reply-to: <CAN=4vMqTmZVoNRV4Bqvhdzn33KzfEwB8ABH4_-O9UuOCRkuoLg@mail.gmail.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- List-unsubscribe: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVCKrg_PnZ6jKLoAwR8XQnswT-Bs2TJA7oefhd_gRtHKUQ@mail.gmail.com> <CAN=4vMpWFR=_TPZ2hcQC_FvKSiPFW2_isn_BYxYaoUKLqu-4Gw@mail.gmail.com> <CAKc7PVCn0PNzu5PxCW=nwZ6unt5CtTarPOo387yvg0+bekuSyQ@mail.gmail.com> <CAN=4vMqtA5k_rDfyn_Pk0Q6isxcJVN1mE+8-k+O=21qYDS+HCg@mail.gmail.com> <CAKc7PVB0piw70MfggmkWpGdkOxZNJrb2tZ+2LAao9N9QZ00bPA@mail.gmail.com> <CAN=4vMqYCXz79kVoUN6dN7psOdcGmF-i2XGtccXZgd+Ti1fkEg@mail.gmail.com> <CAKc7PVBeVzKHeeq_kFfbMhx7iF-nBnk2O4dSJVtXCoZW=517pQ@mail.gmail.com> <CAN=4vMqhVGbZDUd59aHkqh90U2+fTriEz741t1dTQQ_vSqbFsw@mail.gmail.com> <CAKc7PVCVJH6+2MZv70wHYtoDQHavvP1XF+uKVO3+S1GBdiojBw@mail.gmail.com> <CAN=4vMqTmZVoNRV4Bqvhdzn33KzfEwB8ABH4_-O9UuOCRkuoLg@mail.gmail.com>
On Tue, 30 Jul 2019 at 21:42, Roman Perepelitsa
> On Tue, Jul 30, 2019 at 9:34 PM Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx> wrote:
>> On Tue, 30 Jul 2019 at 21:24, Roman Perepelitsa
>> <roman.perepelitsa@xxxxxxxxx> 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 provided by anyone other than the code's author. it's not possible to safely unload 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=1..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 are welcome to call them. They guarantee that repeated load+unload won't leak resources. That is, as long as you don't unset any of their internal variables. They do leave a handful of global parameters after unloading; without 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.
Messages sorted by: