-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Display current args at edit prompt #37968
base: main
Are you sure you want to change the base?
Conversation
@maxandersen could you test that one? |
5731a4a
to
0e614ed
Compare
0e614ed
to
2b574c6
Compare
I tried this and it is better but still broken. tried capture it in this recording: 2024-01-17_09-57-17.mp4editing shows the current arg line correctly, but when I press enter it still shows "current arg: >" making me believe it is still asking for input. But it is actually in devmode input mode as shorthand keys like d for debug etc works. |
@@ -70,7 +70,13 @@ public void accept(int[] ints) { | |||
Holder command = commands.get(key); | |||
if (command != null) { | |||
if (command.consoleCommand.getReadLineHandler() != null) { | |||
QuarkusConsole.INSTANCE.doReadLine(); | |||
if (key == 'e') { | |||
QuarkusConsole.INSTANCE.doReadLineWithPrompt("Current args: " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you think about just having it be:
"state list">
instead of:
Current args: "state list">
just to save some characters in width?
otherwise maybe split over two lines and not use current
as you can't "escape" to reuse it?
Enter new arguments (was "state list"):
>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prompt changed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good changes but behavior still broken after pressing enter.
2b574c6
to
72d761a
Compare
I think this might be some weird issue with different terminals, that's why I wasn't encountering this issue from your original issue:
I am not seeing anything like this - maybe it is something related to Your terminal or OS? I checked this both in ZSH and Bash and it is fine, check the recording below: q-issue.mp4 |
Hey @maxandersen! Have you maybe had a chance to look at the video I posted? I'm checking on the status of this PR. |
Sorry. Missed the update. I'll check when back at my laptop. |
Hey @maxandersen, I'm checking on the status, have You seen the update? |
@maxandersen I think we should merge this as it's better than what we had, even if it didn't fix the whole issue for you (apparently, it works for the OP so it might be environment-dependent). WDYT? |
you are probably right - let me try again. |
Just wanted to let you know, that if there are still some issues with this PR which I will be able to reproduce, then I will be happy to fix them |
i've tried to build this pr but keeps having weird issues building. recent one is:
don't think its this pr fault but just t ogive context why didn'tconfirm the pr yet. |
okey so I managed to build this when disabling cache (-Dno-build-cache=false) but i still see the issue of the line staying around. so something in this PR or branch is triggering bad behaviour. I tried using iterm2 and terminal - same result. works in 3.12 but with this PR it becomes broken. |
also tried plain bash (so none of my zsh customization should influence it). same problem. the prompt keeps "hanging" and even though I can do things like 's' for restart or 'w' for open browser - the terminal is not showing I can do that. |
Signed-off-by: Maciej Lisowski <[email protected]>
I have just retested this, and for me still works as it is supposed to even on the different OS.
And now, using the just build CLI jar, I run this project in two different terminals (emulated by Intellij and system) and here are the results: 2024-07-24.11-16-38.mp4@gsmet @maxandersen I'm not sure why it is happening to You, but like I said, I had no issues with building and running this change, and I tested this on different OS and shells. Maybe there are some steps that You do differently? |
72d761a
to
924ae7f
Compare
@maxandersen What should we do about this one? |
1 similar comment
@maxandersen What should we do about this one? |
@MaciejDromin sorry for dropping ball on this one - it still fails for me so not sure how to fix it :/ maybe a shared screen/debug session would help? (sometime in the new year) |
@maxandersen Sure, sounds good. Maybe together we will be able to figure out what is happening :D |
@maxandersen sounds like you will be able to debug it :-) |
It fixes #37921 - point 3.

At the edit prompt it shows now current command line arguments, as shown in the screenshot below.