-
Notifications
You must be signed in to change notification settings - Fork 73
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
Delkey patch #21
Comments
what is your use-case for including? I had applied it initially but found I was fine with reverting and having default terminfo -- just curious what you're running into. |
Well, without this patch, the delete key behaves like a F1 key. My term variable as set by St is st-256color, but the delete key sends F1 key, meaning many ncurses apps shortcuts don't work like ranger and ncmpcpp shortcuts. |
http://git.suckless.org/st/tree/FAQ |
It appears I had a problem with my environment from previous debugging, where though I had removed the patch a terminfo stuck around with the definition -- I will apply the patch this evening. |
Thanks a lot.
On Tue, Mar 14, 2017, 6:17 PM Nathan Isom ***@***.***> wrote:
It appears I had a problem with my environment from previous debugging,
where though I had removed the patch a terminfo stuck around with the
definition -- I will apply the patch this evening.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGz560Rg5tBRsVeAHT9tgnnsUhEQgQWlks5rloxygaJpZM4MauAn>
.
--
Arindam Banerjee
|
Since you added this patch back in, I seem to be having exactly the problems it is supposed to solve (when it works at all, my delete key is now behaving as a backspace. Backspace also behaves as a backspace). Rolling back to before you applied the patch, everything works fine. |
My delete key still behaves like a F1 key. Do I need to do anything? The
backspace still works as expected. So, no changes observed.
On Tue, Mar 21, 2017, 9:53 PM parchd-1 ***@***.***> wrote:
Since you added this patch back in, I seem to be having exactly the
problems it is supposed to solve (when it works at all, my delete key is
now behaving as a backspace. Backspace also behaves as a backspace).
Rolling back to before you applied the patch, everything works fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGz5694NK5tMvYtURvURrQKHR_25iwixks5rn_lwgaJpZM4MauAn>
.
--
Arindam Banerjee
|
Without the patch, I just followed the guide in the st FAQ and aded a couple of workarounds into my profile for programs behaving badly (nvim, for example). Pretty much everything worked fine. With the patch, no matter what I do (or don't do) I can't use the delete key. |
Do you know how to use the delete key in ncurses applications? (Without the
patch)
On Tue, Mar 21, 2017, 10:05 PM parchd-1 ***@***.***> wrote:
Without the patch, I just followed the guide in the st FAQ and aded a
couple of workarounds into my profile for programs behaving badly (nvim,
for example). Pretty much everything worked fine. With the patch, no matter
what I do (or don't do) I can't use the delete key.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGz56wpnQ0IK1HCV8TT5IwqR5UrLgpZ7ks5rn_xWgaJpZM4MauAn>
.
--
Arindam Banerjee
|
What shell do you use? |
Zsh
On Tue, Mar 21, 2017, 10:51 PM parchd-1 ***@***.***> wrote:
What shell do you use?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGz561RBQMc7OLWi10k2WCi-rpMDyWq4ks5roAchgaJpZM4MauAn>
.
--
Arindam Banerjee
|
Here is the relavant part of my zshrc. Note, this does not work correctly when the patch is applied - you need to compile an older revision. # Make the keyboard work correctly in st and similar terminals
function zle-line-init() {
echoti smkx
}
function zle-line-finish() {
echoti rmkx
}
zle -N zle-line-init
zle -N zle-line-finish
nvim(){ # fix delete key in neovim for the time being
tput smkx
command nvim $@
}
ipython(){ # apparentyl ipython also has the problem with delete, etc.
tput smkx
command ipython $@
}
bindkey "^[[1;5C" forward-word
bindkey "^[[1;5D" backward-word
bindkey "^[[1~" beginning-of-line
bindkey "^[[4~" end-of-line
bindkey "^[[3~" delete-char |
I experience the same. Will revert the patch. |
Thanks |
@parchd-1 so, for each ncurses program, I'll need to define functions? I've
got aliases set up for many programs. Also, will this work when we do
something of the sort of ``st -e ranger``?
Do you know of anyway to bypass this?
On Wed, Mar 22, 2017, 4:01 AM parchd-1 ***@***.***> wrote:
Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGz563egtz-Ita4bimsWKGIbQ_ZevdVuks5roE_BgaJpZM4MauAn>
.
--
Arindam Banerjee
|
@SageEx those two functions I used are not for ncurses programs, but both behave a bit badly in that they don't switch to application input mode. Last I checked the exact reason in neovim was being investigated. On my end, ncurses programs already function correctly. What makes you think ranger doesn't? Have you actually bound something to delete? Although the list of bindings it displays suggests is already bound, I found that it wasn't. Try: |
@parchd-1 I already have this mapping |
Which version of xst are you using at the moment? |
Can you include the delkey patch ?
The text was updated successfully, but these errors were encountered: