> You could byte-compile your customization : it'll warn you about most > potential problems (change in the number of arguments and non-existing names).
I'm sorry if my post was not clear enough. But I've NEVER had problem knowing which functions have changed their name. The problem I had was that I didn't have an effective way to QUICKLY figure out the new names of those function. York On Thu, Jul 16, 2015 at 1:48 AM, Nicolas Richard <youngf...@members.fsf.org> wrote: > York Zhao <gtdplatf...@gmail.com> writes: > >> Thanks Kyle for the tip. However, because in my customization I've called or >> bound a lot of Magit functions / commands, it would be nice if there's a way >> to >> quickly figure out the new names of those functions / commands I've used. >> Without a documentation for changed function / command names, I have to use >> "git >> log -G" which can be pretty time consuming to find out the information I need >> from a lot of commits returned by "git log -G". > > You could byte-compile your customization : it'll warn you about most > potential problems (change in the number of arguments and non-existing > names). Then you still have to find the new names, but at least you do > it only once. > > -- > Nico > > -- > 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 magit+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 magit+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
