* complete-or-expand-prefix
@ 1997-05-30 13:00 Anthony Iano-Fletcher
1997-05-30 17:05 ` complete-or-expand-prefix Bart Schaefer
0 siblings, 1 reply; 2+ messages in thread
From: Anthony Iano-Fletcher @ 1997-05-30 13:00 UTC (permalink / raw)
To: Zsh-workers
Hi All,
One of the zle functions 'complete-or-expand-prefix' no longer
works. 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).
The good news is that the option COMPLETE_IN_WORD causes completion
to do what 'complete-or-expand-prefix' was meant to do, i.e. complete
words up to the cursor rather than to the end of the word.
There are 2 options:
1. I can fix 'complete-or-expand-prefix' (I have a patch) or
2. delete 'complete-or-expand-prefix' completely.
Im happy with either - do we want backward compatibilty?
Anthony.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: complete-or-expand-prefix
1997-05-30 13:00 complete-or-expand-prefix Anthony Iano-Fletcher
@ 1997-05-30 17:05 ` Bart Schaefer
0 siblings, 0 replies; 2+ messages in thread
From: Bart Schaefer @ 1997-05-30 17:05 UTC (permalink / raw)
To: Anthony Iano-Fletcher, Zsh-workers
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1997-05-30 17:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-05-30 13:00 complete-or-expand-prefix Anthony Iano-Fletcher
1997-05-30 17:05 ` complete-or-expand-prefix Bart Schaefer
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).