summaryrefslogtreecommitdiff
path: root/kike-replies
diff options
context:
space:
mode:
authorPřemysl Janouch <p.janouch@gmail.com>2016-04-21 23:58:44 +0200
committerPřemysl Eric Janouch <p@janouch.name>2020-10-04 10:08:30 +0200
commit9819b75b643d60e931ae2a7758b35000e806a925 (patch)
tree2f69daaf52e51987fdbad73734a7d122f8325570 /kike-replies
parentf716e7601fa32947e380e7d1f7dd1433d2818a55 (diff)
downloadxK-9819b75b643d60e931ae2a7758b35000e806a925.tar.gz
xK-9819b75b643d60e931ae2a7758b35000e806a925.tar.xz
xK-9819b75b643d60e931ae2a7758b35000e806a925.zip
degesch: make the unread marker look a bit fancier
Upstreamed after who knows how long, in a slightly modified form. The marker looks fairly ugly without this and defaults should be desirable. It's possible to get the previous behaviour by resetting the separator character in the configuration to an empty string. It might be a better idea in general to just disallow this value with a special validation callback, so that there's only one way to do it. However given that without fancy-prompt.lua, an optional plugin, the long line stands out considerably, it might actually be a good idea to keep the old behaviour as the default. I'm torn. Right now we don't care about the situation where the string occupies more than one terminal cell or is some Unicode BS. User's problem.
Diffstat (limited to 'kike-replies')
0 files changed, 0 insertions, 0 deletions