Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In-buffer filename completion broken #1244

Closed
basil-conto opened this issue Oct 17, 2017 · 3 comments
Closed

In-buffer filename completion broken #1244

basil-conto opened this issue Oct 17, 2017 · 3 comments

Comments

@basil-conto
Copy link
Collaborator

@basil-conto basil-conto commented Oct 17, 2017

Commit 55e34e8 introduced the following two behaviours:

Completion gets stuck
  1. make plain
  2. M-x ielm RET
  3. (find-file "t TAB TAB
    • Expected result: In-buffer completion of files under targets directory
    • Actual result: Unselectable minibuffer with prompt (targets/):
Completion overwrites filename prefixes

This recipe assumes a typical Unix-like installation of Emacs, where package-user-dir is at ~/.emacs.d/elpa.

  1. make plain
  2. M-x ielm RET
  3. (cd "~") RET
  4. (find-file "~/.emacs.d TAB
    • Expected result: (find-file "~/.emacs.d/
    • Actual result: (find-file ".emacs.d/
  5. elpa TAB
    • Expected result: (find-file "~/.emacs.d/elpa/
    • Actual result: (find-file "elpa/
@abo-abo
Copy link
Owner

@abo-abo abo-abo commented Oct 17, 2017

Thanks for the report. I can reproduce the issue, which is basically that :initial-input is e.g. "~/.e", while the candidates are '(".emacs.d" ".emacs" ...). I'll fix this today.

@abo-abo abo-abo closed this in 87c1e4e Oct 17, 2017
@abo-abo
Copy link
Owner

@abo-abo abo-abo commented Oct 17, 2017

Please test.

@basil-conto
Copy link
Collaborator Author

@basil-conto basil-conto commented Oct 18, 2017

Thanks very much, that seems to have fixed it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants