From: Eli Zaretskii <eliz@gnu.org>
To: Pankaj Jangid <pankaj.jangid@gmail.com>
Cc: 38056-done@debbugs.gnu.org
Subject: bug#38056: 27.0.50; dired.c changes introduced autocompletion error
Date: Mon, 04 Nov 2019 17:43:22 +0200 [thread overview]
Message-ID: <838sovir51.fsf@gnu.org> (raw)
In-Reply-To: <m2r22ob4hq.fsf@gmail.com> (message from Pankaj Jangid on Mon, 04 Nov 2019 10:52:09 +0530)
> From: Pankaj Jangid <pankaj.jangid@gmail.com>
> Date: Mon, 04 Nov 2019 10:52:09 +0530
>
> I have tried it in various ways. The checkin
> 84a3793b194efe92e2eb80cd0f625f3324bf4cae have introduced autocompletion
> issues at various places. To reproduce, I have tried these steps. I have
> also tried it on one previous commit
> (3c86424a182892db1e0216b9aa7e8389ae6f13de). This commit is ok; which
> implies that the issues has occurred in commit
> 84a3793b194efe92e2eb80cd0f625f3324bf4cae only.
FTR, this issue was introduced by commit 0b21ecd, not
84a3793b194efe92e2eb80cd0f625f3324bf4cae.
> (1) launched emacs using "./src/emacs -Q".
> (2) (setq debug-on-error t).
> (3) C-x C-f and then type few characters of some file and TAB. This
> produces same error. autocompletion on directories is working fine.
> OR
> (3) Tried to rename a file in dired. Press R, press few characters of
> the file, press TAB. This produces error. I have debug-on-error set to
> t.
>
> produces this error:
>
> Debugger entered--Lisp error: (args-out-of-range "a.txt" 3 2)
> file-name-completion("a" "~/work/temp/" file-exists-p)
Sorry about that. Should be fixed now.
next prev parent reply other threads:[~2019-11-04 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 5:22 bug#38056: 27.0.50; dired.c changes introduced autocompletion error Pankaj Jangid
2019-11-04 13:48 ` Mattias Engdegård
2019-11-04 17:51 ` Pankaj Jangid
2019-11-04 15:43 ` Eli Zaretskii [this message]
2019-11-04 17:52 ` Pankaj Jangid
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838sovir51.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38056-done@debbugs.gnu.org \
--cc=pankaj.jangid@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.