unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "内藤 祐一郎" <naito.yuichiro@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 39399@debbugs.gnu.org
Subject: bug#39399: tramp depends on unstable details of shell command line processing
Date: Tue, 28 Jul 2020 11:51:42 +0900	[thread overview]
Message-ID: <F9094A4E-A6EB-4B5B-898C-2A33A79AC2B7@gmail.com> (raw)
In-Reply-To: <87lfj4omzu.fsf@gmx.de>

Thanks for the reply.

> 2020/07/28 3:01、Michael Albinus <michael.albinus@gmx.de>のメール:
>> I could find a another way to solve this problem that avoids changing
>> ~/.editrc and it's more simple.
>> See my patch attached on this mail.
>> 
>> This problem happens on the latest libedit and FreeBSD sh uses Emacs
>> edit mode by default.
>> 
>> If libedit runs on edit mode, libedit rewrites line by each control character.
>> On '^H', libedit sends line feed and write characters on the line that
>> is held in the internal screen buffer of libedit.
>> 
>> If edit mode turns off, line edit works on terminal that is as same as
>> previous behavior.
>> 
>> Shell command `set +E` escapes from edit mode in spite of libedit has
>> two edit mode (Emacs and Vi). `set +E` disables both of them.
>> 
>> Although libedit has been developed and used by NetBSD, NetBSD doesn’t
>> have this problem.
>> Because NetBSD sh doesn't use edit mode by default.
> 
> Thanks for the report. However, your patch is not applicable in general,
> because the "+E" option is not POSIX conform, and it isn't supported by
> all shells. I thought already about this when I was fixing bug#39399.
> 
> But wait - "set +o emacs +o vi" might give the same effect, and it is
> much more supported by shells. And reading the sources, Tramp calls it
> already (might have been added by Kai, many years ago). Maybe it is
> sufficient to move it earlier in the initialization machinery?

Exactly yes it is!
“ set +o emacs +o vi” works as same as “set +E” on FreeBSD sh.
Tramp-mode hung before it, so it was not executed.

> Appended is a patch for Tramp 2.4.4. You might install it from GNU
> ELPA. Please check, whether this works for you.

The appended patch works for me.
But I think just moving "set +o emacs +o vi” before “stty …” is more simple way.

—
Yuichiro NAITO
naito.yuichiro@gmail.com






  reply	other threads:[~2020-07-28  2:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 21:28 bug#39399: tramp depends on unstable details of shell command line processing John F Carr
2020-02-03  8:58 ` Michael Albinus
2020-02-04  8:34   ` Michael Albinus
2020-02-05 23:42     ` John F Carr
2020-02-06  9:13       ` Michael Albinus
2020-07-27  4:12 ` 内藤 祐一郎
2020-07-27 18:01   ` Michael Albinus
2020-07-28  2:51     ` 内藤 祐一郎 [this message]
2020-07-28  7:34       ` 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=F9094A4E-A6EB-4B5B-898C-2A33A79AC2B7@gmail.com \
    --to=naito.yuichiro@gmail.com \
    --cc=39399@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).