fork/wezterm
git clone https://git.julia.blue/fork/wezterm
680ef1023
termiz-0.23.3
1name : Bug Report Form 2description : Create a report to help us improve 3labels : [ bug , needs:triage ] 4assignees : [] 5body : 6- type : dropdown 7id : os 8attributes : 9label : What Operating System(s) are you seeing this problem on? 10multiple : true 11options : 12- Windows 13- Linux X11 14- Linux Wayland 15- macOS 16- FreeBSD X11 17- FreeBSD Wayland 18validations : 19required : true 20- type : textarea 21id : window_manager 22attributes : 23label : Which Wayland compositor or X11 Window manager(s) are you using? 24description : | 25If running on a unix system, please include the name and version of the compositor/WM. 26Windows and macOS typically can leave this blank, but if you are using additional window 27management software on top of the standard for those systems, please indicate that here. 28placeholder : "ex: Sway, Mutter, wayfire, i3." 29- type : input 30id : version 31attributes : 32label : WezTerm version 33description : | 34Please run `wezterm -V` and include its output here. 35If you installed the flatpak version of wezterm, please consider trying 36the native package format for your system and comparing the behavior, 37as flatpak runs in an isolated sandbox that can prevent some functionality 38from working fully. 39placeholder : "ex: 20210816-085256-935c1f48" 40validations : 41required : true 42- type : dropdown 43id : triednightly 44attributes : 45label : Did you try the latest nightly build to see if the issue is better (or worse!) than your current version? 46options : 47- Yes, and I updated the version box above to show the version of the nightly that I tried 48- No, and I'll explain why below 49validations : 50required : true 51- type : textarea 52id : description 53attributes : 54label : Describe the bug 55description : A clear and concise description of what the bug is 56placeholder : Tell us what happened 57validations : 58required : true 59- type : textarea 60id : to_repro 61attributes : 62label : To Reproduce 63description : Steps to reproduce the behavior 64placeholder : | 65Please include as much information as possible that can help to reproduce and 66understand the issue. 67- type : textarea 68id : config 69attributes : 70label : Configuration 71description : | 72Please include the relevant section(s) of your `wezterm.lua` configuration file. 73You can enter "no config" if the issue happens without you having made a config file. 74validations : 75required : true 76- type : textarea 77id : expected 78attributes : 79label : Expected Behavior 80description : A clear and concise description of what you expected to happen 81- type : textarea 82id : logs 83attributes : 84label : Logs 85description : | 86If possible, activate the Debug Overlay by pressing CTRL-SHIFT-L and then copy 87and paste the log lines in here. If you launched wezterm from 88the command line, copy and paste that output here. 89You can also find log files in `$XDG_RUNTIME_DIR/wezterm` on unix systems, 90or `$HOME/.local/share/wezterm` on macOS and Windows systems. 91placeholder : | 9209:27:26.703 INFO wezterm_gui::termwindow > OpenGL initialized! NVIDIA GeForce GT 1030/PCIe/SSE2 4.6.0 NVIDIA 470.57.02 is_context_loss_possible=false wezterm version: 20210816-085256-935c1f48 93- type : textarea 94id : other 95attributes : 96label : Anything else? 97description : | 98 Add any other context about the problem here. You can attach screenshots by clicking 99 this area to highlight it and then drag the files in, or just paste the image from 100 the clipboard to upload it.