-
-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neomutt true colors support #85
Comments
It's a lovely thought, but until ncurses/slang support true colour there's nothing we can (practically) do. When slang 2.3.1 is released, we can think about it. I hadn't read XVilka post for a while. It's nice to see some progress, e.g. the version of Vim I'm using supports true colour -- I never knew. |
Added this one in the gist as well. Yes, midnight commander devs are also waiting latest slang release to start working on true colour support. |
@flatcap What's blue-sky label for? And I think neovim is good all this while but now I found out that neovim uses stupid library that breaks some keys in st. (insert and delete keys) vim's better even though it is larger and slower and less feature (well I still won't use it) haha |
"blue-sky" is an optimistic idea -- possibly unobtainable. |
haha, unobtainable. |
How does vim manage the terminal control sequences then? Does it have its own hard coded tables for each terminal type? |
It must look them up. The output of Mutt, however, is too dependent on curses. |
Sure, I have seen curs_lib.c; I wouldn't have it any other way, it's good to know when the interface misbehaves it is a bug and not a flea :-) |
Btw, emacs did the same thing last time I looked (tinfo but not ncurses). |
I briefly looked at elinks for inspiration -- small, no curses, true-colour. |
@flatcap Yes, but somehow irssi manage to get true color even though they are using curses. |
ooh! good example. that's worth investigating. |
irssi doesn't use curses. curses doesn't support true colours. also, true colours are overrated :-) |
that's odd, it's certainly linked against ncurses. /me reckons that @ailin-nemui would prefer: |
@ailin-nemui -- Wow, you're Nei -- irssi's true-colour patches were your work. How does irssi do it? |
same as emacs and vim -- it would be enough to link irssi to tinfo on systems where this separation is provided. in the end you need to spew out the ANSI control codes to the terminal somehow (I heard @XVilka convinced slang to add true colour support...) |
Thanks. |
@ailin-nemui Yes, next slang release should be with truecolour support. |
@ailin-nemui Wow, amazing. @XVilka Nice. |
You can now see how it's landed/implemented in Midnight Commander - I hope this can be useful for you http://www.midnight-commander.org/changeset/682a5116edd20b8ba81743a1f7495c883b0ce644 |
(you can see that MC forward it to slang) |
It's a good idea, but it will require major changes to mutt. If someone volunteers to work on it we can re-open the issue. This issue has been added to a list of closed discussions and blue-sky ideas. |
duplicate of #5 |
The link in flatcap's close message to closed discussions and blue-sky ideas is broken. Where can we find this list now? |
Hi @R3load I have a plan for true-colour support 9and some proof-of-concept code), but there are higher priority tasks that need doing first. Unless someone volunteers to help. |
@flatcap Nowadays both slang and ncurses support true color. And you mentioned
Thanks! |
⬆️ ❓ |
There's no progress. I know what I'd like to do, but it's a big job and very low priority. There are two developers on NeoMutt, and we're really busy fixing and improving other areas of the code. If you want true-colour support: you need to help. I will make time to mentor new coders. Every bit of help, in whatever area, improves NeoMutt (and reduces my workload). |
A lot of terminal applications now supports true colors. mutt isn't supporting true colors yet, I wonder if neomutt will take the first step. https://dev.mutt.org/trac/ticket/3674
https://gist.github.com/XVilka/8346728 CC @XVilka
@flatcap What do you think?
The text was updated successfully, but these errors were encountered: