with (setq magit-emacsclient-executable nil) the magit buffer isn't updated after commit is done.
On Fri, Aug 30, 2013 at 2:50 PM, Rémi Vanicat <[email protected]>wrote: > Marius Vollmer <[email protected]> writes: > > > Jonas Bernoulli <[email protected]> writes: > > > >> Some of the drawbacks of the new workflow will vanish after making > overdue > >> changes elsewhere. But some drawbacks are inherent to the use of > >> emacsclient. > > > > Using emacsclient strikes me as wrong. If I understand things right > > from reading this list, you want Git to prepare the content of the > > commit message. Couldn't that be done by piping "git commit --dry-run" > > into the buffer? > > git commit --dry-run don't run git's pre-commit-hook nor > prepare-commit-msg: > > % ln -s /bin/false .git/hooks/pre-commit > % git commit > % git commit --dry-run > # Sur la branche master > # Modifications qui seront validées : > [...] > > You can see that running git commit just fail because the pre-commit > failed, but dry-run do print its result. > > Note also that if emacsclient bother you so much, there is already what > is needed for magit to not run it: > > (setq magit-emacsclient-executable nil) > > -- > Rémi Vanicat > > -- > > --- > You received this message because you are subscribed to the Google Groups > "magit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott -- --- You received this message because you are subscribed to the Google Groups "magit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
