zsh-users
 help / color / mirror / code / Atom feed
From: Scott Anderson <ee_in_co@yahoo.com>
To: zsh-users@sunsite.dk
Subject: Re: Redirection Symbol After Completion
Date: Mon, 10 Jul 2006 16:30:07 -0700 (PDT)	[thread overview]
Message-ID: <20060710233007.10408.qmail@web30715.mail.mud.yahoo.com> (raw)
In-Reply-To: <20060710141220.GA11832@namib.cs.utk.edu>

----- Original Message ----
From: Chris Johnson <cjohnson@cs.utk.edu>
To: zsh-users@sunsite.dk
Sent: Monday, July 10, 2006 8:12:20 AM
Subject: Re: Redirection Symbol After Completion

Bart Schaefer sent me the following 1.9K:

> } > I personally find commands easier to parse with my eye when the space
> } > remains before the redirection symbol:
> } > 
> } >    cat file.txt |
> } > 
> } > Is there any way to force this space to persist even if I type a
> } > redirection operator?
> 
>     self-insert-redir() {
>         integer l=$#LBUFFER
>            zle self-insert
>            (( $l >= $#LBUFFER )) && LBUFFER[-1]=" $LBUFFER[-1]"
>     }
>     zle -N self-insert-redir
>     for op in \| \< \> \&
>     do bindkey "$op" self-insert-redir
>     done
> 
> I like that so much I might even keep it.

This is not working for me.

> ls
noname

> cat no<TAB>

  completes the file as expected.

> cat noname<SPACE>

  Then I type "|"

> cat noname cat noname|[-1]

Am I missing an option?

> echo $ZSH_NAME $ZSH_VERSION
zsh 4.3.2

> setopt
autocd
autopushd
nobeep
nobgnice
correct
extendedglob
extendedhistory
histfindnodups
histignorealldups
histignoredups
histnostore
histsavenodups
nohup
incappendhistory
interactive
interactivecomments
ksharrays
kshglob
monitor
nonomatch
numericglobsort
promptsubst
pushdignoredups
pushdminus
pushdsilent
sharehistory
shinstdin
shwordsplit
zle

Thanks in advance for the help.

Scott




  reply	other threads:[~2006-07-10 23:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 17:32 Chris Johnson
2006-07-08 11:44 ` Peter Stephenson
2006-07-08 17:56   ` Bart Schaefer
2006-07-08 21:44     ` Bart Schaefer
2006-07-10 14:12     ` Chris Johnson
2006-07-10 23:30       ` Scott Anderson [this message]
2006-07-10 23:43         ` Bart Schaefer
2006-07-10 23:53           ` Scott Anderson

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=20060710233007.10408.qmail@web30715.mail.mud.yahoo.com \
    --to=ee_in_co@yahoo.com \
    --cc=zsh-users@sunsite.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).