wez
commented
2 years ago I can't reproduce this. I wonder if this might be something weird with nushell?
Closed kuntau closed 2 years ago
wez
commented
2 years ago I can't reproduce this. I wonder if this might be something weird with nushell?
wez
commented
2 years ago Can you try to zero in on a repro scenario?
kuntau
commented
2 years ago I can't reproduce this. I wonder if this might be something weird with nushell?
This issue happened both with zsh & nutshell.
Nutshell have default configuration.
What do you mean by zero in reproduction scenario?
Thank you
wez
commented
2 years ago What are the minimum number of steps to deterministically make the problem happen?
This is the config I tried; this shows the process in the right status (which only updates ~1 every second), and redefines the key assignment to log the process name. Even quickly starting and exiting vim had it producing the correct results.
I made it run bash without running any rc files in order to isolate it from any config that might be in my shell rcfiles.
local wezterm = require 'wezterm'
function basename(s)
return string.gsub(s, "(.*[/\\])(.*)", "%2")
end
wezterm.on("update-right-status", function(window, pane)
window:set_right_status(basename(pane:get_foreground_process_name()))
end)
return {
default_prog = {"bash", "--norc"},
keys = {
{ key='h', mods="CTRL", action=wezterm.action_callback(function(win, pane)
wezterm.log_info("is_vim", pane:get_foreground_process_name())
end) },
}
}
default_prog = {"bash", "--norc"},
Weird, for some reason whenever use bash as default shell, wezterm can correctly show foreground process.
Have you tried from zsh or nu?
Thank you
edit:
Launching zsh with -f flag fixed the issue, so must be my configs somewhere, but nu with no config still can't detect foreground process.
Feel free to close this issue.
Thank you
rosshadden
commented
2 years ago @kuntau I've been trying to figure this out for months. Have you had any luck? I opened this issue with nushell: https://github.com/nushell/nushell/issues/5050 Nushell people tell me it's a terminal issue, but I've debugged this with help from @wez himself over IRC and we think it's a nushell issue. I have tried making changes in both, and compiling from source. But nothing I have tried has had any success and it's easily the most frustrating part of my workflow right now.
One thing I wanted to do is exactly what you are trying to do above, make mappings that navigate vim panes if in vim, otherwise wez panes. But another much more frustrating side effect of this problem or maybe some other problem is that opening new panes does not open in the current pane directory if you start wezterm with wezterm start, which is how I open all of my wezterm instances.
github-actions[bot]
commented
1 year ago I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What Operating System(s) are you seeing this problem on?
macOS
WezTerm version
wezterm 20220419-232436-924b63eb
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I had this issue for couple of month actually and I'm not sure how to debug it.
Weztermjust detect my shell as foreground process as shown in log/usr/local/bin/zshor/usr/local/bin/nueven I havevim,htop,pingor any other process running.I tried setting
default_progto different shell to no availTo Reproduce
I'm not sure to how reproduce it but here's my full config
Nothing out of ordinary config
Configuration
Expected Behavior
Wezterm should detect
vim/nvimis the foreground processLogs
This log is the output when I actually have other process running on top of shell
Anything else?
No response