James C.

My minimal fix is here: https://github.com/xournal/xournal/pull/6 Imagining that Xournal code-fix is my current form of entertainment, and that I have some ideas about variable-sized cursors, what bug would you prefer that I was looking at?

Thank you, Denis. I've adjusted my message most of the way toward yours: https://github.com/JamesC1/xournal-01/commit/e2eb38b3257d3e8f7c6d2df57b8fe4610999d4f9 The apostrophe breaks vim syntax highlighting, so I've expanded doesn't. I don't know whether gtk2-devel implies pkgconfig in my packaging. I have not yet got around to installing it. Your Xournal is very different from the one that I started with. This change: https://github.com/xournal/xournal/commit/3e59ba847964d7648ac8df58aed1f64f0150dd7b...

Hi Denis, Thanks for getting back to me. I have a few responses, with the last one first. Most people won't develop Xournal, so they will never run into this problem. Of the people who run some linux distribution and do, everyone will run into it, whose distribution does not come with pkgconfig or the correct replacement; ie everyone who's running a distribution which was initially intended for desktop users, and they are now able, at least in principle, to expand it into a software development platform....

I have pull-requested a fix that makes sense to me, which is one line in configuration.ac, to abort the autogen.sh if the offending macro is undefined. Does it make sense to you-all? https://github.com/xournal/xournal/pull/5

On my platform (Trisquel 11, Xournal 0.4.8.2016), the active spot on the text cursor is (correctly) in the vertical middle, and the top left corner of the text box is immediately to the right of the I-beam. On my platform, the largest cursor is 256x256, so in principle, there could be a variety of text cursors, depending on the text size and magnification, including something to indicate text larger than the largest cursor. I think that, to make this sensible, they would have to be procedurally generated....