The Linux Programming Interface as a university course text

https://man7.org/tlpi/academic/index.html

#HackerNews #LinuxProgramming #Interface #UniversityCourse #Textbook #OpenSource #Education #Programming

Actually, I already asked the question on the Gtk Discourse app, but I am posting it here on the fediverse in the hope that maybe a few more people will see it. I don’t mind if you answer in Discorse or here on the fediverse.

#tech #software #Linux #LinuxProgramming #Gtk #Gtk3

So my goal was to have a read-only GtkTextView widgets in which text can be arranged with layouts like grids, flowbox, vbox, or hbox layouts. Imagine my app to be a textual dashboard where end-users can decide how to place each dashboard widget, following the principles of tiling window managers.

I did not have much luck achieving this with GtkTextViews, so I tried a different approach of adding GtkLabels to GtkGrid and GtkFlowBox widgets all with the “selectable” property enabled. So far so good. However the default behavior for GtkGrid or GtkFlowBox seems to always highlight all of the text in the first selectable GtkLabel added to whatever container I am using. I would instead like for nothing to be selected until it is explicitly selected by the end-user.

The attached image shows what the window looks like when it is first made visible and before any user interaction — the upper-left GtkLabel is highlighted. I would like for this to not happen until the end-user drags over the widget with the mouse, but I am not sure how to go about it.

A different but related question: I would also like if the user drags beyond the boundary of a GtkLabel for the selection to continue to neighboring GtkLabel widgets, sort-of like how it works in a web browser. Is there an easy way to achieve this in Gtk without writing lots of custom drag event handlers for all the the widgets I construct in the UI?

Another great meeting — this time with Kaiwan N Billimoria, author of the excellent book Linux Kernel Programming, 2nd Edition:
https://www.amazon.com/gp/aw/d/1803232226/

As a reminder, Kaustubh Manglurkar from Packt had asked me to review this book a while ago. You can find my review in one of my earlier posts, or in the Editorial Review section on Amazon.

Highly recommended!

#LinuxKernel #LinuxProgramming #OpenSource #BookRecommendation #Packt

Somehow I made it the whole way. Looking at it now, it looks like instead of a four year degree, mine took like 14 years.

#computerengineers #hackers #selftaught #linuxprogramming #os2warp

Today, for the first time in a long while, I had occasion to write a C++ program with multithreading.

It provided a solution to a particular problem that was surprisingly easy and satisfying.

Linux has paradigms that really make other systems look like crap.

#LinuxProgramming #CPlusPlus

💡 LIVE NOW @ozoned ! 💡
Watch here: https://stream.ozoned.net/

#RustLang #LinuxProgramming #GamingOnLinux #AwkSed #DevOpsTalks #owncast #livestream #stream #selfhosted

🎬 💡 Live content alert! @ozoned is streaming on Owncast: https://stream.ozoned.net/

#RustLang #AwkSED #LinuxProgramming #GamingOnLinux #DevTalks #owncast #livestream #stream #selfhosted

Where does the tradition/idiom of using fd 9 as a lockfile come from? It's even in the man page: https://man7.org/linux/man-pages/man1/flock.1.html

I guess it's safe because the fd 9 is taken before the command itself is started, so you only risk overriding it in very exceptional cases where maybe you take multiple locks without making sure to use different fds? And it's also process-scoped since each process has its own fdtable.

Still feels a bit weird to statically allocate a specific fd like that.

#LinuxProgramming