You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have to make autocomplete feature for dynamic. To make it work we need to create a xonsh shell. Still confused ?
Ref to this - xonsh
How does it actually works?
When a user types dynamic. It will redirect to a different shell on the same terminal and we can use autocomplete in that shell because our normal terminal doesn't allow you to autocomplete.
Ref first 1 sec of GIF [When he type gitsome, Another shell got popup [still confused? Tried installing gitsome in local and type gitsome in terminal]]-
Credit for xonsh - xonsh
Credit for Gitsome - Gitsome
@sudojarvis That’s correct gitsome uses the xonsh shell.
no no, you don’t have to create it from scratch just leverage the xonsh and try to replicate the flow from gitsome
Okay but i think this autocomplete should work based on both things. One is history and other is args.
As of now, can you make a PR, I’ll review it locally and will give you suggestions accordingly
Restart triage: P3 — xonsh shell proposal for this issue (#125). This issue asks for a custom shell to support autocomplete, and the related autocomplete issue #126 explicitly names #125 as a dependency. Current inspected source has no xonsh integration; earlier prototypes do not establish shipped support.
Next step: agree on command/history completion and normal-shell workflow requirements before adopting the extra runtime surface. Compare the smallest suitable approach and preserve attribution/licensing for reused code. This is outside the first maintenance milestone.
Source review only; no shell or prototype was run during triage. Keeping this issue open.
Activity
sudojarvis commentedon Mar 2, 2022
Hi, I would like to work on this issue. Could you please give some head start?
It would be helpful.
GouravSardana commentedon Mar 2, 2022
Go ahead buddy @sudojarvis
sudojarvis commentedon Mar 3, 2022
@GouravSardana gitsome uses xonsh shell. I have to do a similar thing right?
sudojarvis commentedon Mar 3, 2022
Do we have to do it from scratch or we can merge it from xonsh.
GouravSardana commentedon Mar 3, 2022
@sudojarvis That’s correct gitsome uses the xonsh shell.
no no, you don’t have to create it from scratch just leverage the xonsh and try to replicate the flow from gitsome
sudojarvis commentedon Mar 5, 2022
@GouravSardana could you please assign the issue to me under GSSOC'22.
GouravSardana commentedon Mar 5, 2022
Np. Work on this issue. Don’t worry about assigning the issues. I’ll take care of that
sudojarvis commentedon Mar 6, 2022
Kazam_screencast_00018.mp4
@GouravSardana Till now it is auto-completing, what I typed previously. But I have used code from gitsome. Is this fine?
GouravSardana commentedon Mar 6, 2022
@sudojarvis Is this using XONSH ? I couldn't see this going to the xonsh terminal just like in gitsome.
sudojarvis commentedon Mar 6, 2022
@GouravSardana yes, to 1st two questions. And updated the video watch from 2:35.
sudojarvis commentedon Mar 6, 2022
GouravSardana commentedon Mar 6, 2022
Okay but i think this autocomplete should work based on both things. One is history and other is args.
As of now, can you make a PR, I’ll review it locally and will give you suggestions accordingly
GouravSardana commentedon Mar 7, 2022
@sudojarvis Any update ?
GouravSardana commentedon Oct 21, 2026
Restart triage: P3 — xonsh shell proposal for this issue (#125). This issue asks for a custom shell to support autocomplete, and the related autocomplete issue #126 explicitly names #125 as a dependency. Current inspected source has no xonsh integration; earlier prototypes do not establish shipped support.
Next step: agree on command/history completion and normal-shell workflow requirements before adopting the extra runtime surface. Compare the smallest suitable approach and preserve attribution/licensing for reused code. This is outside the first maintenance milestone.
Source review only; no shell or prototype was run during triage. Keeping this issue open.