From: "Trent W. Buck" <trentbuck@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: rfrancoise@debian.org, 2463@emacsbugs.donarmstrong.com
Subject: bug#2463: 23.0.90; tramp: coreutils' base64(1) in tramp-remote-coding-commands?
Date: Thu, 26 Feb 2009 11:15:23 +1100 [thread overview]
Message-ID: <20090226001518.GA2469@Clio.twb.ath.cx> (raw)
In-Reply-To: <nqzlgaly3j.fsf@alcatel-lucent.de>
On Wed, Feb 25, 2009 at 09:28:16AM +0100, Michael Albinus wrote:
> trentbuck@gmail.com writes:
> > From a mailing list:
>
> Is there a chance to get the full history of the report?
Here, I think.
http://lists.luv.asn.au/wws/arc/luv-main/2009-02/msg00437.html
> > I don't find a reference to the base64 program in
> > tramp-remote-coding-commands. Is there a reason for this?
>
> No special reason. Likely because it is a rather new command.
Well, FSVO new = February 2006 :-)
> Maybe it is sufficient to apply
>
> (add-to-list 'tramp-remote-coding-commands '(b64 "base64" "base64 --decode"))
>
> If it works, I could add it in Tramp permanently.
It seems to work for me; at least after evaluating that form I can
still open files on a remote host (/ssh:foo:bar) where that host has
base64 installed.
next prev parent reply other threads:[~2009-02-26 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1698.1235527424.31690.bug-gnu-emacs@gnu.org>
2009-02-25 8:28 ` bug#2463: 23.0.90; tramp: coreutils' base64(1) in tramp-remote-coding-commands? Michael Albinus
2009-02-26 0:15 ` Trent W. Buck [this message]
2009-02-26 14:38 ` Michael Albinus
2009-02-25 1:43 trentbuck
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=20090226001518.GA2469@Clio.twb.ath.cx \
--to=trentbuck@gmail.com \
--cc=2463@emacsbugs.donarmstrong.com \
--cc=michael.albinus@gmx.de \
--cc=rfrancoise@debian.org \
/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).