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: Mon, 21 Aug 2017 17:45:53 +0200 [thread overview]
Message-ID: <8760dgapqm.fsf@detlef> (raw)
In-Reply-To: <CAC45yQtbQeBqO=2F-xsOr0YqFswZQmgukV5RGd+uk-dRoRFEWw@mail.gmail.com> (Daniel Pittman's message of "Mon, 21 Aug 2017 11:19:31 -0400")
Daniel Pittman <slippycheeze@google.com> writes:
Hi Daniel,
> So, it's not possible to work around this issue without injecting
> additional code into the shell setup process, using `/bin/sh -
> -noediting`, or using an interactive shell and adding that to the .
> profile or equivalent.
>
> note: --noediting has been present since bash 2.0 according to their
> changelog, so it may be reasonable to add by default to the
> non-interactive shell invocations.
>
> Ultimately, though, perhaps adding the ability to run additional
> commands during the interactive shell setup process and/or consuming
> any CSI sequences prior to matching, would be a more future-proof
> solution to this.
Well, we have `tramp-sh-extra-args' for ages. But this doesn't work
usually, because I don't know a bullet-proof way to detect a bash shell
prior invocation, unless "*bash" is called.
Let me contemplate about. With Emacs 26 / Tramp 2.3, we have
connection-local variables. Maybe we could use it for your case.
Best regards, Michael.
next prev parent reply other threads:[~2017-08-21 15:45 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
2017-08-21 15:19 ` Daniel Pittman
2017-08-21 15:45 ` Michael Albinus [this message]
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
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=8760dgapqm.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 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).