searching upwards from cwd

searching upwards from cwd

[Dominik Vogt]

The EQUALS option is very handy, and I'd like to have something similary,
but with a different search path.  My working directory, is structured like this:

  work/
    adresses.txt
    cvs/
      projectx/
        src/
          foo/
      projecty/
        ...

I'd like to be able to open addresses.txt in a single command without knowing
about the working directory.  At the moment, the command depends on cwd:

  work/  =>  less addresses.txt
  work/cvs/  =>  less ../addresses.txt
  work/cvs/projectx/  =>  less ../../addresses.txt
  work/cvs/projectx/src/  =>  less ../../../addresses.txt

It would be very helpful to have an alternative syntax similar to
'**/<filename>' and '=<filename>' that looks upwards in the path.  Maybe

  **/adresses.txt   =>  look in all subdirs
  =addresses.txt => look in the PATH
  .=addresses.txt => successively look in ., .., ../.., ../../.. and so on
  **.=addresses.txt => works like .=, and if that fails works like **/

(or whatever the syntax would be).

I'd be happy to have it as a zsh function, but I think it could be done
much more efficient in the source code.

Ciao

Dominik ^_^  ^_^

P.S.:  Please CC me for fast replies.
-- 


Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

Re: searching upwards from cwd

[Marc Chantreux]

Hi Dominik,

le 19/06/2006,
Dominik Vogt nous écrivait :
> 
> I'd like to be able to open addresses.txt in a single command without knowing
> about the working directory.  At the moment, the command depends on cwd:
> 
>   work/  =>  less addresses.txt
>   work/cvs/  =>  less ../addresses.txt
>   work/cvs/projectx/  =>  less ../../addresses.txt
>   work/cvs/projectx/src/  =>  less ../../../addresses.txt

is this enought ? 

from () {
        local base=${PWD%/$1/*}/$1
        shift
        print -l $base/${~^*}
}

less $( from works '**/adresses.txt' )

regards

Re: searching upwards from cwd

[Bart Schaefer]

On Jun 19, 10:15am, Dominik Vogt wrote:
}
} It would be very helpful to have an alternative syntax similar to
} '**/<filename>' and '=<filename>' that looks upwards in the path.

setopt extendeglob
less (../)#addresses.txt

Re: searching upwards from cwd

[Dominik Vogt]

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

On Mon, Jun 19, 2006 at 11:13:28AM +0200, Marc Chantreux wrote:
> Hi Dominik,
> 
> le 19/06/2006,
> Dominik Vogt nous écrivait :
> > 
> > I'd like to be able to open addresses.txt in a single command without knowing
> > about the working directory.  At the moment, the command depends on cwd:
> > 
> >   work/  =>  less addresses.txt
> >   work/cvs/  =>  less ../addresses.txt
> >   work/cvs/projectx/  =>  less ../../addresses.txt
> >   work/cvs/projectx/src/  =>  less ../../../addresses.txt
> 
> is this enought ? 
> 
> from () {
>         local base=${PWD%/$1/*}/$1
>         shift
>         print -l $base/${~^*}
> }
> 
> less $( from works '**/adresses.txt' )

Ah, that's not quite what I'm looking for.  It's too much to type
- I could as well try an increasing numer of '../' components and
hit TAB every time.

Dominik ^_^  ^_^

 --
Dominik Vogt, dominik.vogt@gmx.de

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: searching upwards from cwd

[Sami Samhuri]

On 19-Jun-06, at 6:11 PM, Bart Schaefer wrote:

> On Jun 19, 10:15am, Dominik Vogt wrote:
> }
> } It would be very helpful to have an alternative syntax similar to
> } '**/<filename>' and '=<filename>' that looks upwards in the path.
>
> setopt extendeglob
> less (../)#addresses.txt
>

How incredibly useful. zsh continues to astound me every time I read  
this list. Pretty much every time someone asks for something, the zsh  
devs have already implemented it. Any zsh devs reading this, thank  
you for making zsh the best shell around, bar none. Keep up the  
excellent work!

Sami

Re: searching upwards from cwd

[Dominik Vogt]

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Mon, Jun 19, 2006 at 11:03:57PM +0200, Dominik Vogt wrote:
> On Mon, Jun 19, 2006 at 11:13:28AM +0200, Marc Chantreux wrote:
> > le 19/06/2006,
> > Dominik Vogt nous écrivait :
> > > 
> > > I'd like to be able to open addresses.txt in a single command without knowing
> > > about the working directory.  At the moment, the command depends on cwd:
> > > 
> > >   work/  =>  less addresses.txt
> > >   work/cvs/  =>  less ../addresses.txt
> > >   work/cvs/projectx/  =>  less ../../addresses.txt
> > >   work/cvs/projectx/src/  =>  less ../../../addresses.txt
> > 
> > is this enought ? 
> > 
> > from () {
> >         local base=${PWD%/$1/*}/$1
> >         shift
> >         print -l $base/${~^*}
> > }
> > 
> > less $( from works '**/adresses.txt' )
> 
> Ah, that's not quite what I'm looking for.  It's too much to type
> - I could as well try an increasing numer of '../' components and
> hit TAB every time.

Hm, this is close:

  less (../)#adr*

But is there any way to prevent the globbing pattern is expanded
to multiple words?  I just want the first/shortest match.

Ciao

Dominik ^_^  ^_^

 --
Dominik Vogt, dominik.vogt@gmx.de

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: searching upwards from cwd

[Bart Schaefer]

On Jun 20,  8:28pm, Dominik Vogt wrote:
}
}   less (../)#adr*
} 
} But is there any way to prevent the globbing pattern is expanded
} to multiple words?  I just want the first/shortest match.

Try

    less (../)#adr*(Odon[1])