Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Oh my God! They killed completion! YOU BASTARDS!

pacman@xxxxxxx wrote:
>I must object to the changes to completion behavior in zsh 3.1 as opposed to
>the previous versions. First, on the matter of LIST_AMBIGUOUS, I would
>suggest that if you're going to add a new option that dramatically alters
>some existing rules that people have been been using for a long time, at the
>very least you shouldn't turn it on by default!

There was a policy decision made in 3.1.1 that, generally speaking, the
clever interactive options should be enabled by default.  It does change
the default behaviour, but it doesn't affect scripts (where compatibility
really matters), and the new behaviour is usually preferred.

>              If I _wanted_ to use a new option, I'd like the chance to read
>about it first, and then turn it on if it sounds like a good idea.

The Etc/NEWS file does list new options.  These options being on by
default isn't listed, but this is a beta version, and it is listed in
the ChangeLog.

>particular option, I think, is not a good idea, and I don't appreciate having
>it forced upon me by a new default setting. Please, let's have a little
>backward compatibility.

Possibility for zsh-workers: should `emulate' have the capability to
emulate earlier zsh versions?  So `emulate zsh-2.3' would turn off

>17:01 6 londo /home/pacman/src %echo $ZSH_ <--\
>ZSH_NAME     ZSH_VERSION                      |
>                              /---------------/
>My cursor is sitting HERE! --/ WHAT THE HELL IS THAT?

ALWAYS_LAST_PROMPT.  One of my favourite features.  It means that you
don't waste screen space with old completion lists -- new lists visibly
replace the old one -- and the command line doesn't jump around, so
it's easier to keep your eyes on what you're editing.  This has been
available since 2.5.

>This behavior is wrong. It's SO wrong.. The vastness of your wrongness here
>astounds me. All the languages in the world do not have enough words to
>adequately describe the degree of wrongness exhibited by zsh 3.1 completion.

I'm glad to see I'm not the only person that gets this emotional about
computer programs.

But ALWAYS_LAST_PROMPT is right.  It's SO right.  So vastly right that
having to use bash purees my brain when it puts the completion list in
the wrong place.

>This is like compiling a new version of vi, only to find out that it is an
>emacs clone.

Bad analogy.  vi's popularity rests on having a simple and *complete*
interface.  zsh has a history of adding cool and unusual features.
Surely you can't expect us to make no progress in this direction in
two years?

>And this, unlike the first issue, can't even be fixed by toggling an option.

"unsetopt alwayslastprompt".

>The description of ALWAYS_LAST_PROMPT is brief and confusing (how can a
>completion key be given an argument? What does that mean? Is that a numeric

Yes.  In vi mode you'd have to fiddle with the key bindings to do it.
I doubt that anyone actually does this, though: just set the option the
way you want it.

>Secondly, there is stuff on the screen below the prompt. Being down there, it
>looks like it should be part of the command line I'm editing, but it isn't.

You'll get used to it, if you use it.  I can understand how it might be
confusing when unexpected.


Messages sorted by: Reverse Date, Date, Thread, Author