123
What's the point of terminal file managers (mc, ranger, nnn, etc)?
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Oct 2023
123 points (90.2% liked)
Linux
47760 readers
1481 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
Well, for schoolwork, I mount my Google Drive storage onto my ~/googledrive directory (where I store all of my schoolwork) and usually use mc to navigate. Although, I am quite comfortable with the terminal. Its just that I have a lot of subfolders and going to a specific subfolder in mc is usually faster than doing "cd ~/googledrive/subfolder-with-long-path".
Have you looked into Autojump? It works with bash and zsh and is even faster than using a terminal file manager if you've already visited the directory before
I still kinda don't see the point. Like, typing cd /usr/share/xsessions is not that much slower than j xsessions or however it would work. Also, how does it actually work? What if I visit both $HOME/backgrounds and /usr/share/backgrounds very often?
It's for when you have really nested directories. It happens especially when you're working in a file space used by others. I used to have a folder I would often reach called /media/nas/documents/personal/school/foo/bar/foobar2001/projectA
I ended up going back to that project so many times, I could just do
j projectAand get there from anywhere. "Why not use a symlink?" I hear you say. Well it's because I often have to go to projectB or another which was in another really nested dir. Or I needed to jump to another directory which was equally as nested, and only had to use it frequently for like a week or so. Making and deleting symlinks all the time wasn't practical. Not to mention some software doesn't properly follow symlinksWhat I usually do for that sort of thing is define some variables that go to my most visited.
Aliases? That could work quite well imo, and I have some to launch my most frequently opened config files, such as my qtile config