From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Writing code that works with emulate zsh and emulate csh
Date: Mon, 8 Feb 2016 11:09:36 -0800 [thread overview]
Message-ID: <160208110936.ZM12172@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVDmAuREbeZY6kQO0yjJhD+ugqiOQFSJqXLbSHdYGHxNeg@mail.gmail.com>
On Feb 8, 6:45pm, Sebastian Gniazdowski wrote:
}
} It turns out that only a single option, CSH_JUNKIE_QUOTES, makes the
} error message that I receive:
}
} ./zplugin.zsh:34: unmatched "
}
} What in this file can trigger the message?
}
} https://github.com/psprint/zplugin/blob/master/zplugin.zsh
cshjunkiequotes means you can't have a newline embedded in a quoted
string, so both the eval in --zplugin-shadow-autoload and the long
help text in zplugin will break.
} I then looked at the Wikipedia page and thought that emulate csh
} enables completely different language syntax. Now it might revealed
} that it just sets CSH_JUNKIE_QUOTES.
Well, it does more than that; it turns off glob qualifiers, changes the
way background jobs are monitored, disables =command expansion, enables
globbing in assignments and substitutions, and enables alternate loop
body syntax. However, it's probably true that the only significant
parse-time (as opposed to execute-time) breakage of native zsh code is
for quoting.
} Maybe it could be possible to adapt zplugin.zsh to that option?
You could use a here-document for the help text in zplugin, and a single
line with semicolons for the eval body in shadow-autoload.
prev parent reply other threads:[~2016-02-08 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:45 Sebastian Gniazdowski
2016-02-08 10:52 ` Peter Stephenson
2016-02-08 17:45 ` Sebastian Gniazdowski
2016-02-08 19:09 ` 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=160208110936.ZM12172@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).