Open NewUserHa opened 6 years ago
And what is the question? Bad Issues
sorry, but I don't admit/think this is a bad issue/question.
after I read the documents[https://conemu.github.io/en/VimXterm.html#vim-color-scheme], I want to know what conemu do to the console, and am I able to configure some settings to adjust conemu's behave.
from the document, 1."Selected Vim color scheme must be prepared specially for Xterm color." 2."Since ConEmu build 170730 all mouse events are posted as XTerm sequences when XTerm mouse mode was requested by console application."
why can't I just disable xterm color to make other things work right if I totally don't use mouse.
this is a terminal, right? I think conemu just like the tmux on windows, and is a great tool/terminal. why does it mess up color, mouse things? these are not documented
ok. I might mean "do you have time to add more details to conemu's documents ?" @Maximus5
I spent a lot of time writing docs. But some things obvious to me (as an author) may be missed from documentation, or they are not easily accessed via hyperlinks or so. Each page has "suggest better edit" at the bottom and PR are appreciated.
The wiki page related to Vim (and actually all third party tools) is my gesture of goodwill, the place where my users may find some hints how to configure their console tools.
You are right, ConEmu is a terminal, it is not required to turn on xterm colors in Vim. But why do you think it's a ConEmu problem?
Enabling XTerm in ConEmu (some techinfo is here) just tells the terminal to post keyboard and mouse events as XTerm sequences. Simple. Nothing else.
Unless you enable XTerm in console application, this console application will not use XTerm/ANSI sequences to output colored text. But in most applications enabling XTerm mouse/keyboard means enabling XTerm colors. Logical.
User is not obliged to enable XTerm to get console application working with mouse. Just take a look at Far Manager - properly written Windows console application using WinAPI.
why does conemu show incorrect color(I guess it's still xterm 256) after disabling inject, xterm, true color mode the three options?
If you cut the monitor cable, the monitor would not show anything. Unfortunately. TechInfo here: https://conemu.github.io/en/ConEmuHk.html
I read the docs you linked now. I mean I tried to turn off xterm mode(inject on & xterm off) in a console application(vim?), but failed. how can I disable it to make color right if I don't want to mouse work
I never mean it's conemu's problem. conemu is a great program. I just hope it will be better.
thank your reply.
I'm lost.
What do you want?
a) let Vim write ANSI sequences to output colors? b) let Vim receive ANSI sequences as mouse and keyboard events?
But in most applications enabling XTerm mouse/keyboard means enabling XTerm colors. Logical.
I want to know the way that document now hasn't, disabling XTerm and letting vim's non-XTerm colors works if users don't use mouse.
Is Conemu able to do that right now? sorry for confusing.
disabling XTerm and letting vim's non-XTerm colors works if users don't use mouse.
I completely can't understand you. What is your problem? Just use Vim with default config.
As I said before:
sorry.
No description. So I suppose you showed screenshot with non-XTerm colors in cmder, and with-XTerm colors in Vim. By XTerm colors here I mean 256 (or higher) color palette.
That is correct. So, what do you want to configure?
Versions
ConEmu build: 171025 x64 OS version: Windows 10.0.10586.x64 Used shell version: CMD
Problem description
I already read some documents about color and mouse event(googling didn't give me that page when searched with like 'conemu vim mouse', so I opened last issue).
why does conemu show incorrect color(I guess it's still xterm 256) after disabling inject, xterm, true color mode the three options? I heard few shell support mouse event but why does conemu seem like use xterm as its only or primary? shell/profit? is this very necessary? xterm even is not in term list in help of vim. vim help: 'term' string (default is $TERM, if that fails: ¦ in the GUI: "builtin_gui" on Amiga: "amiga" ¦on BeOS: "beos-ansi" ¦ on Mac: "mac-ansi" ¦on MiNT: "vt52" ¦ on MS-DOS: "pcterm" ¦on OS/2: "os2ansi" ¦on Unix: "ansi" ¦ on VMS: "ansi" ¦ on Win 32: "win32")
no offense. Thanks!