unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: nyc4bos@aol.com
Cc: 13299@debbugs.gnu.org
Subject: bug#13299: 24.3.50; Tramp adb and device not found
Date: Mon, 11 Mar 2013 11:27:49 +0100	[thread overview]
Message-ID: <87d2v62pui.fsf@gmx.de> (raw)
In-Reply-To: <xl5ip501djk.fsf@aol.com> (nyc4bos@aol.com's message of "Sat, 09 Mar 2013 16:14:23 -0500")

nyc4bos@aol.com writes:

> Hi Michael,

Hi,

> Looks like I spoke to fast.
>
> It still hangs.
>
> I suspect it occurs when `adb devices' returns the following:
>
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
> List of devices attached
>
> Notice that it is blank and a device is not listed.

I can reproduce this message from a shell, if adb does not run on my
local machine, and no device is connected. But it doesn't harm Tramp,
and Emacs does not hang.

In order to reproduce your problem, I have killed adb on my local
machine prior to the following test runs.

1st test
========

C-x C-f /adb: <TAB>
  => "[Sole completion]"

2nd test
========

C-x C-f /adb:: <TAB>
  => "[No match]"

3rd test
========

C-x C-f /adb:: <RET>
  => "No device connected"

So I cannot reproduce the problem. As usual, my local machine does not
run MS Windows but Ubuntu; maybe this is the difference.

Could you, please, tell exactly which key sequence you have used? And
please use "emacs -Q" for your test.

I have used the following Emacs version for test:

GNU Emacs 24.3.50.20 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.13)
 of 2013-03-09 on detlef

Best regards, Michael.





  reply	other threads:[~2013-03-11 10:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87han5s0dv.fsf@gmx.de>
2012-12-31 12:24 ` bug#13299: 24.3.50; Tramp adb and device not found Jürgen Hötzel
2012-12-31 15:32   ` Michael Albinus
2012-12-28 21:28     ` nyc4bos
2013-01-05 20:26       ` nyc4bos
2013-01-07  9:59         ` Michael Albinus
2013-01-26  5:57           ` nyc4bos
2013-02-04 14:38             ` Michael Albinus
2013-02-05 23:32               ` nyc4bos
2013-02-27  9:25                 ` Michael Albinus
2013-03-05 21:43                   ` nyc4bos
2013-03-09 21:14                     ` nyc4bos
2013-03-11 10:27                       ` Michael Albinus [this message]
2013-03-16 20:00                         ` nyc4bos
2013-03-17 17:31                           ` Michael Albinus
2013-03-17 18:34                             ` Eli Zaretskii
2013-03-18  7:33                               ` Michael Albinus
2013-03-18 17:26                                 ` Eli Zaretskii
2013-03-18 17:36                                   ` Michael Albinus
2013-03-21 22:47                             ` nyc4bos
2013-03-23 11:57                               ` Michael Albinus
2013-01-06 18:25       ` Jürgen Hötzel
2013-01-07 21:10         ` nyc4bos
2013-01-07 23:55       ` nyc4bos

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=87d2v62pui.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=13299@debbugs.gnu.org \
    --cc=nyc4bos@aol.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).