zsh-users
 help / color / mirror / code / Atom feed
From: Steve Dondley <s@dondley.com>
To: zsh-users@zsh.org
Subject: Re: How do I get rid of _complete_alias error generated by bash code?
Date: Wed, 15 Sep 2021 18:29:02 -0400	[thread overview]
Message-ID: <597ba0e55f9904347eec15ab823f6dd9@dondley.com> (raw)
In-Reply-To: <E098748A-D34A-4CCF-8BBE-4705CC0385D9@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

On 2021-09-15 05:50 PM, Bev In TX wrote:

>> On Sep 15, 2021, at 4:33 PM, Bart Schaefer <schaefer@brasslantern.com> 
>> wrote:
> 
> On Wed, Sep 15, 2021 at 1:48 PM Steve Dondley <s@dondley.com> wrote: 
> I'm migrating my stuff from bash to zsh. I'm a stymied by an error that 
> crops up from time to time and I'm not sure how to fix. In bash, I had 
> these lines: # completion commands complete -F _complete_alias t
> (and so on)
> 
> That means that at some other point in your bash startup, a function
> named _complete_alias was defined, and you told bash to run that
> function to complete the "t" (etc.) commands.
> 
> Removing these lines is probably the right thing, but otherwise you
> need to port the _complete_alias definition into your zsh startup as
> well.  You must already be loading bashcompinit if there is no
> complaint about the "complete" command not being found.
  Perhaps the OP is using:
https://github.com/cykerway/complete-alias

This looks very vaguely familiar. I think you are right and I did use 
this. Thanks for googling that for me. :)

I've had a little too much wine with dinner to go back and figure out 
what I did 2 hours ago, never mind 2 years ago. I will review this 
tomorrow. Thanks!

[-- Attachment #2: Type: text/html, Size: 2892 bytes --]

      reply	other threads:[~2021-09-15 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 20:48 Steve Dondley
2021-09-15 20:54 ` Steve Dondley
2021-09-15 20:55 ` Roman Perepelitsa
2021-09-15 22:37   ` Steve Dondley
2021-09-15 21:20 ` Bart Schaefer
2021-09-15 21:50   ` Bev In TX
2021-09-15 22:29     ` Steve Dondley [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=597ba0e55f9904347eec15ab823f6dd9@dondley.com \
    --to=s@dondley.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).