-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Code echo'ed when running a command quickly #100
Comments
Thank you for your report! Currently, the problem doesn't reproduce. I'll later check the related code to guess what's happening. It may take some time. |
Just to provide some of my configs, below is my set colored-stats on
set visible-stats on
set completion-ignore-case on
set show-all-if-unmodified on
set colored-completion-prefix on
set mark-symlinked-directories on
set menu-complete-display-prefix on
set keyseq-timeout 1
Control-l: clear-screen Weirdly enough this doesn't happen (as far as I can tell) on my laptop where I've turned off a few settings: complete -r
bleopt complete_auto_history=
bleopt complete_auto_complete= Outside of that, the only interesting stuff is my statusline and some vimode stuff in my opt info_display=bottom
function status/set-up-status-line {
opt keymap_vi_mode_show=
opt keymap_vi_mode_update_prompt=1
function ble/prompt/backslash:status/currentmode {
local mode; ble/keymap:vi/script/get-mode
case $mode in
(*n) ble/prompt/print $"-- NORMAL --" ;;
(*v) ble/prompt/print $"-- VISUAL --" ;;
(*V) ble/prompt/print $"-- V-LINE --" ;;
(*^V) ble/prompt/print $"-- V-BLOQ --" ;;
(*s) ble/prompt/print $"-- SELECT --" ;;
(*S) ble/prompt/print $"-- S-LINE --" ;;
(*^S) ble/prompt/print $"-- S-BLOQ --" ;;
(i) ble/prompt/print $"-- INSERT --" ;;
(R) ble/prompt/print $"-- RPLACE --" ;;
(^R) ble/prompt/print $"-- VPLACE --" ;;
(*) ble/prompt/print $"-- ?????? --" ;;
esac
# Change the default color of status line
case $mode in
*n)
color prompt_status_line fg=silver,bold
;;
i)
color prompt_status_line fg=magenta,bold
;;
*[vV^VsS^S])
color prompt_status_line fg=cyan,bold
;;
*[iR^R])
color prompt_status_line fg=red,bold
;;
*)
color prompt_status_line fg=silver,bold
;;
esac
}
opt prompt_status_line="\q{status/currentmode}"
}
blehook/eval-after-load keymap_vi status/set-up-status-line |
Hi, sorry for the delay, and thank you for your additional information. I still cannot reproduce the main problem. Maybe this is related to the way how you source opt info_display=bottom Where you defined
For this problem, I could reproduce a similar behavior by setting |
This is what loads ble: ble() {
[ -n "$SKIPBLE" ] && return
. "$BASH_CONFIG/ble.sh/out/ble.sh"
. "$BASH_CONFIG/blesh" # My .blerc
}
[ -z "$STARTXORG" ] && [ -t 0 ] && ble The whole idea is to allow the user to disable Ble in my dotfiles with a simply variable which is why that's there, furthermore it also doesn't load Ble on TTY's where Xorg will run, as that's just slowing down Xorg. In terms of the
The only variable that's set is |
Thank you for the information!
Ah, OK. You are sourcing
OK, so the code shown in your previous reply was just a part of your Also, if you have time, can you check if the problem reproduces without any settings in By the way, I think I'll define a function
OK. This value seems to be fine. Where do you set that variable? Is it a system-wide setting? Or is it a setting that you set inside your |
Yup
Yeah it's also aliased
It's part of my sourced files in my I also tested with only the |
OK, thank you for the additional information. I'll later continue to investigate the issue. Thank you |
ble version: 0.4.0-devel3+0506df2
Bash version: 5.1.4(1)-release
For some reason when running certain commands right after or during startup a long piece of code is echo'ed out. From the process title
for map in vi-insert vi-command emacs;
I can presume this has something to do with me having vimode enabled.This is the result of opening
fzf
:And also sometimes I get some rather more confusing text:
Here I'm trying to run
fc
but before clicking enter that gets outputted.This is all likely just some race conditions or whatever, but I thought I might want to open an issue as this happens quite frequently. Hoping for a fix or similar.
The text was updated successfully, but these errors were encountered: