On Dec 11, 10:02am, Ray Andrews wrote:
}
} Ah! So the plugin runs predictably, but this doesn't mean that the
} user's setup is ignored otherwise, it would just be ignored while the
} plugin is running insofar as the commands within the plugin go.
Er, no. It would be ignored while the code for the plugin is being
*parsed*, i.e., converted into zsh's internal wordcode format, NOT
while the wordcode is being *run*. If the plugin wants to ignore or
save/restore the user state while it is *running*, that's up to the
plugin itself.
This is for things like IGNORE_BRACES, IGNORE_CLOSE_BRACES, RC_QUOTES,
C_BASES, C_PRECEDENCES, MULTI_FUNC_DEF, POSIX_ALIASES, POSIX_IDENTIFIERS,
and POSIX_STRINGS, and alias expansions themselves, which affect the
interpretation of the program text before it even begins running.
Of course, the implementation example I gave could affect some of the
running of the code if it executed simultaneously with the initial
load of the plugin; there's no way to avoid that with an interpreted
language. But the assumption is that most plugin source files only
set up a bunch of state (function definitions, etc.) that is meant to
execute later.