unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 68227@debbugs.gnu.org
Subject: bug#68227: 29.1; [tramp] adb stopped working (after upgrade from Emacs 28 to 29?)
Date: Wed, 17 Jan 2024 17:10:39 -0500	[thread overview]
Message-ID: <87fryvmx0g.fsf@gmail.com> (raw)
In-Reply-To: <87r0iqc0op.fsf@gmx.de> (Michael Albinus's message of "Tue, 09 Jan 2024 10:31:50 +0100")

Hi Michael,

Michael Albinus <michael.albinus@gmx.de> writes:

>>> [...] the result of this function is cached. There might be something
>>> unstale. Could you, pls, try to test w/o cached properties? That is,
>>> call
>>
>>> # emacs -Q /adb::
>>
>> This is what I see in the *Messages* buffer:
>>
>> Tramp: Opening adb shell connection...done
>> File error: Directory /adb::/data/local/tmp not accessible
>> Wrong type argument: "Wrong type argument", "stringp nil"
>> Tramp: Inserting ‘/adb::/’...failed
>> File is missing: /adb::/
>> Use M-x make-directory RET RET to create the directory and its parents
>
> If /data/local/tmp isn't accessible (writable), Tramp has problems,
> because it uses it as temporary directory on the phone. Pls check why
> this doesn't work.

I'm a bit puzzled; as I've now re-rooted the phone and I get the same
result, although I can now do:

--8<---------------cut here---------------start------------->8---
$ adb shell
shell@htc_alpine_dugl:/ $ cd /data/local/tmp
shell@htc_alpine_dugl:/data/local/tmp $
--8<---------------cut here---------------end--------------->8---

It's also possible to 'touch' a file there and delete it afterward.

Any other ideas?

-- 
Thanks,
Maxim





  parent reply	other threads:[~2024-01-17 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  4:37 bug#68227: 29.1; [tramp] adb stopped working (after upgrade from Emacs 28 to 29?) Maxim Cournoyer
2024-01-08 11:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-09  3:37   ` Maxim Cournoyer
2024-01-09  9:31     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-17 12:44       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-17 22:10       ` Maxim Cournoyer [this message]
2024-01-18  7:46         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19  4:40           ` Maxim Cournoyer
2024-01-19 10:31             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-28 17:18               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-04 11:13                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87fryvmx0g.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=68227@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).