Good article. Rather than aliasing `cd ../.." etc. I've got this function in my setup:
up () {
local x=''
for i in $(seq ${1:-1})
do
x="$x../"
done
cd $x
}
This lets me do up 4 to go up 4 directories.
this post was submitted on 24 Nov 2023
73 points (95.1% liked)
Linux
48247 readers
493 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You could also do a "up" for one up "upp" for 2 and "upppp" for 4 because of fun
True. That is something that could be done.
Oh I really like this. I never had an alias for this since I need to do multiple backwards cds very rarely, but I might just copy this
I have the zsh option autopushd set which calls pushd in interactive shells for every cd, that way 90% of the time when I want to go back up to another path I can just use popd
Go for it. I've been using it for years without a problem.
Holy shit
I use Fish and have keybinds for previous and next directory, 99% of the time when going up in a directory it's to (one of) the previous directory/ies I was in
Look into zoxide.
z direc
Will take you to the most used directory starting with "direc" eg "/home/me/random/directory"
I've tried things like that before but never got on with them. I found when I had many projects with similar directory structures it was easy to end up in the wrong place and took more thought to get to the right place than just cding
The dir's are the same names or similar? A few extra key strokes to get the fullname should be easier than cd'ing back and forth.
There's also z foo "space" "tab" as per docs to get interactive list for matches.
But, just a suggestion!
What I use to automatically extend stuff like ls .... to ls ../../../..
function expand-dots() {
local MATCH
if [[ $LBUFFER =~ '(^| )\.\.\.+' ]]; then
LBUFFER=$LBUFFER:fs%\.\.\.%../..%
fi
}
function expand-dots-then-expand-or-complete() {
zle expand-dots
zle expand-or-complete
}
function expand-dots-then-accept-line() {
zle expand-dots
zle accept-line
}
zle -N expand-dots
zle -N expand-dots-then-expand-or-complete
zle -N expand-dots-then-accept-line
bindkey '^I' expand-dots-then-expand-or-complete
bindkey '^M' expand-dots-then-accept-line
(for zsh)
Is there a community for people that actually know and use linux or is this just like 'programmer'humor where morons can't exit vim, use a debugger, or RTFM?
How would you define "knowing" and "using" linux? Many people here don't use Linux professionally and only on the desktop, so they probably aren't too familiar with all the features of different cli programs.
Reading a blog post is more accessible than reading a man page. I didn't know cd -, so reading the post was worth it I'd say.
Reading a blog post is more accessible than reading a man page.
I don't agree with that assessment at all. People should learn to read manpages, instead of being spoon-fed pieces of manpages in inferior form.
Any program should have a man page, even if it only lists all options. My point is that a blog post helps some people to learn about a program. For example a post often highlights the most important options of a software.
manpages aren't guides though - they don't help much in learning new tools, especially complicated ones. They're comprehensive references, some can literally span hundreds of pages. Useful when you know what you're doing and what you're looking for, not great for learning new tools.
Some of these tips are dangerous. You generally don't want cause insensitivity in your shell. Also, ls should never be used as a subshell to find files as a part of commands.
Thanks for these tips.
Great stuff! Didn't know about lf
I use that r function regularly to go to the git project root. But I call it gtop. I mostly use that and zoxide to get around.