From: Ray Andrews <rayandrews@eastlink.ca>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: trapped in bash
Date: Sat, 17 Dec 2016 14:40:50 -0800 [thread overview]
Message-ID: <5855BEF2.6090208@eastlink.ca> (raw)
In-Reply-To: <161217124354.ZM7815@torch.brasslantern.com>
On 12/17/2016 12:43 PM, Bart Schaefer wrote:
> On Dec 17, 12:27pm, Ray Andrews wrote:
> }
> } Seems I have to rebuild all my own C projects as they have the same
> } 'not found' characteristic.
>
> Or you need to follow Aaron's instructions for installing the 32-bit
> runtime on your 64-bit system. Although that's not *guaranteed* to
> make everything work without rebuilding.
No need to risk doing something that might be flaky, I'm just rebuilding
as needed. So far there hasn't been a hint of a problem beyond needing
to retrieve some 64 bit libraries. So I'm pumped that zsh will rebuild
with similar results.
>
> } and so far everything is where I put it, except that command completion,
> } if there is no match, brings up the last command, whereas my setup
> } should do nothing (leave the prompt blank). Where might that change be
> } effected from?
>
> That doesn't sound familiar at all. Bringing up the last command seems
> to imply that one of the history completers is in the zstyle.
>
> Your best bet may be:
>
> 1. type ctrl-x h and see what completions are active in that context;
>
> 2. if that doesn't give you an obvious hint, use ctrl-x ? for a debug
> trace and look through that.
>
>
Ah ... it's the stock files in /etc/zsh, I renamed the directory and
everything is as I expect. It's one of my perpetual mini-rants to hate
the way most linux programs hide bits of themselves all over the place.
Actually I deleted all those on my main machine for fear of them
doing funny things on Tuesday, but it's time I took a look at them again
and put them work, maybe, now that I have some clue what I'm doing.
Thanks Bart.
next prev parent reply other threads:[~2016-12-17 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 15:33 Ray Andrews
2016-12-16 21:51 ` Aaron Schrab
2016-12-16 22:39 ` Ray Andrews
2016-12-16 23:05 ` Bart Schaefer
2016-12-17 20:27 ` Ray Andrews
2016-12-17 20:43 ` Bart Schaefer
2016-12-17 22:40 ` Ray Andrews [this message]
[not found] ` <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca>
2016-12-18 15:06 ` Daniel Shahaf
2016-12-18 15:54 ` Ray Andrews
2016-12-19 0:32 ` Daniel Shahaf
2016-12-19 2:30 ` Bart Schaefer
2016-12-19 4:29 ` Ray Andrews
2016-12-19 5:48 ` Bart Schaefer
2016-12-19 16:26 ` Ray Andrews
[not found] ` <ab7aeb33-d091-6602-8baa-cce92300d289__26556.3400615521$1482166729$gmane$org@eastlink.ca>
2016-12-19 17:47 ` Daniel Shahaf
2016-12-17 23:16 ` Jim
2016-12-17 23:38 ` Ray Andrews
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=5855BEF2.6090208@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=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).