zsh-users
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh-users@sunsite.dk
Subject: Re: cd to a file
Date: Mon, 16 Apr 2007 18:00:51 +0200	[thread overview]
Message-ID: <20070416160051.GB28724@fsst.voodoo.lan> (raw)
In-Reply-To: <20070416144016.GA20630@spiegl.de>

Andy Spiegl <zsh.Andy@spiegl.de>:
[...]
> # cd to a file should take you to the dir that contains the file
> # courtesy of Artur Penttinen <artur@niif.spb.su>
> function cd () {
>   if [[ -n $2 ]]; then
>     builtin cd $1 $2
>   elif [[ -f $1 ]]; then
>     builtin cd $1:h
>   else
>     builtin cd $*
>   fi
> }
> 
> Could still be optimized though, I guess.

I once did a 'cd'-wrapper function, that also tries to do some basic
error correction (this is also on <http://zshwiki.org>):

[snip]
function smart_cd () {
  if [[ -f $1 ]] ; then
    [[ ! -e ${1:h} ]] && return 1
    print correcting ${1} to ${1:h}
    builtin cd ${1:h}
  else
    builtin cd ${1}
  fi
}

function cd () {
  setopt localoptions
  setopt extendedglob
  local approx1 ; approx1=()
  local approx2 ; approx2=()
  if (( ${#*} == 0 )) || [[ ${1} = [+-]* ]] ; then
    builtin cd "$@"
  elif (( ${#*} == 1 )) ; then
    approx1=( (#a1)${1}(N) )
    approx2=( (#a2)${1}(N) )
    if [[ -e ${1} ]] ; then
      smart_cd ${1}
    elif [[ ${#approx1} -eq 1 ]] ; then
      print correcting ${1} to ${approx1[1]}
      smart_cd ${approx1[1]}
    elif [[ ${#approx2} -eq 1 ]] ; then
      print correcting ${1} to ${approx2[1]}
      smart_cd ${approx2[1]}
    else
      print couldn\'t correct ${1}
    fi
  elif (( ${#*} == 2 )) ; then
    builtin cd $1 $2
  else
    print cd: too many arguments
  fi
}
[snap]

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925


  reply	other threads:[~2007-04-16 16:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-19 12:43 More zsh tricks required please zzapper
2004-06-19 13:06 ` Christian Schneider
2004-06-20 12:19 ` Julius Plenz
2004-06-21  0:38 ` Drew Perttula
2007-04-16 14:40   ` cd to a file Andy Spiegl
2007-04-16 16:00     ` Frank Terbeck [this message]
2007-04-18  1:08       ` Andy Spiegl
2007-04-21 15:12       ` Atom Smasher
2007-04-22 18:18         ` Frank Terbeck
2007-04-23  8:45           ` Atom Smasher

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=20070416160051.GB28724@fsst.voodoo.lan \
    --to=ft@bewatermyfriend.org \
    --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).