|
I'm a Mac user who half switched to Linux. I have a linux desktop and a Macbook pro running Yosemite. My transition was not terribly difficult. I use ZSH and all the terminal emulators I've tried (Stock Crunchbang, Ubuntu, LXDE on Ras-pi and xfce terminals, along with xterm, and my current favorite urxvt) support emacs keybindings. I'm pretty sure thats a per shell thing though, as I switched ZSH to Vi keybindings with no problem. If you don't use TMUX or Screen, it's not hard to get the normal copy and paste bindings working in any of the emulators I mentioned. With the exception of xterm and urxvt, ctrl-c and ctrl-v usually just work. In xterm and urxvt, you have a little bit of work to do to configure the keybindings, but once that's done, it just works. I like urxvt so much that I'm actually looking to replace iterm2 with something like it. x11.app will run urxvt, but since x is it's own windowing system, it doesn't work with my window management on OS X. Bummer. When I use a desktop environment my favorite desktop environment is xfce, although I do like Elementary OS. However, normally I'm not running a DE. I started my Linux journey dual booting Ubuntu 12.04 and Crunchbang. Eventually, due to some dumb mistake with apt while trying to install a package on Crunchbang (#!), I reinstalled #! and wiped out Ubuntu. (I to have a hatred for Unity) Eventually, I discovered the Awesome window manager. I haven't looked back since. Awesome is completely configurable in Lua, so any key binding you want is possible. I have super+enter (super is the windows key on my keyboard) set to open a terminal, super+w bound to open my browser, and several other keyboard shortcuts like that. Also, Awesome 3+ has a task runner like Alfred built in. I have it bound to Ctrl+space. I'm still using Awesome, but now I'm on Arch. I didn't like how slow Debian stable (the base for #!) updated, so I switched to Manjaro and loved it, but I ran into a problem where I couldn't install a library for some software I wanted. (I probably just didn't have the right repositories configured, but I'll never know.) I'd been considering Arch for a while, so I did a practice install in VirtualBox. It wasn't terribly difficult with the tutorial I found on Youtube. After getting everything working in Virtualbox. I did the install on my computer. I think I've installed Arch on my machine twice now. One of those times I used pacman to generate a list of the packages I had on one install, saved it to a thumb drive, then wrote a python script to parse the list and install the software I was missing. I set the script lose and got in the shower. When I got out, everything was installed. Last thing, the Arch wiki is an invaluable resource for all things Linux. Sure, the package management commands are wrong, but the configuration instructions for things aren't. Even if the files are in a different place, the Arch wiki gives you enough info that you should be able to run find or grep in one of the parent directories and find what you're looking for. https://wiki.archlinux.org/index.php/Main_page |