From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21143 invoked from network); 23 Dec 2002 04:47:46 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 23 Dec 2002 04:47:46 -0000 Received: (qmail 18033 invoked by alias); 23 Dec 2002 04:47:35 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5605 Received: (qmail 18022 invoked from network); 23 Dec 2002 04:47:35 -0000 Date: Sun, 22 Dec 2002 21:29:18 -0500 From: David B Harris To: zsh-users@sunsite.dk Subject: Re: The removal of spaces after a tab-complete Message-Id: <20021222212918.1ad0a19d.david@eelf.ddts.net> In-Reply-To: <1021223012821.ZM13386@candle.brasslantern.com> References: <20021221203256.3445250b.david@eelf.ddts.net> <1021223012821.ZM13386@candle.brasslantern.com> Organization: Tachyon Systems X-Mailer: Sylpheed version 0.8.6claws70 (GTK+ 1.2.10; ) X-Face: +!jI>15IbOmQ\xxdkL/F"p-?6];tG@;:BK5ZD=8d^?gO-pt[$5r"W|Hlwz-gv-tMCU0H::n 2!T5}SW:j9'3bc/U:=D8O'J}Fq)3TX#<|C?S0nR]}I?JFM{?Sf$LrJ{*Ho\:d/:Cs/ kpJH:[Wmxox8JXSY# Mail-Copies-To: nobody Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=./.hfE_MFeys0N=" --=./.hfE_MFeys0N= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 23 Dec 2002 01:28:21 +0000 "Bart Schaefer" wrote: > You can't turn it off. You can only forcibly defeat it. You can > either define your own completions with auto-suffix-removal disabled, > for every situation in which you don't want this to happen; or you can > re-bind the specific keys for which, when typed after a completion, it > should not happen. The latter is probably easier: I suspected as much, at least for the auto-suffx-removal stuff; after I read largish portions of zshcomp*(1), I got worried ;) > function self-insert-no-autoremove { > LBUFFER="$LBUFFER$KEYS" > } > zle -N self-insert-no-autoremove > bindkey '|' self-insert-no-autoremove > > The reasons why you can't turn it off are varied and in some instances > nearly lost in the mists of time, but it boils down to something like: > (1) it was automatically added, so it's not costing you keystrokes if > it automatically goes away again; (2) the absence of the space doesn't > matter to the syntax; (3) there are more cases where leaving the space > is wrong, than cases where removing it is wrong; so (4) if you really > want a space there, you can just type one yourself. Thanks a bunch for the help :) I appreciate it a lot. P.S.: For the other poster to this tread asking why I needed it off, the answer is: "I don't". I don't need it off, I want it off. I do a lot of shell script writing for my work, and I do the prototypes live in an interactive shell. Once I've poked it enough, I copy and paste it into the shell script. Spaces around punctuation make things much more readable. Have you tried to maintain a 50k shell script that wasn't formatted nicely? :) I've just been having to go through re-editing the paste, and it proves irritating. That's all. No "need" involved. --=./.hfE_MFeys0N= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+BnT+uCQ/g7GxJcARApqbAJ90lcmu4yFGN+S4XDw+UIsMtTHzhwCeLzBx I5A3h4oOoPVkix7DRiofzxg= =O+Hl -----END PGP SIGNATURE----- --=./.hfE_MFeys0N=--