From: Michael Albinus <michael.albinus@gmx.de>
To: Jeronimo Pellegrini <j_p@aleph0.info>
Cc: 35639@debbugs.gnu.org
Subject: bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual)
Date: Fri, 10 May 2019 10:40:00 +0200 [thread overview]
Message-ID: <8736lm3dpb.fsf@gmx.de> (raw)
In-Reply-To: <20190509201129.GE1697@socrates.lan> (Jeronimo Pellegrini's message of "Thu, 9 May 2019 17:11:29 -0300")
Jeronimo Pellegrini <j_p@aleph0.info> writes:
> Hi Michael,
Hi Jeronimo,
>> > Okay, I have it ready. Do I attach it here in the bug report?
>>
>> Yes, pls do.
>
> All right, here it is!
Thanks.
> I'm not sure I like the changes to the manual. Do you think it is
> OK?
Yes. See my comments, all of them are minor.
> --- a/doc/misc/tramp.texi
> +++ b/doc/misc/tramp.texi
> +@item @command{perl} or @command{perl5}(if the @command{MIME::Base64} module is available, it will be used)
Use a space between "{perl5}" and "(if". Care about 80 chars per line
limitation.
> +but other methods may still be used. If @command{grep} is available, it is
> +also used, in order to improve performance.
That's an error in the manual, gzip is meant. Pls correct.
> --- a/lisp/net/tramp-sh.el
> +++ b/lisp/net/tramp-sh.el
> +(defconst tramp-hexdump-awk-coding-test
> + "test -c /dev/zero && \
> +busybox hexdump -v -e '16/1 \" %02x\" \"\\n\"' < /dev/null && \
This must be "hexdump", not "busybox hexdump".
> + "Test command for checking `tramp-hexdump-awk-encode' and `tramp-awk-decode'.")
Care about 80 chars per line limitation.
> ;; Oops, I don't know what to do.
> (t (tramp-error
> - v 'file-error "Wrong method specification for `%s'" method)))
> + v 'file-error (concat "Cannot find any way to encode data using `%s'"
> + "-- check tramp-remote-path, and also "
> + "verify encoding binaries on the remote end.")
> + method)))
This error message is too long, I believe. Just the first part "Cannot
find ... using "%s" should serve.
> + ;; These is painful slow, so we put it on the end.
";; These are painful slow, so we put them on the end."
> + (b64 tramp-hexdump-awk-encode tramp-awk-decode ,tramp-hexdump-awk-coding-test)
Care about 80 chars per line limitation.
> Thank you!
> J.
Best regards, Michael.
next prev parent reply other threads:[~2019-05-10 8:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 16:25 bug#35639: 27.0.50; tramp fails to use ssh on LibreCMC (no base64 encoder available, and not mentioned in tramp manual) Jeronimo Pellegrini
2019-05-08 18:29 ` Michael Albinus
2019-05-08 23:01 ` Jeronimo Pellegrini
2019-05-09 7:35 ` Michael Albinus
2019-05-09 10:19 ` Jeronimo Pellegrini
2019-05-09 12:05 ` Michael Albinus
2019-05-09 12:37 ` Jeronimo Pellegrini
2019-05-09 12:45 ` Michael Albinus
2019-05-09 19:52 ` Jeronimo Pellegrini
2019-05-09 20:02 ` Michael Albinus
2019-05-09 20:11 ` Jeronimo Pellegrini
2019-05-10 8:40 ` Michael Albinus [this message]
2019-05-10 9:07 ` Robert Pluim
2019-05-10 9:17 ` Michael Albinus
2019-05-10 9:49 ` Jeronimo Pellegrini
2019-05-10 10:18 ` Michael Albinus
2019-05-10 14:45 ` Jeronimo Pellegrini
2019-05-11 1:57 ` Jeronimo Pellegrini
2019-05-12 8:43 ` Michael Albinus
2019-05-17 19:00 ` Jeronimo Pellegrini
2019-05-18 7:46 ` Michael Albinus
2019-10-11 13:14 ` Michael Albinus
2019-10-14 1:50 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-14 7:59 ` Michael Albinus
2019-12-27 17:26 ` Michael Albinus
2019-12-27 18:42 ` Eli Zaretskii
2019-12-30 13:12 ` Jeronimo Pellegrini
2020-01-01 9:28 ` Michael Albinus
2020-01-01 15:39 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-09 12:58 ` Michael Albinus
2020-01-11 13:07 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-11 13:23 ` Michael Albinus
2020-01-16 20:09 ` Jeronimo Pellegrini via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-16 20:23 ` Michael Albinus
2019-10-15 2:38 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736lm3dpb.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=35639@debbugs.gnu.org \
--cc=j_p@aleph0.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).