Various tips how to increase your productivity (esp. in Linux).

Who uses which editor and is willing to provide a mini-training for new users (show config, favorite macros, highlighters etc.).
Feel free to add your name and editor.

• vim: Ondřej Bojar, Ruda Rosa, Milan Straka (C++ completion, Python completion, asynchronous make), …
• emacs: ?
• atom: Martin Popel

• Use Bash auto-completion (source /etc/bash_completion). Some tools have plugins, e.g. many Perl tools.
• export HISTCONTROL=ignoreboth results in bash history ignoring duplicate entries and entries starting with a space.

• Ondřej Bojar prefers to store the history in each directory in .history-bojar. See /home/bojar/diplomka/granty/cracker-2015/mtm-2016-organization/accounts-mtm16/bash-profile-for-ufal-accounts
  • Note that this creates the “.history-your-name” wherever you have write access and some ÚFALers are not happy with this. In addition everyone sees what you did (this may be useful, but be careful).
• Ondřej Dušek (/home/odusek/.bashrc) uses a variant more friendly to others, which saves the histories in his home (but does not handle renamed directories):

  if [ -z "$USER" ]; then
      export USER=`whoami`
  fi
  
  # Store all history with times and directories
  function store_history () {  
      history 1 | awk '($2 !~ "^[mr]?cd[0-9a-z]?$") {$1="_T="strftime("%Y%m%d_%H:%M:%S_") PROCINFO["ppid"] "_PWD="  ENVIRON["PWD"] "\t"; $2=gensub("^_T=[-_0-9:]*[ \t]* *", "", 1, $2); $2=gensub("^_P=[^ \t]* *", "", 1, $2); print;}' >> ~/.history-all-$USER
  }
  export PROMPT_COMMAND="store_history"
  
  # Grep history
  function dhist (){
      DIR=`pwd`
      command grep "_PWD=$DIR"$'\t'".*$@" ~/.history-all-$USER | tail -n 30
  }
  
  function hist (){    
      if [ "$#" -eq 0 ]; then
          tail -n 30 ~/.history-all-$USER
      else
          command grep "$@" ~/.history-all-$USER | tail -n 30
      fi
  }

• bash-git-prompt shows e.g. the current branch and status. Martin Popel prefers to configure it (in bashrc) with

  export GIT_PS1_SHOWDIRTYSTATE=1
  export GIT_PS1_SHOWSTASHSTATE=1
  export PS1='[\t]\[\033[2;31m\]\h:\W\[\033[01;95m\]$(__git_ps1 "(%s)")\[\033[2;31m\]>\[\033[0m\] '

• tig text-mode gitk but better
• read https://guides.github.com/, understand GitHub flow, check GitHub training
• learn GitHub keyboard shortcuts, esp. “y” for permalink to a given line (line range) in source codes

• When using Perl at ÚFAL, we recommend using Perlbrew with shared perl interpreters (different versions) and shared Perl modules (which otherwise take several hours to install and 6GB).
• See Python for using Python at ÚFAL.
• See remote access, esp. for byobu and mosh.
• You should not turn off Linux workstations at ÚFAL, unless really needed (or agreed with it@ufal). In that case, try the standard ways, and if they do not work, try Ctrl+Alt+SysRq+[R,E,I,S,U,B] rather than plug out power cable. Mnemonics: “Reboot Even If System Utterly Broken”, see http://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
• Ondřej Bojar has implemented many Text utils, which he likes to use in his scripts and advises his students to do so as well.
  • The web versions of the text utils are often older than the ones in /home/bojar/tools/vimtext and /home/bojar/tools/shell
• latexmk can be used with -pdf -pvc, so whenever you save a tex file, the corresponding pdf will be regenerated (and your pdf viewer will refresh). Other useful options are -interaction=nonstopmode -synctex=1, see e.g. synctex
• pdftk for merging and splitting pdf files (and much more) from the command line