'Hi ZyX
Thanks for reply so quick.
I think there is an issue on my environment.
I try 'ht update local-defaullt' and it switch to 'default' branch.
Then compile with --enable-termtruecolor
But the gui color only have black and white.
I am using this on iTerm 2.9x. with term type 'xterm-256color'
And on the same environment.
Commit '8abaeea8b2e5' is fine.
So the issue might between this commit to next merge.
2014-11-22 19:45 GMT+08:00 Павлов Николай Александрович <zyx.vim@gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On November 22, 2014 7:49:04 AM EAT, othree <othree@gmail.com> wrote:
>>ZyX於 2014年3月20日星期四UTC+8下午11時04分58秒寫道:
>>> On Thursday, March 20, 2014 9:03:34 AM UTC+4, Suresh Govindachar
>>wrote:
>>> > Oops! Sorry, just realized that what I wrote below might not be
>>what
>>> > you are asking about -- the subject says "24 bit colorscheme" and I
>>am
>>> > writing about 256 colors!
>>>
>>> ConEmu supports true color. The same exact sequences as konsole does.
>>Support was added shortly after I wondered whether it will be added, so
>>I assume author of ConEmu has already prepared his code for something
>>like this.
>>
>>Hi ZyX
>>
>>Are your still maintain this feature?
>>I found the branch '24-bit-xterm' is dead on BitBucket now.
>>And the last commit can support 24 bit color well is '8abaeea8b2e5'.
>>Just want to make sure is there any update on this.
>>
>>
>>Thanks
>>
>>
>>--
>>--
>>You received this message from the "vim_use" maillist.
>>Do not top-post! Type your reply below the text you are replying to.
>>For more information, visit http://www.vim.org/maillist.php
>>
>>---
>>You received this message because you are subscribed to the Google
>>Groups "vim_use" group.
>>To unsubscribe from this group and stop receiving emails from it, send
>>an email to vim_use+unsubscribe@googlegroups.com.
>>For more options, visit https://groups.google.com/d/optout.
>
> It is not "dead", it is "finished". I have merged this bookmark into local-default bookmark which I am using and local-default bookmark is being periodically merged with upstream bookmark which is periodically updated to upstream tip. If there were any merge conflicts with upstream I most likely would've updated 24-bit-xterm, but currently there is not much sense in this action.
>
> Currently I am using this functionality and it works just fine.
> -----BEGIN PGP SIGNATURE-----
> Version: APG v1.1.1
>
> iQI1BAEBCgAfBQJUcHc/GBxaeVggPHp5eC52aW1AZ21haWwuY29tPgAKCRCf3UKj
> HhHSvq3TD/wOOSLTWvvKIrl0K+IXUACaRxDCK2CvhSLeTXL5xsG7QE1MbpgLtQrU
> t7N4F6gCohQIRd7ttJ/jmV6+p7CLkaQEUYxpIjDsx6SngY7rrZoiEsNfv2QEh9q5
> SSE7toU633TA3kGe28ODBZ4xdxNQdzWISSt/5IlGnR8KIS9riXFkNP+XBz2u9m/5
> FK+C40e0jHPIApiB4NNoKoX66LH5N744rnW3Ydrf9KnlVqmMtEArNGufdAPF5Tf6
> zxotfR1KxiNy3W0qMpDGb85wTD821EfglazxYf6E7yj4flssrqvXEquOqHtzQ926
> geVsG8pbTDhhuCUE8DpuVtEOAaCzZGwdrj3tPqoVvHDjSRBMTcruwZlIS4gOwLGq
> eRMH3ww2xPz+/NQX+2hz/XbNs1y2PZMAhNWMuR1FkR4YWCYbmTOpiIvi10ZA8/HA
> OJa2h4pFALk4VJQO5WPkxR/XI2jzxt448ApnQ/UIUtIOpY4rZ5Bx5Igqz+lFV+oo
> yktZT3Mr9xeP4QaaqKRWj1OQqlkg+Z11tRCD2He96MF5+XCAQ33ASo5KWy8PKW1e
> 1VQfFe+q1DHhHuqdISC0H8t9rhjgsmHIZ58MSrDlvhx/cDhL+Dx5gTKg8V3MAEGQ
> Si/ZspH8rlFHjuxypFFIFiisWpRiMOkoN3cl72Slibvw7S9AO09oJA==
> =U9xn
> -----END PGP SIGNATURE-----
>
--
OOO
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment