vim / taskwarrior possible?

[joweka]

hi,

got a Kobo Aura Edition 2 v1 today from a friend. Trying out the 'Konsole' in pbchess I thought how nice it would be to have my main productivity tools at the time, 'vim' and 'taskwarrior', running on e-Ink.

'vi' seems to run in 'Konsole' but the interface is verry buggy (probably Konsole does not interpret ANSII sequences)..

how difficult would it be to have a completely working 'bash'-shell as a plugin? or at least vim, which could also be used as some kind of GUI for taskwarrior? I'm thinking of something similar to 'termux' on Android.
or does something like this already exist, could not find anything about it other than installing a full blown Debian distro where I'm not sure it will run on my device.

greetings,
joweka

[joweka]

update:

found inkvt ( https://github.com/llandsmeer/inkvt ) and managed to compile it with the ko-reader toolchain ( https://github.com/koreader/koxtoolchain)

so vi is kind of running though without an OTG keyboard it's a little bit hard to use

still I can't compile taskwarrior ( https://taskwarrior.org/download/ )

I set the environment with

source refs/x-compile.sh kobo env

and in the taskwarrior directory i ran

cmake -DCMAKE_BUILD_TYPE=release .

but cmake exits with the following errors:

cc: error: unrecognized command-line option '-mfpu=neon'
cc: error: unrecognized command-line option '-mfloat-abi=hard'
cc: error: unrecognized command-line option '-mthumb'

any suggestions how to fix that? I guess the toolchain is in some way not up-to-date with the taskwarrior code or something?

[NiLuJe]

Cross-compilation is not for the faint of heart.

CMake is ... hilariously tricky to deal with at the best of times.

I'll let you figure out what happens when you combine the two .

As a rather strong hint, look at: https://github.com/koreader/koreader...akeCross.cmake

[NiLuJe]

Not familiar with taskwarrior, but cross-compiling vim should be fairly easy, on the other hand.

I've settled for nano instead in KoboStuff because it's slightly more self-contained, which is helpful because FAT32 is the worst. (It's also slightly less arcane to newcomers, but let us not delve into that any further ^^).

[joweka]

Not familiar with taskwarrior, but cross-compiling vim should be fairly easy, on the other hand.

thanks for pointing this out, it motivated me to check my build environment and I enventually found out I had to set the CC/GCC env variables with prefix

arm-kobo-linux-gnueabihf-

still having issues with missing libraries/headers but maybe I can fix that with enough time

[pascal jakobs]

Originally Posted by joweka

update:

found inkvt ( https://github.com/llandsmeer/inkvt ) and managed to compile it with the ko-reader toolchain ( https://github.com/koreader/koxtoolchain)

so vi is kind of running though without an OTG keyboard it's a little bit hard to use

I'd like to use this terrific terminal on my clara but the labels of the OSK are far too tiny to be usable. I join a screen dump that shows the keyboard size of the built in browser and inkvt's. No contest.
I'd love to have the knowledge to fix it myself ...
Could somebody give me a direction please
Thanks for help

[NiLuJe]

That'd take basically re-implementing the way the OSK is currently drawn ;o).

(It's currently poking directly at the font data and unpacking the bitmap by hand, it should be possible to let FBInk do the drawing, and that could include scaling, you'll "just" have to play with computing exact positioning properly).

Or, keep doing it by hand and also (re)implement scaling .

[pascal jakobs]

Thanks you,
I'm going to read the source and try to understand what you said.
On another hand, don't you think it could be worth adding it to your kobostuff?
Have a nice day

[NiLuJe]

Not until it sees wider testing .

[joweka]

by the way, since we're talking about keyboards, has anyone managed to integrate the USB host driver of the XSoar kernel ( https://github.com/hjr/XCSoar-Kobo-Build/ ) into a firmware patch or something so one could use that for others things than flying around?

sadly I'm not into compiling kernels all that much so I have to ask ...

would be a great improvement for my future low-power-sunlight-agnostic-outdoor-commandline-producitvity-thingy which I think this kobo could/should be

[NiLuJe]

Possibly unnecessary on newer devices? (c.f., https://www.mobileread.com/forums/sh...d.php?t=340418).

[joweka]

already tried that one, but after

mount -t debugfs none /sys/kernel/debug
echo host > /sys/kernel/debug/ci_hdrc.0/role

it tells me

-ash: can't create /sys/kernel/debug/ci_hdrc.0/role: nonexistent directory

in dmesg, the following appears when pluggin' in the keyboard

PMU:charger_adp_isr
PMU:charger_usb_isr
PMU:charger_in_isr
PMU:charger_irq_work In
PMU:_config_ricoh619_charger_params set SDP charging.
usb plugged 1-0
PMU:charger_irq_work Out

testet with the latest avaiilable firmware, 4.26.16704

maybe they did not include the OTG drivers in the release for the 'Mark 6' hardware?