mimencode error using tramp

mimencode error using tramp

[Will Parsons]

Using Emacs 22.1.1 on FreeBSD, I'm trying to edit remote files on a system
running QNX4 using tramp, but I get the following error in the minibuffer:

  Couldn't find exit status of `mimencode -b </dev/null'

From the tramp buffer:

  ( mimencode -b </dev/null 2>/dev/null; echo tramp_exit_status $? )
  mimencode: not found
  tramp_exit_status 1

How can I turn off looking for mimencode so that I can get tramp to work?

-- 
Will

Re: mimencode error using tramp

[Michael Albinus]

Will Parsons <wbp@nodomain.invalid> writes:

> Using Emacs 22.1.1 on FreeBSD, I'm trying to edit remote files on a system
> running QNX4 using tramp, but I get the following error in the minibuffer:
>
>   Couldn't find exit status of `mimencode -b </dev/null'
>
> From the tramp buffer:
>
>   ( mimencode -b </dev/null 2>/dev/null; echo tramp_exit_status $? )
>   mimencode: not found
>   tramp_exit_status 1
>
> How can I turn off looking for mimencode so that I can get tramp to work?

See variable `tramp-coding-commands'. But Tramp shall check first, if a
given coding command is applicable on the remote host, so I don't
understand, why it is using mimencode.

Could you, please, send the traces?

Best regards, Michael.

Re: mimencode error using tramp

[Will Parsons]

Michael Albinus wrote:
> Will Parsons <wbp@nodomain.invalid> writes:
>
>> Using Emacs 22.1.1 on FreeBSD, I'm trying to edit remote files on a system
>> running QNX4 using tramp, but I get the following error in the minibuffer:
>>
>>   Couldn't find exit status of `mimencode -b </dev/null'
>>
>> From the tramp buffer:
>>
>>   ( mimencode -b </dev/null 2>/dev/null; echo tramp_exit_status $? )
>>   mimencode: not found
>>   tramp_exit_status 1
>>
>> How can I turn off looking for mimencode so that I can get tramp to work?
>
> See variable `tramp-coding-commands'. But Tramp shall check first, if a
> given coding command is applicable on the remote host, so I don't
> understand, why it is using mimencode.
>
> Could you, please, send the traces?

When I retried this, I get somewhat different diagnostics, but still the
same basic problem.

Tramp buffer:
--------------------------------------
( tramp_encode </dev/null 2>/dev/null; echo tramp_exit_status $? )
tramp_encode: not found
tramp_exit_status 1


Trace buffer:
--------------------------------------
Debugger entered--Lisp error: (error "Couldn't find an inline transfer encoding")
  signal(error ("Couldn't find an inline transfer encoding"))
  error("Couldn't find an inline transfer encoding")
  tramp-find-inline-encoding(nil nil "wbp" "maple")
  tramp-post-connection(nil nil "wbp" "maple")
  tramp-open-connection-rsh(nil nil "wbp" "maple")
  tramp-maybe-open-connection(nil nil "wbp" "maple")
  tramp-send-command(nil nil "wbp" "maple" "cd ~; pwd" t)
  tramp-handle-expand-file-name("/wbp@maple:.emacs" nil)
  apply(tramp-handle-expand-file-name ("/wbp@maple:.emacs" nil))
  tramp-sh-file-name-handler(expand-file-name "/wbp@maple:.emacs" nil)
  apply(tramp-sh-file-name-handler expand-file-name ("/wbp@maple:.emacs" nil))
  tramp-file-name-handler(expand-file-name "/wbp@maple:.emacs" nil)
  expand-file-name("/wbp@maple:.emacs")
  find-file-noselect("/wbp@maple:.emacs" nil nil t)
  find-file("/wbp@maple:.emacs" t)
  call-interactively(find-file)

--------------------------------------

The value of tramp-coding-commands is:

(("mimencode -b" "mimencode -u -b" base64-encode-region base64-decode-region)
 ("mmencode -b" "mmencode -u -b" base64-encode-region base64-decode-region)
 ("recode data..base64" "recode base64..data" base64-encode-region base64-decode-region)
 ("uuencode xxx" "uudecode -o /dev/stdout" tramp-uuencode-region uudecode-decode-region)
 ("uuencode xxx" "uudecode -o -" tramp-uuencode-region uudecode-decode-region)
 ("uuencode xxx" "uudecode -p" tramp-uuencode-region uudecode-decode-region)
 ("uuencode xxx" "tramp_uudecode" tramp-uuencode-region uudecode-decode-region)
 ("tramp_encode_with_module" "tramp_decode_with_module" base64-encode-region base64-decode-region)
 ("tramp_encode" "tramp_decode" base64-encode-region base64-decode-region))

But I don't know what to do with this information to get tramp to work.

-- 
Will

Re: mimencode error using tramp

[Michael Albinus]

Will Parsons <wbp@nodomain.invalid> writes:

> When I retried this, I get somewhat different diagnostics, but still the
> same basic problem.
>
> Tramp buffer:
> --------------------------------------
> ( tramp_encode </dev/null 2>/dev/null; echo tramp_exit_status $? )
> tramp_encode: not found
> tramp_exit_status 1
>
>
> Trace buffer:
> --------------------------------------
> Debugger entered--Lisp error: (error "Couldn't find an inline transfer encoding")

That means what it says: Tramp cannot find a program on the remote host
for encoding and decoding.

You must use an external method instad of, like scp. I'm not sure
whether this works for Tramp 2.0; recently I've fixed a bug in Tramp
2.1, where Tramp gave up in the same case although inline encodings
where not needed.

If Tramp 2.0 works for you with scp - fine. Otherwise, you might check
the latest Tramp 2.1 from Tramp or Emacs 23 CVS repository. Or you wait
for Tramp 2.1.16, which shall be released, soon.

Best regards, Michael.