Live data from Hacker News

Love Your Terminal

blog.andrewhays.net

131–137 of 137 posts

Re: Love Your Terminal

#131

Earlier quoted context omitted.

Actually, applications can control colors in the same way over SSH as they can on a local distro.

So, would my SSH client just map the colors to the closest available one in its' palette? I'm kind of naive - I figured every application run within command line (not terminal) was restricted to a specific 256 palette.

SSH doesn't care about colours. You can use the colours of whatever terminal emulator you're using.

Re: Love Your Terminal

#132
post #24
post #14

Earlier quoted context omitted.

That's actually why I stopped tweaking things to hell and back, losing my config's was too painful. I usually just go for basic colour tweaks these days. It also makes me more portable and productive when I am using a new or someone else's machine.

I used to take this approach. One day I found I had no choice but to remap CapsLock as a second Ctrl key because my little finger was in constant agony otherwise. I've never had a second's trouble from the finger since then, but you should see me try to type on other peoples' computers now. I TEND TO WRITE IN ALL-CAPS A LOT BY ACCIDENT! So for me there's no longer much point in caring about portability, and I have al…

Yea, CapsLock must die and reborn as third Ctrl. Not only because of all caps, but some folks tend to map it to keyboard layout switching only because it gives them LED indication of the language being used. It also makes your keyboard habits more portable, as laptop keyboards have different order of Ctrl and Fn.

Re: Love Your Terminal

#133
post #93

Earlier quoted context omitted.

> A whole extra line above the working prompt? Because it's frequently useful, and thus the tradeoff of a bit of space for simplicity, speed and familiarity is worth it. > If you need that info at any particular moment, make a command. Right, so your prompt is composed of nothing but the hardcoded character `>`? (you obviously don't need the $/# toggle as you can use `whoami`, and you don't need the previous command'…

> Right, so your prompt is composed of nothing but the hardcoded character `>` Hey that's what mine is! Actually it is simply the ')' character. I went from full on prompt-porn to nothing. For the most part this was just to see how much of the prompt I really needed on a daily basis (how often do I really type git branch because I don't know what branch I'm on, how often do I type pwd... stuff like that). Turns out I…

It's an interesting approach! I want to try it in combination with some custom 1-or 2-letter command that would display all this 'prompt-porn' in a single line on demand.

Maybe a 1 or 2-letter indicator on what host I am (e.g. nothing for local, P for production, C for cluster head...), got confused too often.

And, of course, fuzzy completions of zsh.

Re: Love Your Terminal

#134
post #4
post #2

use tmux for multiple screens and ditch that xorg garbage.

Calling Xorg garbage is naive. Even if you only use terminals, and you have to have a framebuffer that supports that native resolution of your screen, you'll find that Xorg is nearly always more performant. If you have issues with X11's security model that's a different story, I'd suggest trying http://wayland.freedesktop.org/

Could someone elaborate how x11/xterm compares to iTerm2? I've been using tmux in iTerm. After reading this discussion, i installed x11 and quartz-wm. Why would I switch to X11 ?

(I do notice that within tmux on iterm, i can use the mouse for selection (using Alt), but the mouse does not work in tmux in xterm.)

Re: Love Your Terminal

#135
post #61

YA post about making fancy prompts - at least its not about how to make a ssh tunnel ;-) Personally I'm never using anything, or adding any fancy setting, if it doesn't serve any direct purpose and/or is not clear, simple and efficient. It's not because I believe "simple" and "efficient" are "cool" or "better". It's just because it's always what made _me_ efficient. I don't lose much time digging configs either, and…

Yup. Everybody and their dog want fancy prompts with lots and lots of info, and I never understood why. Most of the time I don't need any information on my bloody prompt. I just need it to sit there and alert me if something is unusual, maybe, but not to get into my hair otherwise. A couple of years ago I settled on one minimalist prompt, and I've used it ever since. I've even written my own post about fancy prompts[…

I agree. In fact, reading your post, I'd nearly call your prompt fancy, mine just tells me user, and directory, everything else I'll runn a command for.

Re: Love Your Terminal

#136
post #129
post #75

Earlier quoted context omitted.

You could kick that up a notch with something I just threw together. http://npmjs.org/motd :)

If you told me 10 years ago that people would be auto-executing JavaScript upon SSHing to a server.. what have we done.

Haha, true. I do not actually use it at the moment either, I just figured it could be fun.

Re: Love Your Terminal

#137
post #92

Earlier quoted context omitted.

I've run into the same issues. My solution is to reach a sort of balance between portability and usability. My xmodmap + XMonad config is designed to be reproducible on Windows via AutoHotkey and OS X via SizeUp + PCKeyboardHack, that way I'm always in my home environment no matter the OS!

How do you handle window-switching on OSX? I haven't found anything that satisfactorily reproduces the simple mod-j/k keys of xmonad.

I'm not on a Mac at the moment so I can't tell you the exact wording of the preference, but I just set it up through the hotkeys section of the keyboard system preferences pane.

One of the options allows switching window focus, and another allows switching through windows in the active application. There's no option for switching backwards, however. The way I deal with that is to separate any xmonad specific functionality behind a prefix-key submap in my XMonad config.

Any hotkeys that don't take the prefix I can use on any OS, the ones that do are xmoand specific. To me this keeps things nice and organized, while still letting me exploit the xmonad-contrib stuff to the full extent.

For example, instead of mod-j/mod-k, I use the window navigation extension behind the prefix so I get finer control over focus navigation, and this makes xmonad function precisely like tmux just with a different prefix key.

Can you tell I hate context switching?

Post reply on HN