zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Command substitution parsing issues (not really Re: completion)
Date: Fri, 16 Jan 2015 18:57:32 -0800	[thread overview]
Message-ID: <150116185732.ZM30791@torch.brasslantern.com> (raw)
In-Reply-To: <54B9AA99.6080403@eastlink.ca>

On Jan 16,  4:19pm, Ray Andrews wrote:
}
}      $ ln -svf zsh-5.0.7-175-./Src/zsh: symbol lookup error: 
} /usr/local/lib/zsh/5.0.7-dev-0/zsh/zle.so: undefined symbol: lexsave

You need to re-install the shared object files.  The symbols have in
fact changed, you're loading a .so from a previous build.

In fact if you're going to live on the bleeding edge of git pull, you
should have a separate shared-object directory for every build.


However, the latest change has NOT fixed things for me.  I still get:

schaefer<501> echo ÿÿÿÿÿÿÿÿ$(ls)
Completing all expansions
ÿÿÿÿÿÿÿÿ$(ls)
Completing original
$(ls)

And history recall screws up with aliases:

schaefer<501> echo $(ls)        
Config/ config.modules config.status* Etc/ Src/ config.h config.modules.local
core.28047 foo/ stamp-h config.log config.modules.sh Doc/ Makefile Test/
schaefer<502> echo $(lsls -CF)


Perhaps the alias is why I'm getting the ÿÿÿÿÿÿÿÿ text as well.  Let's
see ...  yes, that's the problem:

schaefer<502> unalias ls
schaefer<503> echo Config/
Completing expansions
Config                Test                  config.modules.sh   
Doc                   config.h              config.status       
Etc                   config.log            core.28047          
foo                   config.modules        Makefile            
Src                   config.modules.local  stamp-h             
Completing all expansions
Config config.h config.log config.modules config.modules.local config.modul ...
Completing original
$(ls)


  reply	other threads:[~2015-01-17  2:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  0:19 completion Ray Andrews
2015-01-17  2:57 ` Bart Schaefer [this message]
2015-01-17  3:29   ` Command substitution parsing issues (not really Re: completion) Ray Andrews
2015-01-17 13:25     ` Vin Shelton
2015-01-19 10:29     ` Peter Stephenson
2015-01-19 10:39       ` Peter Stephenson
2015-01-22  0:34       ` make check problem Ray Andrews
2015-01-22  8:49         ` Peter Stephenson
2015-01-22 16:00           ` Ray Andrews
2015-01-22 16:40         ` Jun T.
2015-01-22 17:38           ` Ray Andrews
2015-01-22 17:56             ` Bart Schaefer
2015-01-22 18:24               ` Ray Andrews
2015-01-23  4:02                 ` Bart Schaefer
2015-01-23  4:48                   ` Ray Andrews
2015-01-22 19:04               ` --enable-pcre and regex comparison (Was: make check problem) Lawrence Velázquez
2015-01-23  4:04                 ` Bart Schaefer
2015-01-18 16:36   ` Command substitution parsing issues (not really Re: completion) Peter Stephenson
2015-01-18 17:31   ` Peter Stephenson
2015-01-18 22:34     ` Peter Stephenson

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=150116185732.ZM30791@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).