zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: Unset “zle_bracketed_paste” .zshrc
Date: Thu, 23 Jan 2020 09:53:33 +0000	[thread overview]
Message-ID: <1579773213.5343.1.camel@samsung.com> (raw)
In-Reply-To: <20200123031249.034c7e1a@tarpaulin.shahaf.local2>

On Thu, 2020-01-23 at 03:12 +0000, Daniel Shahaf wrote:
> I haven't tried to implement this yet, but what I have in mind is
> (1) Make unsetparam_pm() add the PM_UNSET bit if the PM_AUTOLOAD bit is
> present; (2) Make module loading, before creating a parameter, check if
> there's a Param with PM_UNSET and PM_AUTOLOAD both set; if there is,
> rather than create the "real" parameter, delete the tombstone parameter.
> (But if there isn't a Param at all, the module _should_ create its special
> Param anyway, to allow modules to be unloaded and reloaded in the same
> shell session.)

The obvious expected behaviour would be for it to have the same
behavious as unsetting the parameter after the module is loaded.  But a
quick tests suggests that doesn't work for readonly parameters, for one
--- all that would happen is that would produce an error when the module
is loaded, which doesn't really make much sense.  So in that case, at
least, the behaviour above is as logical as anything.

Documenting the current behaviour is perfectly respectable.  The
autoload flag effective means the parameter behaviour defers to the
module.  Remember, you can use zmodload -F to manipulate which features
are provided by a module, although not at the point of declaring
autoloads --- some sort of autoloadable feature set might be another
way of doing this.

pws


  reply	other threads:[~2020-01-23  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 23:20 Andrew Reyes
2020-01-18 19:40 ` Daniel Shahaf
2020-01-23  3:12   ` Daniel Shahaf
2020-01-23  9:53     ` Peter Stephenson [this message]
2020-01-26  0:45       ` Daniel Shahaf
2020-01-27 14:01         ` Peter Stephenson
2020-01-28 11:09           ` Peter Stephenson
2020-01-29 11:23             ` Peter Stephenson
2020-02-06 12:40               ` Daniel Shahaf
2020-02-06 13:32                 ` Mikael Magnusson
2020-02-06 14:09                   ` Peter Stephenson
2020-03-14  3:28                     ` Daniel Shahaf
2020-01-29  8:34           ` Daniel Shahaf

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=1579773213.5343.1.camel@samsung.com \
    --to=p.stephenson@samsung.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).