From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: dana <dana@dana.is>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>,
Zsh workers <zsh-workers@zsh.org>
Subject: Re: zsh 4.6.2-test-2
Date: Mon, 31 Dec 2018 16:19:18 +0100 [thread overview]
Message-ID: <CAKc7PVBRy0pOZa2ppcOci1Y4yRu5q=vatt3vFF=3SgqqCbrCGg@mail.gmail.com> (raw)
In-Reply-To: <F05D7E53-3D15-4D9A-AE80-E4C323C08F7E@dana.is>
On Mon, 31 Dec 2018 at 14:41, dana <dana@dana.is> wrote:
>
> (I guess this should go to workers)
>
> This fixes it for me, but i'm not sure if it's the right thing...?
>
> dana
I confirm that there's such problem. I was using standard
module-utilizing test support of the Test sub-directory, and I've
missed that the zpty's Zsh needs to know about custom module_path. The
fix is good IMO.
>
> diff --git a/Test/X04zlehighlight.ztst b/Test/X04zlehighlight.ztst
> index 23ad14bd6..9f00b4697 100644
> --- a/Test/X04zlehighlight.ztst
> +++ b/Test/X04zlehighlight.ztst
> @@ -12,6 +12,7 @@
> export PS1= PS2=
> zpty -d
> zpty zsh "${(q)ZTST_testdir}/../Src/zsh -fiV +Z"
> + zpty -w zsh "module_path=( ${(@q-)module_path} \$module_path )"
> zpty -w zsh 'zle_highlight=( fg_start_code:"CDE|3" fg_end_code:"|" bg_start_code:"BCDE|4" bg_end_code:"|" )'
> }
> zpty_input() {
>
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
prev parent reply other threads:[~2018-12-31 15:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7b0451f90bdfe61f48cc1361690180e07158900.camel@ntlworld.com>
[not found] ` <b8851c3a50bd8bceba1961f2f764e1a6869481ac.camel@ntlworld.com>
2018-12-20 22:25 ` The big kre zsh bug report Martijn Dekker
2018-12-21 7:53 ` Bart Schaefer
2018-12-21 8:11 ` Fix for ${\var} oddity Bart Schaefer
2018-12-25 17:18 ` [PATCH] honour NO_UNSET when reading values in arithmetic expansion/commands Martijn Dekker
2018-12-25 20:44 ` 'wait' exit status and warnings [was: The big kre zsh bug report] Martijn Dekker
2018-12-30 18:13 ` Peter Stephenson
2019-01-21 22:53 ` Martijn Dekker
2018-12-31 2:08 ` Line continuation between $ and { " Martijn Dekker
2018-12-21 11:30 ` The big kre zsh bug report Robert Elz
2018-12-21 20:37 ` Bart Schaefer
2018-12-22 0:13 ` Robert Elz
2018-12-21 2:28 ` Robert Elz
2018-12-24 5:40 ` zsh 5.6.2-test-2 Axel Beckert
2018-12-24 7:14 ` Axel Beckert
2018-12-24 7:38 ` dana
2018-12-24 9:16 ` [PATCH] ztrftime(): Fix truncation for % dana
2018-12-24 12:45 ` Daniel Shahaf
2018-12-24 16:24 ` dana
2018-12-24 17:06 ` Daniel Shahaf
2018-12-24 17:31 ` dana
2018-12-28 22:16 ` dana
2018-12-29 9:55 ` Daniel Shahaf
2018-12-29 10:27 ` Daniel Shahaf
2018-12-29 11:02 ` dana
2018-12-29 11:08 ` Daniel Shahaf
2018-12-29 11:30 ` dana
2018-12-29 11:34 ` Daniel Shahaf
2018-12-24 23:35 ` Joey Pabalinas
2018-12-24 23:30 ` Joey Pabalinas
[not found] ` <CAKc7PVDUjo8HAdwqgRAKcgQHOzThM+hYnjX+2FKzUZB+pfmC-Q@mail.gmail.com>
[not found] ` <CAKc7PVB-agFUarJ=LqC2QNDFta1O5D_o4v-gt7LiobVDohNGVQ@mail.gmail.com>
[not found] ` <06228a6975b91f7066d0046bf912dd69fa5993a2.camel@ntlworld.com>
2018-12-31 13:44 ` zsh 4.6.2-test-2 dana
2018-12-31 15:19 ` Sebastian Gniazdowski [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='CAKc7PVBRy0pOZa2ppcOci1Y4yRu5q=vatt3vFF=3SgqqCbrCGg@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=dana@dana.is \
--cc=p.w.stephenson@ntlworld.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).