movq @www.uninformativ.de
 (3d ago)

(#4b4ypwa) @lyse@lyse.isobeef.org Unix terminals are quite limited in that regard. šŸ«¤ You know how Ctrl works? The XOR 0x40 thing? And Alt doesnā€™t exist at all, itā€™s just a prefixed ESC byte.

I was surprised to see curses knowing about ā€œShift+Tabā€, wondering how that is supposed to work. Well, itā€™s an escape sequence, of course (depending on the terminal, of course).

#5pxodta
lyse @lyse.isobeef.org
 (3d ago)

Here am I looking at the different tcell.Key constants and typing different key combinations in the terminal to see the generated tcell.EventKeys in the debug log. Until I pressed Ctrl+Alt+Backspaceā€¦ :-D Yep, suddenly there went my Xā€¦

So far, it appears as if I can have either only Ctrl or Alt as modifiers. But not in combination. And Shift is just never ever set at all. Interesting.

#4b4ypwa
prologic @twtxt.net
 (5d ago)

This week, Mu (Āµ) get s bit more serious and starts to refactor the native backend (a lot). Soonā„¢ we will support darwin/arm64, linux/arm64 and linux/amd64 (Yes, other forms of BSD will come!) ā€“ Mu (Āµ) also last week grew concurrency support too! šŸ¤£

#4hzbyjq
lyse @lyse.isobeef.org
 (6d ago)

Iā€™m trying to implement configurable key bindings in tt. Boy, is parsing the key names into tcell.EventKeys a horrible thing. This type consists of three information:

  1. maybe a predefined compound key sequence, like Ctrl+A
  2. maybe some modifiers, such as Shift, Ctrl, etc.
  3. maybe a rune if neither modifiers are present nor a predefined compound key exists

Itā€™s hardcoded usage results in code like this:

func (t *TreeView[T]) InputHandler() func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
    return t.WrapInputHandler(func(event *tcell.EventKey, setFocus func(p tview.Primitive)) {
        switch event.Key() {
        case tcell.KeyUp:
            t.moveUp()
        case tcell.KeyDown:
            t.moveDown()
        case tcell.KeyHome:
            t.moveTop()
        case tcell.KeyEnd:
            t.moveBottom()
        case tcell.KeyCtrlE:
            t.moveScrollOffsetDown()
        case tcell.KeyCtrlY:
            t.moveScrollOffsetUp()
        case tcell.KeyTab, tcell.KeyBacktab:
            if t.finished != nil {
                t.finished(event.Key())
            }
        case tcell.KeyRune:
            if event.Modifiers() == tcell.ModNone {
                switch event.Rune() {
                case 'k':
                    t.moveUp()
                case 'j':
                    t.moveDown()
                case 'g':
                    t.moveTop()
                case 'G':
                    t.moveBottom()
                }
            }
        }
    })
}

This data structure is just awful to handle and especially initialize in my opinion. Some compound tcell.Keys are mapped to human-readable names in tcell.KeyNames. However, these names always use - to join modifiers, e.g. resulting in Ctrl-A, whereas tcell.EventKey.Name() produces +-delimited strings, e.g. Ctrl+A. Gnaarf, why this asymmetry!? O_o

I just checked k9s and theyā€™re extending tcell.KeyNames with their own tcell.Key definitions like crazy: https://github.com/derailed/k9s/blob/master/internal/ui/key.go Then, they convert an original tcell.EventKey to tcell.Key: https://github.com/derailed/k9s/blob/b53f3091ca2d9ab963913b0d5e59376aea3f3e51/internal/ui/app.go#L287 This must be used when actually handling keyboard input: https://github.com/derailed/k9s/blob/e55083ba271eed6fc4014674890f70c5ed6c70e0/internal/ui/tree.go#L101

This seems to be much nicer to use. However, I fear this will break eventually. And itā€™s more fragile in general, because itā€™s rather easy to forget the conversion or one can get confused whether a certain key at hand is now an original tcell.Key coming from the library or an ā€œextendedā€ one.

I will see if I can find some other programs that provide configurable tcell key bindings.

#sczoyta
lyse @lyse.isobeef.org
 (6d ago)

(#2puspya) @movq@www.uninformativ.de Sorry, I meant the builtin module:

$ python3 -m pep8 file.py
/usr/lib/python3/dist-packages/pep8.py:2123: UserWarning: 

pep8 has been renamed to pycodestyle (GitHub issue #466)
Use of the pep8 tool will be removed in a future release.
Please install and use ```pycodestyle` instead.

  $ pip install pycodestyle
  $ pycodestyle ...

I canā€™t seem to remember the name pycodestyle for the life of me. Maybe thatā€™s why I almost never use it.

#2jboz4q
movq @www.uninformativ.de
 (1w ago)

Since I used so much Rust during the holidays, I got totally used to rustfmt. I now use similar tools for Python (black and isort).

What have I been doing all these years?! I never want to format code manually again. šŸ¤£šŸ˜…

#pebgp3a
movq @www.uninformativ.de
 (1w ago)

Okay, I had heard of ā€œRiverā€ before but I was not aware of this:

https://codeberg.org/river/river

River defers all window management policy to a separate window manager implementing the river-window-management-v1 protocol. This includes window position/size, pointer/keyboard bindings, focus management, window decorations, desktop shell graphics, and more.

This sounds promising and it follows the old X11 model. River does all the nasty Wayland work and I can make just the WM? šŸ¤”šŸ¤Æ

#74u6qdq
lyse @lyse.isobeef.org
 (1w ago)

It drizzled all morning when we picked up the old christmas trees in town with the scouts. Right after lunch the snow storm suddenly hit and dumped three centimeters of snow in just 15 minutes. I cycled home in these crazy conditions, freezing rain hammered my face. As soon as I arrived, it stopped. Itā€™s now down to drizzling again.

All my soaked gear is now hung up to dry. The next 11 months, Iā€™m going to find needles over needles in all kind of impossible places.

#s2hgrfa
movq @www.uninformativ.de
 (1w ago)

(#g34eztq) @lyse@lyse.isobeef.org Itā€™s not super comfortable, thatā€™s right.

But these mouse events come with a caveat anyway:

ncurses uses the XM terminfo entry to enable mouse events, but it looks like this entry does not enable motion events for most terminal emulators. Reporting motion events is supported by, say, XTerm, xiate, st, or urxvt, it just isnā€™t activated by XM. This makes all this dragging stuff useless.

For the moment, I edited the terminfo entry for my terminal to include motion events. That canā€™t be a proper solution. Iā€™m not sure yet if Iā€™m supposed to send the appropriate sequence manually ā€¦

And the terminfo entries for tmux or screen donā€™t include XM at all. tmux itself supports the mouse, but Iā€™m not sure yet how to make it pass on the events to the programs running inside of it (maybe thatā€™s just not supported).

To make things worse, on the Linux VT (outside of X11 or Wayland), the whole thing works differently: You have to use good old gpm to get mouse events (gpm has been around forever, I already used this on SuSE Linux). ncurses does support this, but this is a build flag and Arch Linux doesnā€™t set this flag. So, at the moment, Iā€™m running a custom build of ncurses as a quick hack. šŸ˜… And this doesnā€™t report motion events either! Just clicks. (I donā€™t know if gpm itself can report motion events, I never used the library directly.)

tl;dr: The whole thing will probably be ā€œkeyboard firstā€ and then the mouse stuff is a gimmick on top. As much as Iā€™d like to, this isnā€™t going to be like TUI applications on DOS. Iā€™ll use ā€œWindowsā€ for popups or a multi-window view (with the ā€œWindowManagerā€ being a tiny little tiling WM).

#wulnloq
prologic @twtxt.net
 (1w ago)

(#q33dfjq) Most of it should work on other platforms, the bytecode VM that is. You may run into some platform quirks though that rely on syscall() ā€“ Let me know what you run into and Iā€™ll try to fix them nw. The problem right now is I havenā€™t even begun to start work on another platform/architecture yet.

#y5s2uvq
prologic @twtxt.net
 (1w ago)

Mu (Āµ) is coming along really nicely šŸ¤£ Few things left to do (in order):

  • Finish the concurrency support.
  • Add support for sockets
  • Add support for linux/amd64
  • Rewrite the heap allocator
  • Rewrite Mu (Āµ) in well umm Mu (Āµ) šŸ˜…

Hereā€™s a screenshot showing off the builtin help():

#q33dfjq
lyse @lyse.isobeef.org
 (1w ago)

(#g34eztq) @movq@www.uninformativ.de Oh, I see. Unfortunately, there seems to be no box drawing character for a corner with a diagonal line. Indeed, this is probably the best you can do.

Is the single character enough to hit it comfortably with the mouse, though? Maybe one additional to the left and above could be something to think about. Not sure. Of course this complicates it a bit more. Personally, I like fullscreen windows, so Iā€™m definitely the wrong guy to judge this or even comment on. :-)

#pjdqhsq
movq @www.uninformativ.de
 (1w ago)

(#javxoxa) @lyse@lyse.isobeef.org Ah, the lower right corner is different on purpose: Itā€™s where you can click and drag to resize the window. https://movq.de/v/cbfc575ca6/vid-1767977198.mp4 Not sure how to make this easier to recognize. šŸ¤” (Itā€™s the only corner where you can drag, btw.)

@bender@twtxt.net Seriously, if I ever get a CRT monitor again, I want it to be an amber one and then hook it up to some 8086. šŸ˜… Only problem is that this stuff is expensive as hell now ā€¦

#g34eztq