...-remote variables differ from local variants

[AlexTalker]

I've been trying to get a grasp at Emacs power by using Doom Emacs and specifically TRAMP-related functionality.

I've noticed that attempting to issue project build while over TRAMP SSH|Podman session resulted in an error due to rustic-cargo-bin-remote defaulted to rustup-based version, so while looking around the code for the source of the value I've noticed the following snippet:

(defcustom rustic-compile-command (purecopy "cargo build")
  "Default command for rust compilation."
  :type 'string
  :group 'rustic-compilation)

(defcustom rustic-compile-command-remote "~/.cargo/bin/cargo"
  "Default command for remote rust compilation."
  :type 'string
  :group 'rustic-compilation)

(defun rustic-compile-command ()
  (if (file-remote-p (or (buffer-file-name) ""))
      rustic-compile-command-remote
    rustic-compile-command))

I'm not yet too familiar with Emacs Lisp but in general it appears that remote command is missing build argument in expectation for the user to do not forget to add it in for rustic-compile command to have a meaningful impact. In addition, it is unclear why rustic-compile-command invokes purecopy but one below doesn't.

I've not inspected all the similar functionality as it is quite late, which is why the issue title is a bit generic.

In addition, is there a possibility to hook onto TRAMP opening a connection in order to determine the values for the variables appropriate for remote system with respect to remote PATH, for example by calling which? =)