Re: Unset “zle_bracketed_paste” .zshrc

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Peter Stephenson wrote on Wed, 29 Jan 2020 11:23 +0000:
> On Tue, 2020-01-28 at 11:09 +0000, Peter Stephenson wrote:
> > % zmodload -Fa zsh/datetime p:EPOCHSECONDS
> > % print $EPOCHSECONDS
> > 1580209515
> > % zmodload -Fl zsh/datetime
> > -b:strftime
> > +p:EPOCHSECONDS
> > -p:EPOCHREALTIME
> > -p:epochtime
> > 
> > This is another way of fixing the underlying problem --- e.g. here
> > you don't need to "unset EPOCHREALTIME" because it wasn't provided
> > as a feature in the first place.  You can turn on and off the
> > feature as needed once the module is loaded.  
> 
> I see parameters used by ZLE are only fairly weakly linked into this
> mechanism, however.  At least one reason for that is because of the
> unhelpfully tight linkage between ZLE and the main shell, so it's
> not simply a straightforward plugin.  However, I haven't looked
> further so I don't know if that's an issue with zle_bracketed_paste.
> There may be some scope for rationalisation.
> 

zle_bracketed_paste isn't declared special; it's just getaparam()'d in
the guts of a random C function.

> Loading a module for your own purposes --- for which Sebastian
> no doubt provides a good deal of support --- is in any case a
> rather different thing from the shell loading a module to provide
> its own basic features, so this may not be going anywhere particularly
> useful in this case.

Well, it's an option.  It would result in the following interface:
to prevent $zle_bracketed_paste from being defined one will have to run
«unset zle_bracketed_paste» if zsh/zle has been loaded, or «zmodload -Fa
zsh/zle -p:zle_bracketed_paste» otherwise.

On the other hand, the approach I described in 45339 aimed to make it
possible to just do «unset zle_bracketed_paste» to unset that parameter
(and keep it unset), regardless of whether zsh/zle has or hasn't been
loaded.

I find the latter option preferable.  (Assuming it can be implemented
without errors about readonly parameters cropping up at unexpected
times, as discussed upthread)

In the meantime, here's a test for -Fa.

diff --git a/Test/V01zmodload.ztst b/Test/V01zmodload.ztst
index 1bd8c1900..6a4e34d2d 100644
--- a/Test/V01zmodload.ztst
+++ b/Test/V01zmodload.ztst
@@ -348,6 +348,20 @@
 ?(eval):6: unknown function: systell
 ?(eval):9: file descriptor out of range
 
+ $ZTST_testdir/../Src/zsh -fc '
+  zmodload zsh/zutil
+  zmodload -Fal zsh/zutil | grep parse
+  zmodload -u zsh/zutil
+  #
+  zmodload -Fa zsh/zutil -b:zregexparse
+  zmodload zsh/zutil
+  zmodload -Fal zsh/zutil | grep parse >&2
+ '
+0:zmodload -Fa can disable features from being loaded
+>b:zparseopts
+>b:zregexparse
+?b:zparseopts
+
 %clean
 
  eval "$deps"

Sorry for the delays responding to this thread; life has been getting
in the way.

Daniel