unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Neal Becker <ndbecker2@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp trouble with 24.3
Date: Mon, 22 Apr 2013 12:45:17 +0200	[thread overview]
Message-ID: <87vc7eq1xe.fsf@gmx.de> (raw)
In-Reply-To: <kks5tq$1nu$1@ger.gmane.org> (Neal Becker's message of "Fri, 19 Apr 2013 15:29:02 -0400")

Neal Becker <ndbecker2@gmail.com> writes:

Hi Neal,

> Neal Becker wrote:
>
>> Michael Albinus wrote:
>> 
>>> Neal Becker <ndbecker2@gmail.com> writes:
>>> 
>>>> This is a linux box talking to a linux box, so if doesn't work for me, I'll
>>>> bet I'm not the only one who will/has seen this.
>>> 
>>> Your prompt doesn't look to be the default one. I guess it is
>>> customized, isn't it?
>>> 
>>> Best regards, Michael.
>> 
>> No it isn't.  Maybe it's cause color prompts are on by default?  That's not my
>> idea.  That's fedora 18.

Many people are using Fedora 18, and I haven't seen any other complaint yet.

> Also, shell-prompt-pattern is working in shell-mode.  In shell mode:
>
> echo $PS1
> \[\033[01;32m\]\u@\h\[\033[00m\] 
> \[\033[01;34m\]\W\[\033[00m\]\[\033[1;32m\]\$\[\033[m\]

And? Tramp does not use shell-mode. Anyway, this prompt is hard enough
to parse. The Tramp manual gives you some hints how to avoid escape
sequences, when scripts are accessing your account from remote.

> Also, don't forget, the problem is not seen in 24.2

Maybe there was a pattern change in Tramp. As I said, I don't remember, but ...

> I used emacs from fedora.  Used rpmbuild --rebuild to build the fedora
> 20 rpm on
> fedora 18.  I don't see anything added by the fedora rpm that would change this 
> prompt regex (but haven't searched exhaustively)

Sorry, I don't use Fedore, and I don't understand what you have changed
via rpmbuild etc. Anyway, if I could see your complete prompt (including
escape sequence), I could try to adapt tramp-shell-prompt-pattern to
your needs. The example above is not sufficient, because it does not
expand user and host names, and alike.

Just run your test case with tramp-verbose 10. There will be traces like

--8<---------------cut here---------------start------------->8---
12:37:39.845362 tramp-accept-process-output (10) # 
#$
--8<---------------cut here---------------end--------------->8---

(#$ is my prompt). Send those lines as coded attachment, in order not to
loose escape sequences. I will analyze them.

You could send it directly to me, in order to avoid bit lossages.

Best regards, Michael.



      reply	other threads:[~2013-04-22 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 13:35 tramp trouble with 24.3 Neal Becker
2013-04-19 14:38 ` Michael Albinus
2013-04-19 14:53   ` Neal Becker
2013-04-19 15:05     ` Michael Albinus
2013-04-19 15:24       ` Neal Becker
2013-04-19 17:56         ` Michael Albinus
2013-04-19 18:23           ` Neal Becker
2013-04-19 18:38             ` Michael Albinus
2013-04-19 18:42               ` Neal Becker
2013-04-19 19:29                 ` Neal Becker
2013-04-22 10:45                   ` Michael Albinus [this message]

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=87vc7eq1xe.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ndbecker2@gmail.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.
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).