zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: key bindings, fixes, docs, tests for vi stuff
Date: Thu, 20 Nov 2014 22:23:53 -0800	[thread overview]
Message-ID: <141120222353.ZM10495@torch.brasslantern.com> (raw)
In-Reply-To: <546EA58F.7010101@eastlink.ca>

On Nov 20,  6:38pm, Ray Andrews wrote:
} Subject: Re: PATCH: key bindings, fixes, docs, tests for vi stuff

Please don't hijack threads by hitting "reply" and then starting a
whole new conversation.  If you have a new topic, start a new message.
Thanks.

} On 11/20/2014 06:20 PM, Mikael Magnusson wrote:
} 
} > If you use dev versions of zsh, you will sometimes need to manually 
} > purge your .zwc files as they're not compatible across some code 
} > changes.
} 
} Thanks for the tip.  I trust these files are rebuilt at some point?

There's nothing that automatically rebuilds .zwc files in the regular
zsh distribution or "make" process.  If you have .zwc files in your
$fpath, either you zcompile'd them, or they were zcompile'd for the
zsh package installed with your OS package manager (which seems not
very likely).

} Anyway, I deleted all of them and:

Where were they before you deleted them?

} 6: text.c:865: unknown word code in gettext2()
} 1: text.c:865: unknown word code in gettext2()
} 7: text.c:865: unknown word code in gettext2()
} 8: text.c:865: unknown word code in gettext2()

This is a bit suspicious because gettext2() is only called when turning
a wordcode program back into readable text; for example, when calling
a DEBUG trap or preexec.


  reply	other threads:[~2014-11-21  6:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 21:36 Oliver Kiddle
2014-11-18  8:04 ` Jun T.
2014-11-19  8:48   ` Oliver Kiddle
2014-11-19 15:35     ` Ray Andrews
2014-11-21  0:01   ` Oliver Kiddle
2014-11-21  0:49     ` Bart Schaefer
2014-11-21  1:10       ` Ray Andrews
2014-11-21  5:53         ` Bart Schaefer
2014-11-21 10:35       ` Oliver Kiddle
2014-11-22  6:59         ` Bart Schaefer
2014-12-12 16:47           ` Oliver Kiddle
2014-11-21  1:15     ` Ray Andrews
2014-11-21  2:20       ` Mikael Magnusson
2014-11-21  2:38         ` Ray Andrews
2014-11-21  6:23           ` Bart Schaefer [this message]
2014-11-21 17:28             ` trouble with debugging binary Ray Andrews
2014-11-22  4:45               ` Bart Schaefer
2014-11-22  5:27                 ` Ray Andrews
2014-11-22  5:43                 ` Bart Schaefer
2014-11-22 16:49                   ` Ray Andrews
2014-11-22 22:35                     ` Bart Schaefer
2014-11-23  7:58                     ` Lawrence Velázquez
2014-11-23 16:22                       ` Ray Andrews
2014-11-23 18:12                         ` Mikael Magnusson
2014-11-23 18:42                           ` Ray Andrews
2014-11-23 19:01                             ` Mikael Magnusson
2014-11-23 22:30                               ` Ray Andrews
2014-11-21 15:20     ` PATCH: key bindings, fixes, docs, tests for vi stuff Jun T.

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=141120222353.ZM10495@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).