Simple Tip of the Day

Simple Tip of the Day

[zzapper]

Hi,

from your prompt type 
>bindkey
then 
> zstyle


to see what you've got setup and may have forgotten about

my favorite


bindkey -M viins '^O' copy-prev-word

"^O" copy-prev-word

allows me to type say

> cp longfilename.tex ^O
> cp longfilename.tex longfilename.tex
which I then modify

Your most useful binding?

-- 
zzapper
Success for Techies and Vim,Zsh tips
http://SuccessTheory.com/

Re: Simple Tip of the Day

[Jean Chalard]

> bindkey -M viins '^O' copy-prev-word
>
> "^O" copy-prev-word
>
> allows me to type say
>
> > cp longfilename.tex ^O
> > cp longfilename.tex longfilename.tex
> which I then modify
>
> Your most useful binding?

Definately
bindkey "ESC-[A" history-search-backward
bindkey "ESC-[B" history-search-forward
(the values of the keys may change according to your terminal. I
should use a termcap to get it actually, except I'm too lazy to look
it up ; they are really up and down arrow)
Type the beginning of a command, and you can navigate through your
history lines that begin with what you typed. Exactly the same thing
as the default binding, except it's more powerful.
Only that messes up zed, because it only accepts up-line-or-history to
go up. I suggested a patch on the zsh-workers mailing list long ago
that Bart greatly improved, but it never made it into the CVS.

Also, these are set by default but not that much known, so I'd like to mention
bindkey "ESC-q" push-line
...which pushes the current line onto a stack and pops it when a new
prompt appears. Useful when you started typing something, then you
realize you have to execute some other command before the one you were
typing.
and
bindkey "ESC-." insert-last-word
...which inserts the last word of the previous command, exactly like
your ^O binding does with the current line.

--
J
"Toi, je te trouve pas la même tête que sur la page précédente" -- Wakamiya

Re: Simple Tip of the Day

[Bart Schaefer]

On Oct 28,  8:32pm, Jean Chalard wrote:
} Subject: Re: Simple Tip of the Day
}
} Type the beginning of a command, and you can navigate through your
} history lines that begin with what you typed. Exactly the same thing
} as the default binding, except it's more powerful.
} Only that messes up zed, because it only accepts up-line-or-history to
} go up. I suggested a patch on the zsh-workers mailing list long ago
} that Bart greatly improved, but it never made it into the CVS.

A patch for zed?  Searching the archives, I can't find anything that
mentions you, me, and zed in the same article.  I did find the 2004
thread "Re: .zshrc sanity check" where PWS proposed a vared patch to
make zed use its own keymap ... but that patch appears to have been
applied.

Re: Simple Tip of the Day

[Jean Chalard]

> } Type the beginning of a command, and you can navigate through your
> } history lines that begin with what you typed. Exactly the same thing
> } as the default binding, except it's more powerful.
> } Only that messes up zed, because it only accepts up-line-or-history to
> } go up. I suggested a patch on the zsh-workers mailing list long ago
> } that Bart greatly improved, but it never made it into the CVS.
>
> A patch for zed?  Searching the archives, I can't find anything that
> mentions you, me, and zed in the same article.  I did find the 2004
> thread "Re: .zshrc sanity check" where PWS proposed a vared patch to
> make zed use its own keymap ... but that patch appears to have been
> applied.

Hmmm...
Indeed I was referring to that thread, I misremembered the one who
wrote the final patch *sorry Peter*...

I think I misunderstood something at that time, like the patch would
bind a new keymap to zed *and configure it*, and that I shouldn't have
to add lines in my configuration file to have zed rebind the keys.
Re-reading it now makes it so obvious I'm really ashamed to have just
lived with it for one year and a hald when I only needed to undestand
what Peter said.

Ok well my saying crap again will have pointed out the fact that
there's this simple way to have zed use the keys you like :)

--
J
"Toi, je te trouve pas la même tête que sur la page précédente" -- Wakamiya

Re: Simple Tip of the Day

[zzapper]

On Fri, 28 Oct 2005 20:32:12 +0900,  wrote:

I forgot
> compctl



-- 
zzapper
Success for Techies and Vim,Zsh tips
http://SuccessTheory.com/

Re: Simple Tip of the Day

[Hannu Koivisto]

zzapper <david@tvis.co.uk> writes:

> bindkey -M viins '^O' copy-prev-word
>
> "^O" copy-prev-word
>
> allows me to type say
>
>> cp longfilename.tex ^O
>> cp longfilename.tex longfilename.tex
> which I then modify

Wouldn't copy-prev-shell-word be even more useful for that purpose?
It handles things like cp filename\ with\ spaces.txt ^O

> Your most useful binding?

Hmm, I can't name just one.  But I couldn't imagine using zsh
without the following:

bindkey '^[[A' history-beginning-search-backward # "Up"
bindkey '^[[B' history-beginning-search-forward  # "Down"
bindkey -s '^[[5~' 'cds\r' # "PageUp"

Just in case you are wondering what that 'cds' is, it is an
interactive way to select a directory from the directory
stack-treated-as-history, along the lines of a similar feature in
4nt:

cds () {
    local DIR="$PWD"
    if [[ ! -z "$dirstack" ]]; then
        DIR=$(print -rl $dirstack | tac \
            | iselect -a -f -n chdir -Q "$PWD" -t "Change directory to..." -p ${#dirstack})
    fi
    cd "$DIR"
}

As you can see, it requires 'iselect' utility that is available as
a Debian package, for example.  (I wish I could implement an
iselect replacement using only zsh/zle.)  Also, in order to be
useful it requires you to setopt auto_pushd.  I also setopt
pushd_ignore_dups and set DIRSTACKSIZE to a reasonably large value.

-- 
Hannu

Re: Simple Tip of the Day

[Nikolai Weibull]

Hannu Koivisto wrote:

> zzapper <david@tvis.co.uk> writes:

> > bindkey -M viins '^O' copy-prev-word
> >
> > "^O" copy-prev-word

> Wouldn't copy-prev-shell-word be even more useful for that purpose?
> It handles things like cp filename\ with\ spaces.txt ^O

What I was going to say as well, but thanks for introducing
copy-prev-word to me, as I was wanting that functionality but hadn't
found it earlier.

> > Your most useful binding?

> Hmm, I can't name just one.  But I couldn't imagine using zsh without
> the following:
> 
> bindkey '^[[A' history-beginning-search-backward # "Up"
> bindkey '^[[B' history-beginning-search-forward  # "Down"

Like Vim does it.  I have only one binding for these:

bindkey "^X^L" history-beginning-search-backward

That's also how Vim does it, in insert mode.

My most useful binding is

_sudo-command-line() {
  [[ $BUFFER != sudo\ * ]] && LBUFFER="sudo $LBUFFER"
}
zle -N sudo-command-line _sudo-command-line
bindkey "^Os" sudo-command-line

as I always forget to add a sudo...

> Just in case you are wondering what that 'cds' is, it is an
> interactive way to select a directory from the directory
> stack-treated-as-history, along the lines of a similar feature in 4nt:
> 
> cds () {
>     local DIR="$PWD"
>     if [[ ! -z "$dirstack" ]]; then
>         DIR=$(print -rl $dirstack | tac \
>             > iselect -a -f -n chdir -Q "$PWD" -t "Change directory to..." -p ${#dirstack})
>     fi
>     cd "$DIR"
> >
> 
> As you can see, it requires 'iselect' utility that is available as a
> Debian package, for example.  (I wish I could implement an iselect
> replacement using only zsh/zle.)  Also, in order to be useful it
> requires you to setopt auto_pushd.  I also setopt pushd_ignore_dups
> and set DIRSTACKSIZE to a reasonably large value.

Here's my version of a command like that:

~/.zsh/functions/d:

# contents: d command.
#
# Copyright © 2005 Nikolai Weibull <nikolai@bitwi.se>

emulate -L zsh

autoload -U colors

local color=$fg_bold[blue]
integer i=0
dirs -p | while read dir; do
  local num="${$(printf "%-4d " $i)/ /.}"
  printf " %s  $color%s$reset_color\n" $num $dir
  (( i++ ))
done
integer dir=-1
read -r 'dir?Jump to directory: ' || return
(( dir == -1 )) && return
if (( dir < 0 || dir >= i )); then
  echo d: no such directory stack entry: $dir
  return 1
fi
cd ~$dir

I don't know how iselect works, but this works very well for me.

-- 
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Re: Simple Tip of the Day

[Konstantin Sobolev]

On Friday 28 October 2005 15:47, Hannu Koivisto wrote:
> bindkey -s '^[[5~' 'cds\r' # "PageUp"
>
> Just in case you are wondering what that 'cds' is, it is an
> interactive way to select a directory from the directory
> stack-treated-as-history, along the lines of a similar feature in
> 4nt:
>
> cds () {
>     local DIR="$PWD"
>     if [[ ! -z "$dirstack" ]]; then
>         DIR=$(print -rl $dirstack | tac \
>
>             | iselect -a -f -n chdir -Q "$PWD" -t "Change directory to..."
>             | -p ${#dirstack})
>
>     fi
>     cd "$DIR"
> }

I'm using menu completion for this:

bindkey "^Z" "menu-complete"
bindkey -s '\ec' 'cd -^Z'

-- 
/KoS
* Any program will expand to fill all memory PLUS ONE BYTE!	      

Re: Simple Tip of the Day

[Christian Taylor]

Konstantin Sobolev wrote:
> On Friday 28 October 2005 15:47, Hannu Koivisto wrote:
> > bindkey -s '^[[5~' 'cds\r' # "PageUp"
> >
> > Just in case you are wondering what that 'cds' is, it is an
> > interactive way to select a directory from the directory
> > stack-treated-as-history, along the lines of a similar feature in
> > 4nt:
> >
[...]
>
> I'm using menu completion for this:
>
> bindkey "^Z" "menu-complete"
> bindkey -s '\ec' 'cd -^Z'

I'm using something very similar:

zle -N select-from-cd-stack
select-from-cd-stack() {
    LBUFFER=$LBUFFER"~+"
    zle menu-complete
    if [[ ${LBUFFER[-2,-1]} = "~+" ]]; then
        LBUFFER=${LBUFFER[1,-3]}
    fi
}
bindkey '\ed' select-from-cd-stack

The advantage is that I can also use it for other commands like cp (for 
example when I want to copy a file from a directory in the stack to the 
current one). And since I have setopt auto_cd, I can instantly jump to 
directories in the stack.

Another (default) binding that I really like is:
bindkey "^[h" run-help

Christian

run-help and \cmd (was: Simple Tip of the Day)

[Vincent Lefevre]

On 2005-10-29 16:52:30 +0200, Christian Taylor wrote:
> Another (default) binding that I really like is:
> bindkey "^[h" run-help

BTW, I've just seen that it doesn't work when the command starts with
a backslash (to avoid aliases). I assume that this is a bug.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: run-help and \cmd (was: Simple Tip of the Day)

[Peter Stephenson]

Vincent Lefevre wrote:
> On 2005-10-29 16:52:30 +0200, Christian Taylor wrote:
> > Another (default) binding that I really like is:
> > bindkey "^[h" run-help
> 
> BTW, I've just seen that it doesn't work when the command starts with
> a backslash (to avoid aliases). I assume that this is a bug.

You mean run-help on \ls doesn't work?  The shell doesn't know what the
run-help alias/function is going to do with the information so provides
exactly what it got.  Using a more sophisticated version of run-help would
do the trick; even turning "man $1" into "eval man $1" would work.
However, that's a little dangerous to have as the default.

(GNU man seems to accept "man '\ls'", as it happens.)

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com

Re: run-help and \cmd (was: Simple Tip of the Day)

[Peter Stephenson]

Peter Stephenson <pws@csr.com> wrote:
> You mean run-help on \ls doesn't work?  The shell doesn't know what the
> run-help alias/function is going to do with the information so provides
> exactly what it got.  Using a more sophisticated version of run-help would
> do the trick; even turning "man $1" into "eval man $1" would work.
> However, that's a little dangerous to have as the default.

Slightly more helpfully, here is the run-help function supplied with the
shell enhanced to strip quotes (and suppress alias lookup for the stripped
word) when that makes a difference.

Index: Functions/Misc/run-help
===================================================================
RCS file: /cvsroot/zsh/zsh/Functions/Misc/run-help,v
retrieving revision 1.4
diff -u -r1.4 run-help
--- Functions/Misc/run-help	2 Apr 2001 13:04:05 -0000	1.4
+++ Functions/Misc/run-help	1 Nov 2005 18:20:50 -0000
@@ -33,15 +33,22 @@
 fi
 
 # No zsh help; use "whence" to figure out where else we might look
-local what places newline='
+local what places noalias newline='
 '
 integer i=0 didman=0
 
 places=( "${(@f)$(builtin whence -va $1)}" )
+if [[ $places = *"not found"* && $1 != ${(Q)1} ]]; then
+  # Different when unquoted, so try stripping quotes.
+  places=( "${(@f)$(builtin whence -va ${(Q)1})}" )
+  # Quotation is significant to aliases, so suppress lookup.
+  noalias=1
+fi
 
 while ((i++ < $#places))
 do
     what=$places[$i]
+    [[ -n $noalias && $what = *" is an alias "* ]] && continue
     builtin print -r $what
     case $what in
     (*( is an alias)*)


-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com

Re: run-help and \cmd (was: Simple Tip of the Day)

[Vincent Lefevre]

On 2005-11-01 18:02:48 +0000, Peter Stephenson wrote:
> You mean run-help on \ls doesn't work?

It tries to call run-help on \ls instead of ls. What I mean is that
run-help should drop the backslash.

> (GNU man seems to accept "man '\ls'", as it happens.)

No, it doesn't.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: Simple Tip of the Day

[DervishD]

    Hi zzapper :)

 * zzapper <david@tvis.co.uk> dixit:
> Your most useful binding?

    Mmm, difficult to say... Probably <ESC>-<ESC>, which I have bound
to "kill-buffer", to clean the command line when I have "running
fingers" and screw it badly XDD

    My ^Q (push-line-or-edit) is very useful for me, too.

    Really, the entire Zle thing is superb. If it were a library...
But nobody is perfect (Zle is *almost* perfect, then).  ;)))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...

Re: Simple Tip of the Day

[Philippe Troin]

zzapper <david@tvis.co.uk> writes:

> Your most useful binding?

"^O" accept-line-and-down-history

Allows someone to repeat a sequence of commands.
Eg.

    % foo <ENTER>
    -foo-output-
    % bar <ENTER>
    -foo-output-
    % baz <ENTER>
    -foo-output-
    % <Up> <Up> <Up>

prompt now shows:

    % foo <CTRL-O>
    -foo-output-
    % bar <CTRL-O>
    -foo-output-
    % baz <ENTER>
    -foo-output-
    %

Easier seen than described.

Phil.

Re: Simple Tip of the Day

[Vincent Lefevre]

On 2005-10-29 22:10:55 -0700, Philippe Troin wrote:
> zzapper <david@tvis.co.uk> writes:
> 
> > Your most useful binding?
> 
> "^O" accept-line-and-down-history

I use it very often. Also, these ones seem to be interesting,
but are not documented:

"^[," _history-complete-newer
"^[/" _history-complete-older

What's the difference?

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA