Ticket #3018 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

no subdir path completion in current dir, if stub not starting with './'

Reported by: yury_t Owned by: andrew_b
Priority: major Milestone: 4.8.11
Component: mc-core Version: master
Keywords: Cc:
Blocked By: Blocking:
Branch state: merged Votes for changeset: committed-master

Description

If completion stub isn't starting with './', one can't complete it (ALT+TAB) to subdir path.

So, for subdir 'abc', the stub './a' completes correctly, 'a' doesn't (also, with no other continuation variants available, the stub in prompt is cleared)

Is this an intended change of behaviour? I seem to have got used to such completions working with no './' required.

---

GNU Midnight Commander 4.8.8
Built with GLib 2.28.6
Using the S-Lang library with terminfo database
With builtin Editor
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With multiple codepages support
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, fish
Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

Change History

comment:1 Changed 4 years ago by andrew_b

  • Milestone changed from 4.8.9 to Future Releases

comment:2 Changed 4 years ago by andrew_b

  • Owner set to andrew_b
  • Status changed from new to accepted
  • Branch state changed from no branch to on review
  • Milestone changed from Future Releases to 4.8.11

comment:3 Changed 3 years ago by slavazanko

  • Votes for changeset set to slavazanko

comment:4 follow-up: ↓ 5 Changed 3 years ago by angel_il

so...
i have follow utility 'base64', 'basename', 'bash' and subdir named - 'bassis123'

when i try complete 'bass' then i get 'bassis123/'. (correct)
when i try complete 'bas' i see 'base64', 'basename', 'bash' in completion window without 'bassis123/' (incorrect?)

comment:5 in reply to: ↑ 4 Changed 3 years ago by andrew_b

Correct. You should reread man page.

Attempt to perform completion on the text before current position. MC attempts completion treating the text as variable (if the text begins with $), username (if the text begins with ~), hostname (if the text begins with @) or command (if you are on the command line in the position where you might type a command, possible completions then include shell reserved words and shell built-in commands as well) in turn. If none of these matches, filename completion is attempted.

So, if you have 'base64', 'basename', 'bash', you don't have 'bassis123/' in completion results.

Last edited 3 years ago by andrew_b (previous) (diff)

comment:6 Changed 3 years ago by angel_il

  • Votes for changeset changed from slavazanko to slavazanko angel_il
  • Branch state changed from on review to approved

So, if you have 'base64', 'basename', 'bash', you don't have 'bassis123/' in completion results.

ok.

comment:7 Changed 3 years ago by andrew_b

  • Status changed from accepted to testing
  • Votes for changeset changed from slavazanko angel_il to committed-master
  • Resolution set to fixed
  • Branch state changed from approved to merged

comment:8 Changed 3 years ago by andrew_b

  • Status changed from testing to closed
Note: See TracTickets for help on using tickets.