At present, gist-* obey the default directory being a tramp pathname and use all applications and configuration from the remote host. I can see some cases where that might be useful, but it seems like the common case would be using the local applications/configuration to post the gist, regardless of the machine the buffer it's from is on would be the common case.
Providing at least an option, defaulting whichever way, would satisfy both cases.
At present,
gist-*obey the default directory being a tramp pathname and use all applications and configuration from the remote host. I can see some cases where that might be useful, but it seems like the common case would be using the local applications/configuration to post the gist, regardless of the machine the buffer it's from is on would be the common case.Providing at least an option, defaulting whichever way, would satisfy both cases.