libedit for sftp
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the Windows sftp build entry point and investigate how the upstream --with-libedit option is supported. Research libedit integration and whether the existing sftp command-line behavior can provide editing and tab completion. Done means the Windows sftp binary builds with libedit and provides the requested interactive completion behavior.
Written by the indexing model from the issue text.
Description
Summary of the new feature / enhancement
As mentioned multiple times since 2016, sftp binary shipped with Windows is still barely usable, tab completion is not hard to implement, and upstream openssh says clearly in their documentation:
--with-libedit Enable libedit support for sftp.
But in the 2016 issue (#261) where this issue had been first raised, one contributor didn't even know if
sftp autocomplete work in the Unix version of OpenSSH?
And a collaborator said auto-completion is "provided by terminal" and closed the issue! Can you please at least do some research if you have no clue how things work?
auto complete functionality is provided by the terminals (like cygwin) and not by the sftp.
sftp protocol doesn't deal with auto complete. please use terminals that support the auto complete (like cygwin).
Not to mention sftp's auto-completion has nothing to do with "terminal", no command line editing ever had anything to do with terminal at all! I'm shocked how he can be a collaborator of this repo with such limited knowledge about openssh and unix in general.
Proposed technical implementation details (optional)
--with-libedit
when building this project
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 822
- Avg merge
- 12m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/Win32-OpenSSH
-
Area-ssh-agent Issue-Upstream Parity
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
PowerShell/Win32-OpenSSH#2458 · 1 reaction ·
-
Area-Authentication Area-Logging/Diagnostics Area-sshd Investigate Issue-Bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PowerShell/Win32-OpenSSH#2466 · 1 comment · 1 reaction ·
-
Area-sshd Area-Terminal Investigate Issue-Regression
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PowerShell/Win32-OpenSSH#2465 · 1 comment · 1 reaction ·
-
Area-ssh-agent Issue-Enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
PowerShell/Win32-OpenSSH#2462 · 1 comment · 1 reaction ·
-
Area-ssh-agent Investigate
Difficulty 5/5 Over a week Newbie friendliness 25/100
PowerShell/Win32-OpenSSH#2460 · 1 reaction ·
All issues in PowerShell/Win32-OpenSSH
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-cli#154 ·
Maintainers usually reply within 3 days
-
type/automation type/performance
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days