Michael Albinus <[email protected]> writes:
> Robert Lupton the Good <[email protected]> writes:
>
>> Dear Michael,
Hi Robert,
> Maybe there is some automatic conversion in Emacs, which regards the
> null character as trigger for a different eol handling. I need to read
> the elisp documentation, first.
There seems to be such a null byte trigger, indeed. The following patch
shall fix it. Could you, please test?
--8<---------------cut here---------------start------------->8---
*** /home/albinus/src/emacs/lisp/vc/vc-git.el.~107457~ 2012-02-28
19:46:06.246595912 +0100
--- /home/albinus/src/emacs/lisp/vc/vc-git.el 2012-02-28 19:45:52.082525679
+0100
***************
*** 1108,1115 ****
(defun vc-git--call (buffer command &rest args)
;; We don't need to care the arguments. If there is a file name, it
;; is always a relative one. This works also for remote
! ;; directories.
! (apply 'process-file vc-git-program nil buffer nil command args))
(defun vc-git--out-ok (command &rest args)
(zerop (apply 'vc-git--call '(t nil) command args)))
--- 1108,1117 ----
(defun vc-git--call (buffer command &rest args)
;; We don't need to care the arguments. If there is a file name, it
;; is always a relative one. This works also for remote
! ;; directories. We enable `inhibit-null-byte-detection', otherwise
! ;; Tramp's eol conversion might be confused.
! (let ((inhibit-null-byte-detection t))
! (apply 'process-file vc-git-program nil buffer nil command args)))
(defun vc-git--out-ok (command &rest args)
(zerop (apply 'vc-git--call '(t nil) command args)))
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
_______________________________________________
Tramp-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/tramp-devel
