My configuration includes information about staged(stagedstr) and unstaged(unstaged), displayed as “:S” and “:U” respectively:

autoload -Uz vcs_info
setopt promptsubst

zstyle ':vcs_info:*' check-for-changes true
zstyle ':vcs_info:*' stagedstr ':S'
zstyle ':vcs_info:*' unstagedstr ':U'
zstyle ':vcs_info:*' enable git hg
zstyle ':vcs_info:*' actionformats \
  '%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{3}%c%u|%F{1}%a%F{5}]%f '
zstyle ':vcs_info:*' formats       \
  '%F{5}(%f%s%F{5})%F{3}-%F{5}[%F{2}%b%F{5}%c%u]%f '

precmd() {
    vcs_info
}

RPROMPT='${vcs_info_msg_0_}[%T on %D]'

And here is how it looks (original):

A few things I struggled with, basically because I didn’t read the docs:

• You must set setopt promptsubst otherwise, ${vcs_info_msg_0_} is not going to be recognized.
• If you use %c or %u for change tracking, you should set to true check-for-changes (see code).
• Don’t forget about precmd()

Here are other examples: 1, 2

Enjoy

Original from http://xach.livejournal.com/296022.html

Whitespace sensitivity – Include ‘-w’ in ‘ediff-diff-options’.

So, I did a quick (setq...) but it didn’t work. After some googling, I came across this message. Seems like you have to make the changes using customize, otherwise it won’t work. So, if somebody else is having this problem, making the changes using customize (M-x customize-group RET ediff-diff) is the way to go.

From the eclipse perspective, there are plugins that simulate emacs keybindings, but I was never truly comfortable using them. Emacs is more than its keybindings. From the emacs perspective, there is the Java Development Environment for Emacs, or JDEE, but it doesn’t seem to be under active development; while it gained some momentum last year, their devel mailing list statistics show that only 11 messages have been send this year.

Then, I found Eclim, and as stated in their homepage: “The primary goal of eclim is to bring Eclipse functionality to the Vim editor. The initial goal was to provide Eclipse’s java functionality in vim, but support for various other languages… have been added and several more are planned.”

Basically, eclim has two parts, a java plugin that hooks into eclipse and exposes some of its functionality, and a VIM plugin. I like this approach. For a lot of people, emacs and vim are almost their natural environment, so making other tools provide extra functionality to them instead of trying to simulate the editor experience is the way to go.

For emacs, you have the Emacs Eclim project, hosted in github, which is the equivalent of the vim plugin. To use it, first install eclim, then download emacs-eclim from github, and finally add to you .emacs:

(add-to-list 'load-path (expand-file-name "/path/to/emacs-eclim/"))
(add-to-list 'load-path (expand-file-name "/path/to/emacs-eclim/vendor"))
(require 'eclim)

(setq eclim-auto-save t) ;; very important
(global-eclim-mode)

And now you are ready to go. The main feature missing in emacs eclim is doc searching, but AFAIK it’s provided by eclim, so it shouldn’t be too hard to implement the emacs part. Emacs eclim is under active development.

As a side note, if you want to do some Android development, I deeply recommend you to use IntelliJ. It has built-in Android support and works great. A month ago I tried to setup Eclipse’s android plugin and it was extremely frustrating. So, try IntelliJ if you want to experiment a different IDE and can withstand its no so pretty interface. (They have a community edition which is OpenSource, check it here).

If it is soooo good, why did I change it? well, I had some stability issues with it for a while (which ended been problems with Xorg, so it’s not their fault). Also, there are two features I don’t like. First, while bringing lots of flexibility, the config file is usually “cluttered” with code you don’t want to see. As I said, it seems like half of the WM is written in the config file, so you have tons of code defining the default WM behaviour and, after a while, you stop feeling like you are configuring the WM and start feeling that you are patching it. Every new release was an exercise of retrofitting your changes to the new default config file, otherwise you may lose some of the new features bring by the update. Awful. Second, lua. The config file and other parts of the WM are written in lua, which is not part of my personal preferences. I may be biased by my lack of knowledge about programming in lua, or maybe not, even Julien Danjou, the original author of Awesome, has ranted about it.

So, one day I decided to try other tiling WM. I installed stumpwm, i3, ratpoison, and xmonad. I never got pass the first one.

StumpWM is not the most stable WM out there, nor the most lightweight (it requires a CL interpreter), and it has neither a large nor extremely active community (its latest stable release is from March 2010, but the repository is active so you get your code from there). Now, to the good stuff.

StumpWM is tiling, but has some support for floating “groups” (desktops). AFAIK, it doesn’t have the advance automatic tiling layouts of Awesome, so its window placement capabilities are more closely related to GNU Screen or Emacs Frames, but given that I usually have a single app in full-screen mode it doesn’t matter. What really make StumpWM shine is that it’s written in Common-Lisp. It’s at least as configurable as awesome while keeping your configuration file clean. Being Common-lisp, you can write a new function and it will override the previous one (not as powerful as advices in emacs, but close enough). If you don’t know lisp, learning it is very easy. Once you passed the feeling of “why there are so many parenthesis?” and get use to the prefix (+ 3 2) syntax, you will see it’s pure genius.

If you want to give it a try, the best way to do it is following the ArchLinux wiki. Also, take a look at the awesome Stumpwm experience video.

http://www.youtube.com/watch?v=iGy9YH9tY88

I just needed to recompile it with +truetype as useflag. Hope this is useful to somebody else.

I have to admit that I do store some important information there, but I did my homework and encrypted it using pgp before uploading. Still, I’m taking the next step: I’ve switched to SpiderOak as my main remote storage/sync service, given that they do client-side encryption, so my data is safe(r). My Dropbox account is going to store anything which I have absolutely problem sharing.

If you read the Beamer user guide (PDF), it mentions modifying the heading to include the handout option, and to add an additional command specify the number of pages per page:

\documentclass[handout]{beamer}
% Other packages...
\pgfpagesuselayout{2 on 1}[a4paper,border shrink=5mm]

This produced a PDF with two slides per page (or more depending on what you want), but no notes space anywhere. Some further googling showed a TeX StackExchange entry with the solution, which pointed to this blog post by Guido Diepen.

What you need to do is download this package, and add it to your document preamble, and then modify the pgfpagesuselayout (to include with notes) command like this:

% add this package to your directory (not in CTAN!)
% download it from the link above.
\usepackage{handoutWithNotes}

\pgfpagesuselayout{2 on 1 with notes}[a4paper,border shrink=5mm]

Check out the original blog post by Guido to see examples and more options. Enjoy!

P.d. I forgotted to add with notes the first time, and I didn’t realized that right away. So be aware in case you are as sloppy as I am.

\begin{frame}
  \begin{small}
    \phantomsection
    \addcontentsline{toc}{section}{\bibname}
    \bibliographystyle{plain}
    \bibliography{bibliography}
  \end{small}
\end{frame}
\end{document}

I didn’t like the size of the entries, and the fact that they only spawn a single frame, so only a few entries were visible. Some Googling and I came with an improved solution:

\begin{frame}[shrink=5,allowframebreaks]
  \begin{small}
    \phantomsection
    \addcontentsline{toc}{section}{\bibname}
    \bibliographystyle{plain}
    \bibliography{bibliography}
  \end{small}
\end{frame}
\end{document}

Then I realized that the citations weren’t included in the bibliography!. Sure, the entries were there but, which one was the “13″? Bibtex showed some nice, and pretty useless, icons instead of the citations. Further Googling unveiled an answer (may be others), using natbib+bibtex (here is a quick reference to natbib):

% before \begin{document}
\usepackage[square]{natbib}
\newcommand{\newblock}{}

Enjoy.