CD to "next dir" ??

[Stein Oiestad]

I wonder how I could make an alias that let me go to the "next directory" at the same level.

If the alias is called CDNEXT

Example
¨
c:\
c:\Dir1
c:\Dir1\SubDirA
c:\Dir1\SubDirB
c:\Dir2
c:\Dir2\SubDirC

Command => Result
In c:\Dir1 - CDNEXT ==>> c:\Dir2
In c:\Dir1\SubDirA ==>> c:\Dir1\SubDirB

In the follow folders, the command would be "invalid"
c:\Dir1\SubDirB
c:\Dir2
c:\Dir2\SubDirC

Why ?
For example, cleanup in a bunch of folders.

Why not use GUI/File Manager ??
Due to Visual impairment

Thanks for any tip!

 

[samintz]

Try this. Copy it into CDNEXT.BTM

setlocal
dir /f /a:d /o:n .. > ..\$.tmp
do i = 0 to %@lines[..\$.tmp]
  iff '%@line[..\$.tmp,%i]' == '%_cwd' then
    set dn=%@line[..\$.tmp,%@inc[i]]
    iff '%dn' == '**EOF**' then
      beep
    else
      cd %dn
    endiff
    leave
  endiff
enddo
del /q ..\$.tmp
endlocal /d

 

[rps]

I wonder how I could make an alias that let me go to the "next directory" at the same level.

If the alias is called CDNEXT

Example
¨
c:\
c:\Dir1
c:\Dir1\SubDirA
c:\Dir1\SubDirB
c:\Dir2
c:\Dir2\SubDirC

Command => Result
In c:\Dir1 - CDNEXT ==>> c:\Dir2
In c:\Dir1\SubDirA ==>> c:\Dir1\SubDirB

In the follow folders, the command would be "invalid"
c:\Dir1\SubDirB
c:\Dir2
c:\Dir2\SubDirC

Why ?
For example, cleanup in a bunch of folders.

Why not use GUI/File Manager ??
Due to Visual impairment

Thanks for any tip!

Scott provided the solution to your OP.
Just thought I would add one more to the mix.
These btm's can be used together to visit all directories in a tree.

─────────────────────────────────────────────────────────────
XOVER.BTM             12/09/2014 16:29           3,131 bytes
  When used with XIN, changes to the next subdirectory at the same level as the current directory after executing XIN. Moves up
 one directory and then down to the next one in order.

XIN.BTM               12/09/2014 16:35           2,270 bytes
  Changes to the first subdir of your current directory. Moves down one directory level from the current; used in tandem with x
over.btm is a method to traverse through an entire directory structure, one directory at a time.
────────────────────────────────────────────────────────────────

These were written by Klaus Meinhard many years ago. I may have tweaked them a bit. Enjoy!

 

[samintz]

Another option would be to pre-populate a dirstack and just keep POPD-ing to go down the list.

do d in /a:d * (pushd %d)

You can use DIRS to see the list.

 

[Bill de Haan]

I wrote these a couple of years ago. I map my <C-N> to next, and <C-P> to prev

 

[MaartenG]

alias CDNEXT=`(if "..\%@filename[%CD]" ne "%@FINDFIRST[..\*,+D-L]" do until  "..\%@filename[%CD]" eq "%@FINDNEXT[..\*,+D-L]" (REM) ) & *CD %@FINDNEXT[..\*,+D-L] & if %@FINDCLOSE[] ne 0 BEEP`

 

[rps]

alias CDNEXT=`(if "..\%@filename[%CD]" ne "%@FINDFIRST[..\*,+D-L]" do until  ........

Nice, added to my collection of aliases.

 

[rps]

Another option would be to pre-populate a dirstack and just keep POPD-ing to go down the list.

do d in /a:d * (pushd %d)

You can use DIRS to see the list.

Thanks.
I get a "Change directory" popup menu when I use this method.
x'ing out of all the menu's produces a dirs stack with several duplicate directories in the stack.
Not sure exactly what I have in my particular settings, so I need to do further testing.
One thing I did add was a /x to keep these directories from being placed in the dir history.

 

[rps]

I wrote these a couple of years ago. I map my <C-N> to next, and <C-P> to prev

I assume the mappings (<C-N> to next, and <C-P> to prev) you're using are keyboard aliases:
alias @@ctrl-n=`next.btm`
alias @@ctrl-p=`Prev.btm`

The <ctrl-p> doesn't work on my setup. Need to do some further investigation.

Probably will just use a different key combination.

Thanks for contributing!

 

[Charles G]

Thanks.
I get a "Change directory" popup menu when I use this method.
x'ing out of all the menu's produces a dirs stack with several duplicate directories in the stack.
Not sure exactly what I have in my particular settings, so I need to do further testing.
One thing I did add was a /x to keep these directories from being placed in the dir history.

Why not just change it to:

do d in /a:d * (pushd %@full[%d])

 

[rps]

Why not just change it to:

do d in /a:d * (pushd %@full[%d])

Tried your suggestion and this is the result:

D:\bat>do d in /a:d * (pushd %@full[%d])
TCC: (Sys) The system cannot find the path specified.
 "\BAT\4dosbof\4dostips"
TCC: (Sys) The system cannot find the path specified.
 "\BAT\4dosbof\4dtnt"
TCC: (Sys) The system cannot find the path specified.
 "\BAT\4dosbof\4xbtm6"
TCC: (Sys) The system cannot find the path specified.
 "\BAT\4dosbof\4xbtm7"
...................

After all the errors, one for each directory in c:\bat, I was left here with only d:\bat in the stack.

D:\BAT\4dosbof>dirs
D:\bat

Does this actually work on your system?

 

[David Marcus]

This is different, but I have an alias "r" defined as "select (*)". This lets me change to a subdirectory by selecting it or select one or more files to run.

 

[jmcm]

alias ..*.....=%0\

 

[vefatica]

alias ..*.....=%0\

I don't believe that gives the desired behavior. I think this does (using a couple of plugins).

v:\> d /a:d /b /f
V:\4pluginsPre17
V:\20000files
V:\cksum
V:\ip
V:\IPReg
V:\zippers

v:\> cdin

v:\20000files> cdnext

v:\4pluginspre17> cdnext

v:\cksum> cdnext

v:\ip> cdnext

v:\ipreg> cdnext

v:\zippers>