unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "జిందం వాఐి" <jindam.vani@disroot.org>
Cc: 67759@debbugs.gnu.org
Subject: bug#67759: [ android ] 30.0.50; unable to access device storage
Date: Mon, 11 Dec 2023 10:42:45 +0800	[thread overview]
Message-ID: <87sf49lasa.fsf@yahoo.com> (raw)
In-Reply-To: <4e81690b1b6a34b9411afad27e935015@disroot.org> ("జిందం వాఐి"'s message of "Mon, 11 Dec 2023 07:29:07 +0530")

Please don't remove the bug tracker from the CC list.

జిందం వాఐి <jindam.vani@disroot.org> writes:

> On 2023-12-11 06:38, Po Lu wrote:
>
>> This might seem trivial, but people have run across this pithole
>> before:
>> have you erased the leading "~" character in the default file name
>> prompt?  If not, do so, as Android's storage directory is located at
>> /sdcard rather than your home folder.
>> But assuming that you have, you've likely omitted the trailing "/"
>> after
>> the file name that informs Emacs it is a directory.  Absent this
>> character, file name completion will complete from / instead of
>> /sdcard,
>> and your device is one of those which deny Emacs the rights to examine
>> /.
>
> menu_ file_ opendirectory
> * ~/
> * press enter
> * shows 6 files [ 2 saved messages,
> emacs.d, emacs-fa...., 2 dots ]
>
> no effect [ using hackerskeyboard ]
> on find file or open directory
> * omitted ~ and type sdcard or
> storage
> * omitted ~ and / and type
> sdcard or storage

I don't understand, sorry.  Would you describe the actions you took in
English, rather than as such a heavily abridged enumeration?





  parent reply	other threads:[~2023-12-11  2:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 23:51 bug#67759: [ android ] 30.0.50; unable to access device storage జిందం వాఐి via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11  1:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <4e81690b1b6a34b9411afad27e935015@disroot.org>
2023-12-11  2:42     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-11  5:23       ` జిందం వాఐి via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11  7:28         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-27 13:22         ` Po Lu
2024-06-09 20:56           ` Stefan Kangas
2023-12-11 15:17 ` జిందం వాఐి 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=87sf49lasa.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=67759@debbugs.gnu.org \
    --cc=jindam.vani@disroot.org \
    --cc=luangruo@yahoo.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).