Non-Console Dev Tools

Linux

  • gedit (Gnome) and kate (KDE) are both decent editors. ( Gedit has a nice dark colour scheme you can pick to use. )
  • SciTE light tabbed editor with nice coding features
  • Meld and Kompare are decent diff tools
  • KDESvn is what I used to use to sync with SVN in KDE.

Windows

See Also

You can also use http://qt.nokia.com/products/developer-tools Qt Creator for Mixxx development by creating a Qt project file for the source files. You can do this by running 'qmake -project' under mixxx/src. When using the created project file, you are able to use Creators editing features such as following symbols (F2) and switching between code and header files (F4). When compiling you will still have to resort to SCons as th project file will not resolve the dependencies.

Console Dev Tools

On Ubuntu Linux, G uses:

grep (w/ color)

export GREP_COLOR='1;33'
export GREP_OPTIONS=--color=auto

colordiff

alias svndiff='(echo "Running SVN diff (your changes vs. the repo)..." && (svn -x -w diff|colordiff))|less -R'
alias svnbasediff='(echo "Running SVN diff against BASE:HEAD (changes in the repo since last \"svn update\")..." && (svn diff -x -w -rBASE:HEAD|colordiff))|less -R'
  • diff -y with automatic adjustment for term width.
alias ydiff='y_diff'
function y_diff() {
  diff --width=${COLUMNS} -b -y "$1" "$2" | colordiff | less -R
}

colormake and colorgcc

### Color GCC
if [ -z "`which colorgcc`" ]; then
  echo Installing ColorGCC ...
  sudo aptitude install colorgcc
fi
if [ ! -z "`which colorgcc`" ]; then
  export CC="colorgcc"
  alias gcc='colorgcc'
  for C in `grep /usr/bin /etc/colorgcc/colorgccrc | sed -e 's/# //' -e 's/:.*//'`; do
    if [ ! -e /usr/local/bin/${C} ]; then
      echo "Installing colorgcc wrapper in /usr/local/bin for ${C}... "
      sudo ln -s /usr/bin/colorgcc /usr/local/bin/${C}
    fi
  done
fi
### Color Make
if [ -z "`which colormake`" ]; then
  echo Installing ColorMake ...
  sudo aptitude install colormake
fi
if [ ! -z "`which colormake`" ]; then
  alias make='colormake'
  if [ ! -e /usr/local/bin/make ]; then
    sudo ln -s /usr/bin/colormake /usr/local/bin/make
  fi
fi

source-highlight

alias vs="view_source"
function view_source {
  lang_def=""
  case "`basename $1`" in
    SConscript|SConstruct) lang_def=python.lang;;
    .bashrc|.bashrc-extra) lang_def=sh.lang;;
    # *) lang_def=cpp;;
  esac
  if [ ! -z "${lang_def}" ]; then lang_def="--lang-def=${lang_def}"; fi

  echo -e "\033]0;view-source: $1\007\c"
  source-highlight ${lang_def} --out-format=esc --output=STDOUT "$1" 2>/dev/null | less -RN
}

Nano editor

  • Syntax color highlighting .nanorc file, you may have to run dos2unix on it.
  • Usage:
    • nano somefile.cpp:326:error: some compiler error message
alias nano='smart_nano'
## Smart nano jumps to a line number when you give it filename:nnn where nnn is the line number (like compile warnings/errors)
function smart_nano() {
  if [ -z "$(echo \"$@\" | egrep [a-zA-Z0-9]:[0-9]+)" ]; then
    /usr/bin/nano -w -c "$@"
    return
  fi
  unset args
  echo
  while (( "$#" )); do
    if [ ! -z "${1}" ] && [ ! -z "`echo ${1}|cut -d: -f2|grep -e '^[0-9]*$'`" ]; then
      args[${#args[@]}]=+$(echo ${1}|cut -d: -f2|grep -e '^[0-9]*$') # Line Number Offset
      args[${#args[@]}]=$(echo ${1}|cut -d: -f1) # File Name
    elif [ -f "${1}" ]; then
      args[${#args[@]}]=$1
    else
      echo "Nano could not find: $1"; sleep .5
    fi
    shift
  done
  /usr/bin/nano -w -c "${args[@]}"
}
 
developer_tools.txt · Last modified: 2010/02/07 13:32 by elysion
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki