Expedient way to move around the Linux CLI

kasprosian · 2014-02-27 23:50:27

Hey all,

Hope all is well. Recently, I programmed a solution for a common problem. When you're SSH'd into a server, it's a pain in the ass to cd around. Well, I wrote a small bash script that should make this much quicker.

It operates on the habit of bookmarking. If you're at a directory that you want to bookmark, you do this:

aguo@unix1:~/Documents/10605$ j add

Type an alias for the current working directory, or ^C to quit:

ml

and "j ml" -> ~/Documents/10605, etc.

To install, just save my .jrc file as "~/.jrc", and then ". .jrc" in your ".bashrc".

https://github.com/mallochine/jarvis2

--Kasprosian

graysky · 2014-02-27 23:51:20

Neat. As an aside, are you aware of autojump?

kasprosian · 2014-02-27 23:56:01

Yup. I programmed something similar to autojump earlier here, and you guys provided the feedback that it was an also-ran: https://bbs.archlinux.org/viewtopic.php?id=167550

Last edited by kasprosian (2014-02-27 23:56:28)

karol · 2014-02-28 00:15:34

Do cdable vars work through ssh?
In bash 'shopt -s cdable_vars' + 'export apps="/home/karol/apps"' =

$ pwd
/home/karol/test
$ cd apps
/home/karol/apps
$ pwd
/home/karol/apps

kasprosian · 2014-02-28 00:20:26

They work, and so do aliases. The main idea of "j" was to prevent the buildup of these variables/aliases in your .bashrc. Also, when you do "export apps=...", that's essentially adding a bookmark. This just automates that process, since it can get really cumbersome when you have many different variables and a huge filesystem.

bulletmark · 2014-02-28 00:51:53

Here's my solution. I have used this all day every day for more than 20 years (I wrote it in shell before it became python). It aliases your normal cd command to automatically keep a stack of previous directories. See https://github.com/bulletmark/cdhist.

kasprosian · 2014-02-28 01:00:07

Cool! I like the Makefile, which saves the user from having to think about installation.

zeltak · 2014-03-21 07:30:53

hya

this looks cool, would it be OK to ask for an AUR package for the sake of keeping everything nice and clean

best

Z

karol · 2014-03-21 07:38:20

zeltak wrote:

this looks cool, would it be OK to ask for an AUR package for the sake of keeping everything nice and clean

There's already a 'jarvis' package or two: https://aur.archlinux.org/packages.php?K=jarvis
Using the name 'jarvis2' could be confusing.

tomk · 2014-03-21 10:54:45

A package is pointless here, since it's just a dotfile in your $HOME.

kasprosian · 2014-03-22 21:45:48

Hey zeltak,

I dunno how i'd make a AUR package...would it be that useful? To install jarvis2, you'd just have to "git clone https://github.com/mallochine/jarvis2.git" and then run "make bash". If you want to uninstall/reinstall, run "make uninstall", "make reinstall".

Is that helpful?

Mr Green · 2014-03-28 21:41:26

With the 'j edit' thought I would add a shortcut to the list, it does not work until you source .bashrc again.
You could use $EDITOR if set. Does do the job and will come in handy.

Since you are installing if you like to a users home directory there is little point of a package. If you want Jarvis to be system wide then you would need to one. Of course that would mean it becomes a script rather then a sourced file.

Thanks for sharing

zeltak · 2014-03-29 05:05:35

thx kasprosian

EDIT: i solved the below with using source ~/.jrc but now another error appears:

jarvis_jump:9: = not found

............................................................................................................................

i did what you suggested to install but i get an error each time i open my terminal (im using zsh btw)

i have .jrc in my home root folder and this in my .zshrc

#jarvis
. .jrc

what am i missing here

best

Z

Last edited by zeltak (2014-03-29 05:20:25)

Mr Green · 2014-03-29 07:26:47

Quick change

# allow $EDITOR if set
function jarvis_edit {
  [[ -z "$EDITOR" ]] && ed=vim || ed=$EDITOR
  ${ed} $JARVIS_HOME"/.jarvis"
}

kasprosian · 2014-03-29 18:33:36

Mr Green, that's an awesome addition. I'll add it to jarvis2 right now.

zeltak, I didn't test it for zsh -- I just assumed that it would work in zsh if it worked in bash. Let me test it quickly.

Mr Green · 2014-03-29 19:05:03

This one might be more controversial

function jarvis_all {
  #cat ~/.jarvis
  while read line
  do
    echo ${line}
  done <~/.jarvis
}

Mr Green · 2014-03-29 19:10:10

Maybe

function jarvis_main {
  case ${1} in

kasprosian · 2014-03-29 19:33:32

zeltak, I just fixed the problem. It was very non-trivial. You won't believe the differences there are between bash and zsh

git clone https://github.com/mallochine/jarvis2.git
make zsh

Then restart your shell.

kasprosian · 2014-03-29 19:34:50

lol Mr Green, not use cat for that? hm...OK I guess...

is ${1} compatible across shells?

kasprosian · 2014-03-29 19:35:22

Mr Green, you have idea how to fix this ugly code?

if [[ $JARVIS_SH == *bash* ]];
then
name=$(echo ${parsed[0]})
to=$(echo ${parsed[1]})
fi

if [[ $JARVIS_SH == *zsh* ]];
then
name=$(echo ${parsed[1]})
to=$(echo ${parsed[2]})
fi

kasprosian · 2014-03-29 19:37:57

Mr Green, gonna put this code in for jarvis_all:

60 function jarvis_all {
61 #cat ~/.jarvis
62 while read line
63 do
64 echo ${line}
65 done < JARVIS_HOME"/.jarvis"
66 }

Mr Green · 2014-03-29 19:46:30

Not really clear on what 'j jump' does exactly,

[[ $test == "*bash*" ]] && to="foo"; name="bar"

kasprosian · 2014-03-29 21:10:54

well, "j jump" tries to find the bookmark for "jump". you mean jarvis_jump? The arrays are indexed differently in zsh and bash! zsh starts at 1, while bash starts 0. I was wondering whether I was doing anything wrong there...

Saint0fCloud · 2014-03-30 01:20:36

So many subshells! Sent a github pull that simplifies your code a bit.

Sidenote, to make zsh index arrays begin with '0' you have to enable the option ksh_arrays.

kasprosian · 2014-03-30 03:24:53

yeah dude, kudos. I obviously still have a lot to learn, which is why I'm glad I open sourced it!

Arch Linux

#1 2014-02-27 23:50:27

Expedient way to move around the Linux CLI

#2 2014-02-27 23:51:20

Re: Expedient way to move around the Linux CLI

#3 2014-02-27 23:56:01

Re: Expedient way to move around the Linux CLI

#4 2014-02-28 00:15:34

Re: Expedient way to move around the Linux CLI

#5 2014-02-28 00:20:26

Re: Expedient way to move around the Linux CLI

#6 2014-02-28 00:51:53

Re: Expedient way to move around the Linux CLI

#7 2014-02-28 01:00:07

Re: Expedient way to move around the Linux CLI

#8 2014-03-21 07:30:53

Re: Expedient way to move around the Linux CLI

#9 2014-03-21 07:38:20

Re: Expedient way to move around the Linux CLI

#10 2014-03-21 10:54:45

Re: Expedient way to move around the Linux CLI

#11 2014-03-22 21:45:48

Re: Expedient way to move around the Linux CLI

#12 2014-03-28 21:41:26

Re: Expedient way to move around the Linux CLI

#13 2014-03-29 05:05:35

Re: Expedient way to move around the Linux CLI

#14 2014-03-29 07:26:47

Re: Expedient way to move around the Linux CLI

#15 2014-03-29 18:33:36

Re: Expedient way to move around the Linux CLI

#16 2014-03-29 19:05:03

Re: Expedient way to move around the Linux CLI

#17 2014-03-29 19:10:10

Re: Expedient way to move around the Linux CLI

#18 2014-03-29 19:33:32

Re: Expedient way to move around the Linux CLI

#19 2014-03-29 19:34:50

Re: Expedient way to move around the Linux CLI

#20 2014-03-29 19:35:22

Re: Expedient way to move around the Linux CLI

#21 2014-03-29 19:37:57

Re: Expedient way to move around the Linux CLI

#22 2014-03-29 19:46:30

Re: Expedient way to move around the Linux CLI

#23 2014-03-29 21:10:54

Re: Expedient way to move around the Linux CLI

#24 2014-03-30 01:20:36

Re: Expedient way to move around the Linux CLI

#25 2014-03-30 03:24:53

Re: Expedient way to move around the Linux CLI

Board footer