From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: read-only functions
Date: Tue, 2 Feb 2016 20:59:26 -0800 [thread overview]
Message-ID: <160202205926.ZM2595@torch.brasslantern.com> (raw)
In-Reply-To: <160202173200.ZM2203@torch.brasslantern.com>
[Sorry about the double-inclusion in the previous message; something
strange happened in the handshake between email client and external
text editor.]
On Feb 2, 5:32pm, Bart Schaefer wrote:
}
} Anyway there doesn't seem to be any particular obstacle to applying
} the PM_READONLY flag to shfunc nodes.
After a few minute staring at code and the accompanying further thought,
this seems to be fundamentally not compatible with autoloading. The
number of special cases to handle is doubled, among other things.
prev parent reply other threads:[~2016-02-03 4:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 0:22 Martijn Dekker
2016-02-03 1:32 ` Bart Schaefer
2016-02-03 4:59 ` Bart Schaefer [this message]
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=160202205926.ZM2595@torch.brasslantern.com \
--to=schaefer@brasslantern.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).