![]() ![]() Let's try a Bayesian approach: considering you have been proved wrong, you should update your priors and consider the likelihood of being wrong again is greater than me being wrong, since I have 1) quite an experience with sixels 2) so far I've been proven right. I can't hold your hand while you install msys2 so you realize yourself you were wrong, just like you did with the 24 bit colors which you wrongly assumed to not be supported by sixels. > Because so far you have not adequately explained what is going on here, or corrected any misconceptions, or helped to fix anything Then if you are speaking in good faith, we will talk again. I HAVE TOLD YOU AT LEAST 4 TIMES: YOU NEED TO USE A STATE OF THE ART TERMINAL TO FIRST CORRECT YOUR MISCONCEPTIONS. > So again, please help out with fixing this for me if you know how. I've given you a step-by-step guide to try the best terminal there is. OMG, I spoke too fast, there you go again! > But that's still terrible, and every Sixel implementation I've ever used has spit out dithered images ![]() > It seems I was wrong, it supports 8-bit color, not 6-bit color.Ī positive first step is knowing when to admit error. I suspect other projects wouldn't go for that. ![]() If GIMP was attempting to pressure other projects to output BMP files then yes, that would be a problem. They don't care about the underlying formats. gimp, paint and others support many formats. >What you've written makes about as much sense as saying a drawing program should stop trying to support BMP format since it will have to be replaced down the line by JPG or PNG. If you could just explain what that terminal does that's special so that it could be implemented in other terminals, or show a video, that would help. I'm not going to dual boot Windows or use a VM just to use a terminal emulator for a couple minutes, sorry. You've also got your pick of emulators, from parallels to vmware, if you roll that way. You may be in the best position to do that too. So all paths point towards needing to make some new protocol for this. If I'm confused then you could be in a great position to help me out, so please explain.Īnd there are also other problems with the iterm escape sequences that I suspect will prevent you from correctly implementing them in tmux (see here: ). And even the various libsixel examples seems to show dithering: Because so far you have not adequately explained what is going on here, or corrected any misconceptions, or helped to fix anything that is wrong with these terminals. So again, please help out with fixing this for me if you know how. The only terminal that is able to display full color images for me is iTerm, using the iTerm escape sequences, which are different escape sequences from sixel. But that's still terrible, and every Sixel implementation I've ever used has spit out dithered images. Am I reading this incorrectly? It seems I was wrong, it supports 8-bit color, not 6-bit color. On_project_exit: tmux -CC attach -t project_name # Attach to tmux with custom options (iTerm2 tmux integration) # Disable default attaching to use custom on_project_exit attach # Specifies (by index) which pane of the specified window will be selected on startup ~/.config/tmuxinator/project_name.yml name: project_name Here’s my old iTermocil project vs the new Tmuxinator project: I’ve taken this opportunity to switch to tmux/tmuxinator, using iTerm2 tmux integration to achieve the same native iTerm2 panels and tabs as iTermocil but with the session saving and other benefits of tmux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |