zsh-workers
 help / color / mirror / code / Atom feed
From: Arseny Maslennikov <ar@cs.msu.ru>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH 2/2] promptinit: Fix prompt cleanups
Date: Mon, 25 Jan 2021 15:50:12 +0300	[thread overview]
Message-ID: <YA6+hOffLLkMPXfw@cello> (raw)
In-Reply-To: <CAN=4vMpsBu++iDpHnp-p22zY8g-UN4LdRe+3BK-5VGrDLvgHAQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 639 bytes --]

On Mon, Jan 25, 2021 at 09:23:32AM +0100, Roman Perepelitsa wrote:
> On Mon, Jan 25, 2021 at 9:17 AM Arseny Maslennikov <ar@cs.msu.ru> wrote:
> >
> > This problem was previously brought up in zsh-users/23314, to no avail.
> 
> Also related: zsh-workers/46202.

Thank you for bringing this up!

However, during working on the patch I found out this is not the only
problem with prompt theme cleanups. prompt_$theme_setup works both as an
autoloaded function to pull the theme components in and as the setup
function, so `prompt -h $theme' and `prompt -p $theme' both _activate_ the
$theme and fail to run the cleanup actions.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-01-25 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  8:16 [PATCH 1/2] promptinit: typo: RPOMPT -> RPROMPT Arseny Maslennikov
2021-01-25  8:16 ` [PATCH 2/2] promptinit: Fix prompt cleanups Arseny Maslennikov
2021-01-25  8:23   ` Roman Perepelitsa
2021-01-25 12:50     ` Arseny Maslennikov [this message]
2021-02-18 13:03   ` (ping) " Arseny Maslennikov
2021-02-20  0:50     ` dana
2021-02-20 19:01       ` Bart Schaefer
2021-02-22 18:29   ` Bart Schaefer
2021-02-22 22:24     ` Arseny Maslennikov
2021-02-22 22:28     ` [PATCH v2] " Arseny Maslennikov
2021-02-22 23:50       ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YA6+hOffLLkMPXfw@cello \
    --to=ar@cs.msu.ru \
    --cc=roman.perepelitsa@gmail.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).