Many developers are forced to develop on small screens: Travelling, Coworking spaces, changing project locations, you name it. But what can you do to improve your workflow if you are bound to a small screen? This presentation tries to give some answers and suggestions.
28. Browser:
Google Chrome
• ⇧⌘F opens full screen
• ⌘L
• puts the cursor in the address bar
• shows tabs, bookmarks etc.
• ⌥⌘← and ⌥⌘→ switches tabs
29. Terminal: iterm2
• (in early alpha, but „works for me“)
• ⌘-enter switches to full screen
• hold ⌘ for a second to see the tabs
30. Editor: MacVim, vim
• Choose an editor without a toolbar
• MacVim supports full screen
• Terminal editors support full screen via
iterm2
• Textmate isn‘t bad, either, but has
annoyances (e.g. drawer)
31. What are the problems
when developing on
small screens?
32. Problems on small
screens
• Finding the information you need
• Interacting with a specific process
➡Switching between applications
45. Conclusion
• Switch to a command line editor
• Make the terminal your comfy place
➡Avoid confusion while switching between
your main applications (overshooting)
57. Easier process
switching
• CTRL-Z suspends processes
• CTRL-F alternates between
suspended processes (if you set it up)
58. Easier process
switching (zsh)
• Alternate between backgrounded
processes with CTRL-F
• bindkey -s '^f' "fg %-n"
• export HISTIGNORE="fg*"
• fg to bring up the last bg process
• YOU WILL HAVEdoesn‘t work with ruby) !!!
(the preexec part
TO FIX oh-my-zsh
67. tmux
• terminal multiplexer
• Very powerful
• Does not support OSX clipboard
• (though there is patch for the 1.3 version)
68.
69. iterm2
• Very easy to use
• ⌘D vertical split
• ⌘⇧D horizontal split
• ⌥⌘←/→/↑/↓ switches between panes
• Touchpad scrolling
• Not as powerful as tmux (no rearranging of
panes etc.)
70.
71. Take-aways for all small
screeners:
• Switch to full screen
• Lern you some terminal-fu
• Try a command line editor
• Some stuff is also useful for big screens,
server admin etc.