fix: vterm remote shell + nextcloud

programs/emacs/init.el

@@ -1409,6 +1409,8 @@ create a new one."
                            "-o ControlMaster=auto -o ControlPersist=yes"))
   )
 
+(setq vterm-tramp-shells '(("ssh" "'sh'")))
+
 (use-package diff-hl
   :hook
   ((prog-mode
@@ -1861,23 +1863,110 @@ create a new one."
 (use-package vterm
     :ensure t)
 
-(use-package mmm-mode)
-(setq mmm-global-mode 'maybe)
-(mmm-add-mode-ext-class 'org-mode nil 'org-nix)
-(mmm-add-mode-ext-class 'org-mode nil 'org-elisp)
+(defun sudo-find-file (file-name)
+"Like find file, but opens the file as root."
+(interactive "FSudo Find File: ")
+(let ((tramp-file-name (concat "/sudo::" (expand-file-name file-name))))
+  (find-file tramp-file-name)))
+;;; vterm/config.el -*- lexical-binding: t; -*-
 
-(mmm-add-group
- 'org-nix
- '((nix-src-block
-    :submode nix-mode
-    :face org-block
-    :front "#\\+BEGIN_SRC nix.*\n"
-    :back "#\\+END_SRC")))
+  ;; Original functions overwrites tramp path with a guessed path.
+  ;; However it breaks if remote fqdn/hostname is not resolvale by local machine
+  ;; could also break on port forwarding, multihops,
+  ;; custom protocol such as: docker, vagrant, ...
+  ;; *if* you try to shell-side configure them.
+  ;; Easily testable with vagrant ssh port on localhost.
+  ;; My workflow is to open a tramp dired on / of the remote to get a
+  ;; "foothold" then open vterms from there.
+  (defun vterm--get-directory (path)
+    "[OVERLOADED] Get normalized directory to PATH."
+    (when path
+      (let (directory)
+        (if (string-match "^\\(.*?\\)@\\(.*?\\):\\(.*?\\)$" path)
+            (progn
+              (let ((user (match-string 1 path))
+                    (host (match-string 2 path))
+                    (dir (match-string 3 path)))
+                (if (and (string-equal user user-login-name)
+                         (string-equal host (system-name)))
+                    (progn
+                      (when (file-directory-p dir)
+                        (setq directory (file-name-as-directory dir))))
+                  (setq directory
+                        ;; Bellow is what i altered
+                        (file-name-as-directory (concat (file-remote-p default-directory) dir))))))
+          (when (file-directory-p path)
+            (setq directory (file-name-as-directory path))))
+        directory)))
+  ;; Injects the payload to the vterm buffer.
+  (defun me/vterm-load-config ()
+    "Pass local configuration files to vterm.
 
-(mmm-add-group
- 'org-elisp
- '((elisp-src-block
-    :submode emacs-lisp-mode
-    :face org-block
-    :front "#\\+BEGIN_SRC emacs-lisp.*\n"
-    :back "#\\+END_SRC")))
+Allows remote vterm to be shell-side configured,
+without altering remote config.
+Also adds my personal configuration that does not rely
+too much on external packages.
+Prints a reasuring message to proove good faith."
+    (interactive)
+    (let (;; Bellow messages to reassure other users that look at history
+          (reasuring-message (format "Configuring shell of user %s to be emacs comptible"
+                                     user-full-name))
+          (reasuring-notice "This action is shell local, it will not affect other shells")
+          ;; Bellow lies my configuration
+          (basic-func-script (f-read-text (concat (getenv "HOME")
+                                                  "/.emacs.d/shells/sources/functions.sh")))
+          ;; Bellow lies the vterm shell-side configuration
+          ;; Must be sourced last
+          (vterm-func-script (f-read-text (concat
+                                           (file-name-directory (find-library-name "vterm"))
+                                           "/etc/emacs-vterm-bash.sh"))))
+      (vterm-insert (format "# START: %s\n" reasuring-message))
+      (vterm-insert (format "# %s\n" reasuring-notice))
+      ;; Create one single block in history
+      (vterm-insert "{\n")
+      (vterm-insert basic-func-script)
+      (vterm-insert vterm-func-script)
+      (vterm-insert "}\n")
+      ;; End the single block in history
+      (vterm-insert (format "# %s\n" reasuring-notice))
+      (vterm-insert (format "# STOP: %s\n" reasuring-message))
+      )
+    )
+
+  ;; find-file-other-window does not works great on remote:
+  ;; if given an absolute path on a remote host,
+  ;; the path will be understood as a local file since no
+  ;; tramp prefix is present, and bash does not care
+  ;; about tramp prefixes.
+  ;; Bellow we solve context before sending it to
+  ;; ffow
+  (defun me/vterm--find-file-other-window-wrapper (file)
+    "Help vterm find a FILE."
+    (find-file-other-window (me/vterm--ffow-resolver file)))
+  (defun me/vterm--ffow-resolver (file)
+    "Help vterm resolve FILE."
+    (cond
+     ;; "/sudo::"
+     ;; doom--sudo-file-path do the trick for us
+     ((s-starts-with-p "/sudo::" file)
+       (sudo-find-file
+        (concat (file-remote-p default-directory)
+                (substring-no-properties file 7))))
+     ;; "/" means we want the "Relative root"
+     ;; try appending the remote prefix if relevent
+     ((s-starts-with-p "/" file)
+      (concat (file-remote-p default-directory) file))
+     ;; we got a relative path
+     ;; we don't need to help ffow to find it
+     (t
+      file)))
+
+  ;; The variable vterm-eval-cmds is a SERIOUSLY SENSIBLE variable !
+  ;; Do not be the guy that adds RCE into their config !
+
+  ;; Allow customed ffow to be called from vterm
+  ;; ffow should be as safe as find-file which is already trusted
+  ;; we append our resolver that only manipulate strings,
+  ;; Proove me wrong but i think it's safe.
+  (add-to-list 'vterm-eval-cmds '("find-file-other-window"
+                                  me/vterm--find-file-other-window-wrapper))