From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Anthony Iano-Fletcher <Anthony.Iano-Fletcher@cbel.dcrt.nih.gov>,
Zsh-workers@math.gatech.edu
Subject: Re: complete-or-expand-prefix
Date: Fri, 30 May 1997 10:05:07 -0700 [thread overview]
Message-ID: <970530100507.ZM4924@candle.brasslantern.com> (raw)
In-Reply-To: <199705301300.JAA13081@argo.dcrt.nih.gov>
On May 30, 9:00am, Anthony Iano-Fletcher wrote:
} Subject: complete-or-expand-prefix
}
} One of the zle functions 'complete-or-expand-prefix' no longer
} works.
I've never heard of that one ... are you sure "expand-or-complete-prefix"
isn't what you're thinking of?
} I added this a while back and used it. After a couple
} of job changes I lost it from my zshrc file. So the short story
} is that I dont know when it broke but it is (at least for me -
} Solaris 2.4 on a Sparc).
Can you describe how the behavior changed from before it broke to now?
Is it broken in the same ways in 3.0.3-test5 and the latest 3.1?
The behavior of expand-or-complete-prefix may have been changed when
COMPLETE_IN_WORD was added, or thereabouts ... but I don't recall whether
any such change was intentional.
} There are 2 options:
} 1. I can fix 'complete-or-expand-prefix' (I have a patch) or
} 2. delete 'complete-or-expand-prefix' completely.
}
} I'm happy with either - do we want backward compatibilty?
The problem may be that we now have two different definitions of backward
compatibility -- all the way back to the original you added, or back to
the intermediate versions since COMPLETE_IN_WORD. I'd like to hear more
details before trying to figure out which is what.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
prev parent reply other threads:[~1997-05-30 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-30 13:00 complete-or-expand-prefix Anthony Iano-Fletcher
1997-05-30 17:05 ` Bart Schaefer [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=970530100507.ZM4924@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Anthony.Iano-Fletcher@cbel.dcrt.nih.gov \
--cc=Zsh-workers@math.gatech.edu \
/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).