[GH-ISSUE #472] Improve support for using colors in autocomplete input fields? #342

New issue

Closed

opened 2026-03-04 01:04:09 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:04:09 +03:00

Owner

Originally created by @khughitt on GitHub (Jul 18, 2020).
Original GitHub issue: https://github.com/rivo/tview/issues/472

One more quick idea --

Would it be possible to modify autocomplete to make it easier to include choices which are colored differently?

Currently, autocomplete display text in different colors just fine, however, to actually match one of the words, you have to type the color expression in the input field.

For example, for the string "[#ff0000] word" to match, you have to start with the "[".

It would be nice if there was an option to indicate that colors should still be displayed in the autocomplete options, but otherwise stripped from the strings that are being matched against.

Another possible approach would be to allow Maps to be used, with each entry corresponding to a (label, text) pair.

Originally created by @khughitt on GitHub (Jul 18, 2020). Original GitHub issue: https://github.com/rivo/tview/issues/472 One more quick idea -- Would it be possible to modify autocomplete to make it easier to include choices which are colored differently? Currently, autocomplete display text in different colors just fine, however, to actually match one of the words, you have to type the color expression in the input field. For example, for the string "[#ff0000] word" to match, you have to start with the "[". It would be nice if there was an option to indicate that colors should still be _displayed_ in the autocomplete options, but otherwise stripped from the strings that are being matched against. Another possible approach would be to allow Maps to be used, with each entry corresponding to a `(label, text)` pair.

kerem closed this issue

2026-03-04 01:04:09 +03:00

kerem commented

2026-03-04 01:04:10 +03:00

Author

Owner

@khughitt commented on GitHub (Jul 18, 2020):

Nevermind!

Just realized this was my fault for using strings.HasPrefix() in the inputField.SetAutocompleteFunc() function.

Switching to a different approach to matching fixed the issue.

Please ignore :)

@khughitt commented on GitHub (Jul 18, 2020): Nevermind! Just realized this was my fault for using `strings.HasPrefix()` in the `inputField.SetAutocompleteFunc()` function. Switching to a different approach to matching fixed the issue. Please ignore :)

kerem commented

2026-03-04 01:04:10 +03:00

Author

Owner

@khughitt commented on GitHub (Jul 18, 2020):

Reopening for different but related issue (still having to do with color + autocomplete support):

when navigating through autocomplete choices, colors and formatting are rendered as expected, however, in the text that is shown in the inputField, the unformatted text (e.g. [#ff0000][::b]match...) is shown instead of the rendered text.

@khughitt commented on GitHub (Jul 18, 2020): Reopening for different but related issue (still having to do with color + autocomplete support): when navigating through autocomplete choices, colors and formatting are rendered as expected, however, in the text that is shown in the inputField, the unformatted text (e.g. `[#ff0000][::b]match...`) is shown instead of the rendered text.

kerem commented

2026-03-04 01:04:10 +03:00

Author

Owner

@rivo commented on GitHub (Sep 15, 2020):

That's actually a bug. Colour tags should not appear in the input field when you make an autocomplete selection. I fixed this in the latest commit.

@rivo commented on GitHub (Sep 15, 2020): That's actually a bug. Colour tags should not appear in the input field when you make an autocomplete selection. I fixed this in the latest commit.

kerem commented

2026-03-04 01:04:11 +03:00

Author

Owner

@khughitt commented on GitHub (Sep 15, 2020):

Thanks for the fix! It's much appreciated.

@khughitt commented on GitHub (Sep 15, 2020): Thanks for the fix! It's much appreciated.

kerem referenced this issue

2026-03-04 01:08:33 +03:00

[PR #342] [CLOSED] Fix: non-scrollable textview has strange behavior #916