Yes, Trelby currently lacks this. Filed
https://github.com/oskusalerma/trelby/issues/136
A thinner cursor option would be trivial to add. A blinking cursor
would need the addition of a timer, and some optimizations to screen
update code. Would adding just a thin cursor make things easier for
you.. or is blinking cursor a requirement?
> 2) I have the same problem with the way Trelby highlights blocks of text.
> For one, the highlight effect is just too light and subtle, under certain
> lighting conditions I can't see it at all.
This is easy to fix. Under File> Settings >Change >Colors, change to
selection color to something darker.
If the default isn't good on some monitors, we may need to change the
default also too something darker.
> Secondly, it keeps befuddling my
> learned instincts. I instinctively expect to be able to highlight a block of
> text and then type destructively right over it, but I keep being called up
> short when Trelby won't do that. (I also expect to be able to click multiple
> times on a word to highlight it, though that's not such a big deal.)
>
Filed https://github.com/oskusalerma/trelby/issues/137
> I'm not criticizing your implementation nor the philosophy behind it,
> there's a lot of merit to the way you've done it. There's also a lot of
> merit to the Dvorak keyboard, but I don't use it because I just can't get
> used to it.
>
Yup, thanks. Usability suggestions are very welcome. Many of my recent
fixes have been to change Trelby's default UI behavior to be similar
to any other text editor.
~Anil
This was simple enough to implement:
Patch : https://github.com/oskusalerma/trelby/pull/138/files
Osku: Why exactly do we have separate keyboard selection behaviour
(using arrow keys to extend selection).. is it because that's how it
was implemented? I would like to change that as well (to
shift+arrowkeys) just like with any other editor.
~Anil
Thin cursor patch also in the queue.
Screenshot of new cursor:
https://github.com/oskusalerma/trelby/issues/136#issuecomment-4598683
~Anil
Osku: Why exactly do we have separate keyboard selection behaviour
(using arrow keys to extend selection).. is it because that's how it
was implemented? I would like to change that as well (to
shift+arrowkeys) just like with any other editor.
~Anil
Err.. I meant different selection behavior. From the replies on the
bug, I gather it was because this is also the behavior on emacs? (I
haven't used it, being a steadfast vim user).
On the latter, I was being thickheaded. Of course we already support
that, and I use it all the time.
~Anil