How can I go about using the tty only on my system
I wanted to have a separate laptop where I only use the terminal for my use cases. At the moment I am somewhat confident using the terminal, but I think limiting myself to tty only would build my confidence even more. Any tips?
EDIT: I am already using nvim and I already have installed a minimal distro (Arch). I just need advice on how to actually run this system effectively.
Just don't install a DE? Am I missing something?
Well yeah, but I want to know any tips on doing it effectively. If I just "don't install a DE" I wouldn't know where to go from there.
If I'm reading your post right, you basically want a fully functional system that is console only (no GUI), right? So when you go to install, just simply skip installing the desktop environment/window manager.
That, or you can set it up to where your system boots to the console, and you can activate the DE/WM if you want to (like startx for X11). Each environment is different, but I think it's removing the line for starting the DE/WM from either systemctl or maybe a hook, I forget.
I'll just dump this here.
https://github.com/rust-unofficial/awesome-rust https://zaiste.net/posts/shell-commands-rust/
alternatives
GUI alternatives
Task Management:
Services:
File Manager:
Login Manager:
Others:
ease of use
specialist tools
If you're serious about sticking to the terminal, it's probably worth learning a terminal text editor like emacs or vim. Once you get the hang of them, you can be much more productive compared to something like nano.
I think it's also worth learning about job control and/or terminal multiplexers, but I've yet to fully understand them myself.
How can you be more productive in vim compared to nano?
Serious question.
vim is more then simple file editing.
:global, %s/, etc. which form text manipulation language (from editor ed, I guess)args & argsdo (multi-file editing)ctrl_X completion modesromainl (awesome community member)vim for one-time tasks at work. When people are proposing to script something, I open buffers, normalize the data and filter the results. I think in vim and I would very, very much recommend it, if you work with data or are a dev.
vim has better default keybindings/commands that allow for less movement of your hands. Nowadays, in reasonably current versions of nano, that's mostly it. The main difference is nano is somewhat usable but extremely inefficient unless you learn it, while vim forces you to learn it to get anything done at all, which also pushes people to spend a bit of time learning it in general.
If you're sure of the numbers you're using, vim's ability to repeat commands is also helpful. In practice I find that it's really hard to make use of them beyond low numbers, where nano can still achieve things in similar amounts of keypresses. Eg something to delete 3 words like <escape>3dwi can be done similar with a sequence like Alt-A ^→ ^→ ^→ ^K in nano. Make it 20 words and nano is going to be a lot slower, but that's quite an uncommon action.
But the practice is that nano users don't spend time learning any of that and just hold delete until the words are gone, which takes forever. Everyone that can do basics in vim quickly learns that you can dw words away and make it 3dw to delete 3 of them. The default, easiest to use & access tool for any given situation gets blamed not just for its flaws, but also for the users that don't want to spend time learning any tool.
VIM for the win. I really enjoy the built in file browser accessed by the command :explore
I also code in go frequently and go-fmt and go-lint etc work flawlessly. You can use whatever LSP you want so you get your code tips and autosuggestion etc.
The tabs and split window functions are nice too. Plus if you learn Vi well it's on almost every system in existence. Nano not so much
Easy. Just learn to use it and it is already there.
With nano, you work with that letter where your cursor is at the moment. This is convenient, but limited.
With vim, you can also work with a word, or the whole line, or part of the line, or a section, or the whole file (or many files if you use the shell extension) and it goes all with the same ease.
Vim also allows you to keep your hands in place on the letters on your keyboard all the time. No need to move the hands around, grabbing the mouse and back, or the arrow keys, and thus search for the correct position for your hand every few seconds - which costs time and focus.
Tbh I think it's just a matter of preference and some people are being elitist about it or overestimate the importance of it.
Try running this:
vimtutor
If you are already aware of hjkl, skip to the part where you learn motions:
/motion
Then look up surround (ysw is usually the command to surround a word, ys3w the next 3 words, etc)
It's pretty neat.
why use big app when nano does trick?
Julia Evans recently did a thing about job control here. Nothing yet on multiplexers though
The most important thing about terminal multiplexers is that you have to atart them with the terminal command.
e.g. yourterminal --startcommand=tmux.
Get the server version of whatever your favorite distro is. Nothing but terminal.
I built a console-only laptop once for financial reasons. I wanted something to travel with on a trip and was donated a laptop that, I think 20 MB of RAM after I upgraded it. I was able to run vim, perl and mutt was very tolerable performance.
I don't think there's really special tips. Pick a goal of some tasks to accomplish. Work towards them, discover the rough edges and find solutions for them. If you install everyone else's favorite CLI apps, you can end up more than you need.
All that said, if I had the memory to run a GUI, I probably would have do so. But I wasn't going to have a lot of time for web browsing and other laptop on that trip anyway.
I read this thinking you meant you wanted to only use a serial terminal, which sounds like a really neat project: they're cool hardware and would certainly be a unique way to interact with modern computing.
But uh, yeah no that's probably not what you meant and I've spent WAY too much time dealing with retro stuff lately.
What are these serial terminals you're talking about?
Back in the super early era of computers, they were stupidly expensive. One solution was to hook up a lot of people to a single computer via a computer terminal, which were much cheaper.
Basically it would allow you to deploy a ton of monitors and keyboards to access a single computer relatively cheaply, and UNIX was the OS that (mostly) was used for this.
You noticed that your console session is called 'TTY-a-number'. Well, TTY stands for 'teletypewriter' which was the very first incarnation of this, and was what was in use when the name of the console was a made, and it's just... never been changed, though tty devices and their later serial consoles are quite dead as far as tech goes.
Enabling a serial terminal in Linux is a one-line change, and you can then use any terminal emulator you'd want to connect over it, but eh, it's a pretty dead technology and nobody uses that at this point.
Since I seem to be dumping useless retro facts all over the place: you could do this with DOS, and Digital Research released Concurrent DOS to allow multi-tasking, multi-user access to a DOS system. If you wanted to fiddle with that in the modern era, you'd want the Novell Multiuser DOS rebrand, since it supports vt100 emulation and thus can be used with basically any serial terminal app unlike the previous versions which emulated specific HP and IBM serial terminals.
If you haven't set up this laptop yet, then I'd suggest installing a server-oriented distro like Debian, AlmaLinux, or Ubuntu Server. Those have minimal install options that come without a desktop environment installed, as most servers do not need one. If you'd like to make the install harder for yourself, this might be a good excuse to give Arch Linux or Gentoo a try, as those have the option of a fully manual install. If you'd like, you can install a desktop environment afterwards using the package manager.
If you already have a Linux with a graphical desktop installed, you can configure the system not to automatically start it with sudo systemctl set-default multi-user.target. (Do not do this on your main device!) You can re-enable it with sudo systemctl set-default graphical.target.
Regardless, you can then start a graphical session using startx, or whatever command is more appropriate for your desktop environment (gnome-session to start GNOME on Wayland, startplasma-wayland to start KDE Plasma), or by sudo systemctl starting your login screen manager (sddm, gdm, lightdm, etc).
I've found sc-im to be very useful, but I'm still a little new to it. Visidata is another one that seems to be a lot more powerful than sc-im.
I have used sc-im a few times, I like the simplicity and vim shortcuts.
Thanks for mentioning visidata, I'll install it.
csv-mode on emacs
If you want to mess around with scripting instead of an editor I would recommend Awk- it works great for CSV files and is really powerful. Usually you can use -F, to separate using commas, but for full CSV support (with potential quoted commas) you need to use something like -vFPAT='[^,]*|"[^"]*"' (which isn't POSIX compliant but works with gawk)
VisiData may do what you want.
Almost every CLI only version of Linux is designed to be a server.
Servers assume you have no WiFi. There will not be an option to set it up during first-time setup, you will have to do it manually.
You are doing this on a laptop which generally assumes you will be using WiFi.
You will have to set up wpa_supplicant during install via command line outside of the automated setup.
Further, if your WiFi drivers have any non-free proprietary code in them, you will need to manually install drivers for them like you would normally. Once again, best to do during setup, if possible.
If you have the option of connecting directly with ethernet during setup, you can sort of wiggle past it and set it up after, but I've personally found that the servers prefer it if you do it during setup (ie. fewer weird networking issues).
As others have said, you could also just not install a desktop environment in a normal version of Linux instead of going for a server version, as another way to avoid this issue.
Source: personal experience using server version of Linux on laptop
This is not true.
Especially nowadays network manager handles all that stuff. Nmcli or nmtui make it beyond easy and I haven’t messed with wpa_supplicant in about ten years.
There is some truth to it. If you are installing a server distro it may not come with nmcli by default. Maybe it will. But good to think about
Like others said, you can try installing Arch manually (not with the install script). You get the hang of the terminal and you get to see a bit more of how Linux works under the hood. The wiki is your friend, spend some time reading it!
I actually am using a manual Arch install. What i meant by gaining confidence is completely abandoning xorg and using the tty only.
Look into terminal multiplexers like screen or tmux, they are a sort of "window" system for tty.
There are text-only browsers but I'm not sure they'll be usable on today's websites. May want to set your tty to a graphical mode (framebuffer) and use a mixed-mode browser that can render images and some other stuff.
Just go for it! It'll be fun. You will find yourself navigating your digital life (or at least: most of it) at relative ease with less distractions and graphical fuzz you otherwise get.
Getting to know terminal multiplexer (like screen) or vi-keys are crucial skills for anyone who is not afraid from working on "headless" machines!
vi-keys are crucial skills
I can very seriously argue on this one.
What are your use cases?
Messaging, reading, school work, watching anime, music, web browsing (may not be able to do this one nicely though). My use cases are very simple to implement on tty-only I think.
It is possible to watch movie files rendered in ascii with ffmpeg but I wouldn't recommend it. Playing videos any other way requires a graphical interface.
Web browsing is possible with links, w3m and eww-mode on emacs.
You will struggle with school work. Eduroam is hard to connect to using the CLI for example.
Over time your collection of aliases and scripts will grow to make common tasks you do easier.
I disagree on the aliases. I'd recommend using almost none. It builds competence with the commands on all systems even without your special .bashrc. It'll be easier to write scipts and change shells as well.
I use fish abbreviations. Unlike bash/zsh aliases, they expand when you press space or enter. This way you see the original command every time you use the alias, and you can edit as well. This should lighten the concern you have a bit. Your concern is something that sysadmins keep in mind e.g. default vim bindings so you are always comfortable on any server. However for desktop use I don't think leaving the speed and comfort on table is worth it. Most desktop users only use their own systems anyway.
Great list. Customizing the font is definitely a priority. I recommend one of the Terminus fonts. Also zellij multiplexer + helix editor is a great combo that works well in the tty.
One thing to add is that it took me a while to create a decent 16-color theme for helix and vim, and while they're okay by default you can actually get a pretty nice looking IDE if you spend some time tinkering with the colors
+1 for the Terminus + zellij + helix combo
Thanks a lot, I'll definitely try the terminal multiplexers you're talking about. I wondered how you would get different windows in tty.
Byobu provides good abstraction on tmux as well as screen. Allows you to choose keybindings from any of the two.
Well, there's twin.