From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Pittman <slippycheeze@google.com>
Cc: 28139@debbugs.gnu.org
Subject: bug#28139: 25.2; TRAMP vs bash 4.4 / readline 7.0 "bracketed paste" mode
Date: Sat, 19 Aug 2017 19:59:07 +0200 [thread overview]
Message-ID: <87mv6vjv6c.fsf@detlef> (raw)
In-Reply-To: <CAC45yQtg2aCNk4Ga9rbfG6i91Hbp+CXJPo48FPAwfULJMdzhXw@mail.gmail.com> (Daniel Pittman's message of "Fri, 18 Aug 2017 11:22:29 -0400")
Daniel Pittman <slippycheeze@google.com> writes:
Hi Daniel,
> After upgrading a remote system to a version of GNU/Linux that
> includes bash
> 4.4 (from Debian/testing), with the readline option `set
> enable-bracketed-paste on` in /etc/inputrc, and no personal inputrc,
> tramp breaks.
Many different shells are busy to break Tramp.
> Passing the `--noediting` option to the remote shell command resolves
> the problem, by disabling readline entirely, but it should also be
> possible to augment the
> `tramp-open-connection-setup-interactive-shell` to issue,
> unconditionally, the command:
>
> bind 'set enable-bracketed-paste off'
Does it help to add the following line into your remote ~/.bashrc:
[ $TERM = "dumb" ] && bind 'set enable-bracketed-paste off'
Best regards, Michael.
next prev parent reply other threads:[~2017-08-19 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 15:22 bug#28139: 25.2; TRAMP vs bash 4.4 / readline 7.0 "bracketed paste" mode Daniel Pittman
2017-08-19 17:59 ` Michael Albinus [this message]
2017-08-21 15:19 ` Daniel Pittman
2017-08-21 15:45 ` Michael Albinus
2017-08-21 16:01 ` Daniel Pittman
2017-08-21 16:17 ` Michael Albinus
2017-08-24 19:52 ` Daniel Pittman
2017-08-25 7:31 ` Michael Albinus
2017-10-31 20:40 ` Daniel Pittman
2017-11-05 12:45 ` Michael Albinus
2017-11-13 19:41 ` Daniel Pittman
2017-11-14 10:44 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv6vjv6c.fsf@detlef \
--to=michael.albinus@gmx.de \
--cc=28139@debbugs.gnu.org \
--cc=slippycheeze@google.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.