From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: Call for opinions on a couple of prospective zsh patches
Date: Sun, 6 Jun 1999 16:20:23 +0000 [thread overview]
Message-ID: <990606162023.ZM10310@candle.brasslantern.com> (raw)
In-Reply-To: <19990606143605.B23915@thelonious.new.ox.ac.uk>
On Jun 6, 2:36pm, Adam Spiers wrote:
} Subject: Re: Call for opinions on a couple of prospective zsh patches
}
} Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
} > Greg Badros <gjb@@cs.washington.edu> has submitted patches for three new
} > features that could appear in zsh 3.0.6. I'm undecided whether to add
} > any or all of them. They are:
} >
} > * Completion using "dynamic abbreviations" after the manner of the emacs
} > dabbrev package. This includes adding a special `dabbrev-complete' ZLE
} > action, along the lines of expand-or-complete, complete-word, etc.
}
} Personally I find this feature so useful that I can't stand being
} without it, and still use that version with my patch hacked in to this
} day, which is unfortunate, because it's prevented me from regularly
} trying out the newer development versions.
}
} Which versions is zle -C (or similar) available in these days?
Peter has been doing interim unofficial patch releases about once a week
for some while now, because Zefram's net access has been intermittent.
The "zle -C" stuff merged with some other completion changes that Sven
Wischnowsky implemented, and all will appear in 3.1.6.
(You know you've been reading zsh-workers a long time when you can spell
Wischnowsky without looking it up.)
} > I find the effects of `dabbrev-complete' to be -very- similar to
} > setopt menu_complete
} > compctl -D -s '${=$(history -nr 1)}'
}
} Also, I don't like the idea of menu-completion behaviour, because I
} tend to keep a huge history (precisely for the reason that it makes a
} dabbrev-expand action so useful), so I'd end up with huge menus (or a
} "do you want a huge menu" prompt) most times I hit the key. Ugh.
I think you're confusing menu-completion with completion listings. In a
menu completion, repeatedly striking the completion key (e.g. TAB) cycles
through the list of possible matches; you still see only one at a time,
and you aren't prompted about it. Listing behavior (setopt auto_list and
list_ambiguous) means that if the word can't be completed, all possible
matches are displayed (or you get prompted if there are too many).
Greg's patches do not cause listing behavior, ever; it's a new builtin,
so it doesn't recognize the regular completion options. Hm, I'd probably
have to try to do something about that if I were going to include it.
} I'd say that if this next 3.1 release is coming soon then maybe don't
} bother.
The 3.1.6 release should not be very far apart from the 3.0.6 release,
barring unforseen circumstances.
Slightly off-topic:
} I'm constantly finding that M-f and M-b don't do what I want them to,
} and I can't get them to behave how I want either. How about the
} option of an emacs-like {forward,backward}-word, which jumps to a
} different place depending on which direction you're heading, for
} example?
I imagine this was either an oversight, or works the way it does because
Paul Falstad didn't like having two spaces left behind following a
forward-word backward-delete-word sequence. I've long been using
bindkey -s '^[f' '^[E^F'
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-06-06 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-06 6:51 Bart Schaefer
1999-06-06 13:36 ` Adam Spiers
1999-06-06 16:20 ` Bart Schaefer [this message]
1999-06-06 14:13 ` Peter Stephenson
1999-06-06 16:40 ` Bart Schaefer
1999-06-09 16:34 ` WORDCHARS (Re: Call for opinions on a couple of prospective zsh patches) Bart Schaefer
1999-06-10 0:51 ` Stefan Monnier
1999-06-10 8:15 ` WORDCHARS, etc Peter Stephenson
1999-06-06 16:50 ` Call for opinions on a couple of prospective zsh patches Stefan Monnier
1999-06-06 17:13 ` Adam Spiers
1999-06-06 17:25 ` Bart Schaefer
1999-06-06 18:41 ` Stefan Monnier
1999-06-07 1:22 ` Bart Schaefer
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=990606162023.ZM10310@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@sunsite.auc.dk \
/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).