On 4/23/11 11:30 PM, Andrea Crotti wrote:
Ah yes I moved around the "---" in the wrong position.
From what I gathered the best emacs-git way is for example
- git format-patch -1
- git send-mail --to [email protected] --compose<patch_file>
which will popup my emacs again and let me compose the message, but I'm
not really sure that's the smartest way.
I use
git send-email [--compose] -1
having the to set in the .git/config, --compose it pops the editor and
when needed, used usually only for large patchsets.
What do you mean for whitespace stripping?
stripping trailing whitespace (what color git diff signals mostly)
"
$
int foo(bar) $
{$
...
} $
"
gets
"
$
int foo(bar)$
{$
...
}$
"
Those spaces are the default indentation of elisp code, which normally
nobody changes and it's quite standard.
I didn't mean in the code, I mean enabling it so people using emacs will
get their file whitespace clean on save, (I already posted my vimrc for
that)
About the emacs settings I thing some more magic can be made to
- configure cedet and semantic for ffmpeg (or at worst some tag automatism)
- configure the changelog style
- define some functions to run easily tests
- and everything else you can imagine ;)
I know =), the best probably would be adding an autotemplate so we
create new files with the default headers automagically (hadn't made
that for vim yet)
Thank you for the support ^^
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
