From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: off topic
Date: Sun, 11 Dec 2016 11:20:53 -0800 [thread overview]
Message-ID: <161211112053.ZM30289@torch.brasslantern.com> (raw)
In-Reply-To: <584D94CE.5020706@eastlink.ca>
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.
next prev parent reply other threads:[~2016-12-11 19:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161209130109epcas2p1fd786d46827852a8cf1badcb5d003ec9@epcas2p1.samsung.com>
2016-12-09 12:29 ` vi mode reset Christian Brabandt
2016-12-09 14:33 ` Ray Andrews
2016-12-09 14:41 ` Peter Stephenson
2016-12-09 14:44 ` Oliver Kiddle
2016-12-09 15:07 ` off topic Ray Andrews
2016-12-09 16:28 ` Oliver Kiddle
2016-12-09 17:45 ` Ray Andrews
2016-12-10 0:54 ` Bart Schaefer
2016-12-10 2:50 ` Oliver Kiddle
2016-12-10 3:13 ` Bart Schaefer
2016-12-10 3:31 ` Ray Andrews
[not found] ` <95362.1481338226__15466.9970310808$1481338718$gmane$org@hydra.kiddle.eu>
2016-12-11 4:32 ` Daniel Shahaf
2016-12-11 17:07 ` Ray Andrews
2016-12-11 17:19 ` Bart Schaefer
2016-12-11 18:02 ` Ray Andrews
2016-12-11 19:20 ` Bart Schaefer [this message]
2016-12-11 20:23 ` Ray Andrews
[not found] ` <584AEDBF.2050402__19991.0537027337$1481307418$gmane$org@eastlink.ca>
2016-12-09 19:24 ` Daniel Shahaf
2016-12-09 20:25 ` Ray Andrews
[not found] ` <584B1325.1010907__10266.7204490446$1481316980$gmane$org@eastlink.ca>
2016-12-10 0:14 ` Daniel Shahaf
2016-12-10 0:21 ` Ray Andrews
2016-12-12 13:11 ` Vincent Lefevre
2016-12-09 15:48 ` vi mode reset Christian Brabandt
2016-12-09 16:46 ` Oliver Kiddle
2016-12-09 20:24 ` Christian Brabandt
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=161211112053.ZM30289@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).