new version cannot close

[newyorkthink]

when i close bluetuith, use q, or ctrl c is not work so i just use kill command.

and i kill bluetuith. it show look this

cannot run anything

[darkhz]

The new keybinding is now Shift+q, I forgot to update the docs, I'll do it soon. See #8.

On Thu, 22 Jun, 2023, 10:53 am Thinker, @.***> wrote:

when i close bluetuith, use q, or ctrl c is not work so i just use kill command.

and i kill bluetuith. it show look this [image: image] https://user-images.githubusercontent.com/87791643/247831147-62b6bafa-0578-411d-9c90-6ff606e0ba98.png

cannot run anything

— Reply to this email directly, view it on GitHub https://github.com/darkhz/bluetuith/issues/17, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQERARGFL6RLM2INNLQKXLXMPJGLANCNFSM6AAAAAAZPVMUTU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[darkhz]

The new keybinding is Shift+q, I forgot to update the docs, I'll do it soon. See #8.

[sabrehagen]

@darkhz can this change be added to invidtui too please

[darkhz]

@sabrehagen sure, but make a separate issue in the invidtui repo please.

[sabrehagen]

@darkhz seeing as no other function is bound to q, why not make q quit? q is common throughout many tui utilities as the method of exit, I have never encountered Shift+q before.

[darkhz]

It's very easy to accidentally press 'q', so I think Ctrl+C may be a more suitable choice.

[sabrehagen]

I would disagree, for a competent user 'q' is not usually an issue. Writers of less, more, etc. i.e. unix core tools must not have felt it was an issue.

[darkhz]

That's true, let me look into this further. I think during transfers, for example, it could be an issue when 'q' is accidentally pressed, since it could corrupt the transferring file. I'm currently working on making all the keybindings configurable, however, so that the users can set the keys to whatever they want.