The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
The recording didn’t turn out so well, because … traffic is still louder. And what’s up with that obnoxious beeping? Meh.
https://movq.de/v/84f2866ded/noise.ogg
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I could get rid of the Python part if I just had more LaTeX skills.
You mean doing all this math as macros? That sounds pretty scary. 😱
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
> I don't believe it's a good idea to wipe it.
Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste.
By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
XDG_STATE_HOME just like I do with XDG_CACHE_HOME. So far, only wireplumber appears in this directory … Hm …
I’ll keep an eye on labwc, because it’s very promising, and try again in a few years. If I had the resources to get involved with development, I would, but I don’t, sadly.
https://www.x.org/releases/current/doc/libX11/libX11/libX11.html#Setting_and_Reading_the_WM_NORMAL_HINTS_Property
(Nope, that’s not Twitter.)
https://www.x.org/releases/current/doc/libX11/libX11/libX11.html#Setting_and_Reading_the_WM_NORMAL_HINTS_Property
(Nope, that’s not Twitter.)
https://www.x.org/releases/current/doc/libX11/libX11/libX11.html#Setting_and_Reading_the_WM_NORMAL_HINTS_Property
(Nope, that’s not Twitter.)
WM_NORMAL_HINTS property is a property that can be set on a window. Part of that property is width_inc and height_inc. They tell the window manager to only increase/decrease a window’s size by certain steps.Terminal emulators like to set these values to the font size, so that when you resize the window the size “snaps” to the next increment and the terminal widget fits *exactly* into the window. It’s a bit hard to explain for me, so here’s a demonstration:
https://movq.de/v/7909ebc08a/st.mp4
That’s the st terminal.
It appears, Wayland does not have something like
WM_NORMAL_HINTS, so this functionality has been removed from GTK 3. (You can still set this property on your window, but it’s convoluted and not part of the GTK toolkit, i.e. you have to use Xlib yourself. That makes everything very awkward.)Hence in xiate, it looks like this:
https://movq.de/v/7909ebc08a/xiate.mp4
I kind of got used to that over time, but now that I use st every now and then, I realize how ugly and annoying xiate’s behaviour is. 🫤
WM_NORMAL_HINTS property is a property that can be set on a window. Part of that property is width_inc and height_inc. They tell the window manager to only increase/decrease a window’s size by certain steps.Terminal emulators like to set these values to the font size, so that when you resize the window the size “snaps” to the next increment and the terminal widget fits *exactly* into the window. It’s a bit hard to explain for me, so here’s a demonstration:
https://movq.de/v/7909ebc08a/st.mp4
That’s the st terminal.
It appears, Wayland does not have something like
WM_NORMAL_HINTS, so this functionality has been removed from GTK 3. (You can still set this property on your window, but it’s convoluted and not part of the GTK toolkit, i.e. you have to use Xlib yourself. That makes everything very awkward.)Hence in xiate, it looks like this:
https://movq.de/v/7909ebc08a/xiate.mp4
I kind of got used to that over time, but now that I use st every now and then, I realize how ugly and annoying xiate’s behaviour is. 🫤
WM_NORMAL_HINTS property is a property that can be set on a window. Part of that property is width_inc and height_inc. They tell the window manager to only increase/decrease a window’s size by certain steps.Terminal emulators like to set these values to the font size, so that when you resize the window the size “snaps” to the next increment and the terminal widget fits *exactly* into the window. It’s a bit hard to explain for me, so here’s a demonstration:
https://movq.de/v/7909ebc08a/st.mp4
That’s the st terminal.
It appears, Wayland does not have something like
WM_NORMAL_HINTS, so this functionality has been removed from GTK 3. (You can still set this property on your window, but it’s convoluted and not part of the GTK toolkit, i.e. you have to use Xlib yourself. That makes everything very awkward.)Hence in xiate, it looks like this:
https://movq.de/v/7909ebc08a/xiate.mp4
I kind of got used to that over time, but now that I use st every now and then, I realize how ugly and annoying xiate’s behaviour is. 🫤
https://lists.suckless.org/dev/1706/31857.html
This never made it into their
master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
https://lists.suckless.org/dev/1706/31857.html
This never made it into their
master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
https://lists.suckless.org/dev/1706/31857.html
This never made it into their
master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
(Srsly, though, nice shots as always. 😅)
(Srsly, though, nice shots as always. 😅)
(Srsly, though, nice shots as always. 😅)
.txt or “plain text” are ambiguous terms, I’m afraid. 🫤Other than that, it looks neat and interesting. 😅
.txt or “plain text” are ambiguous terms, I’m afraid. 🫤Other than that, it looks neat and interesting. 😅
.txt or “plain text” are ambiguous terms, I’m afraid. 🫤Other than that, it looks neat and interesting. 😅
For now, I’m drafting. Interestingly, an 80x24 terminal could fit quite a lot of plain ASCII tiles. That would be pretty close to the original game. On the other hand, if I were to use nothing but box drawing characters and made every cell on the terminal a tile, I could get a huge grid. This could allow for some new and interesting stuff, thus extending the original game. 🤔
https://movq.de/v/60a9db4869/s.png
For now, I’m drafting. Interestingly, an 80x24 terminal could fit quite a lot of plain ASCII tiles. That would be pretty close to the original game. On the other hand, if I were to use nothing but box drawing characters and made every cell on the terminal a tile, I could get a huge grid. This could allow for some new and interesting stuff, thus extending the original game. 🤔
https://movq.de/v/60a9db4869/s.png
For now, I’m drafting. Interestingly, an 80x24 terminal could fit quite a lot of plain ASCII tiles. That would be pretty close to the original game. On the other hand, if I were to use nothing but box drawing characters and made every cell on the terminal a tile, I could get a huge grid. This could allow for some new and interesting stuff, thus extending the original game. 🤔
https://movq.de/v/60a9db4869/s.png
A portability table for a function, what the heck? I never expected to see something like that. 🤯 (Turbo C++ is from 1992 – I didn’t even know what UNIX was during that time. Only DOS, Windows, and OS/2 existed in my little world.)
And it’s so fascinating that code which I wrote in 2015 without any intention of ever porting it to some other system just compiles with a 20/30 year old compiler and then the program *works*. 🤯🤯🤯 Granted, the program is simple, but still.
It shows that I don’t really have a lot of knowledge about DOS on this level / from this perspective. On the other hand, it means that I now get to explore this old operating system like it’s brand new. 😅
A portability table for a function, what the heck? I never expected to see something like that. 🤯 (Turbo C++ is from 1992 – I didn’t even know what UNIX was during that time. Only DOS, Windows, and OS/2 existed in my little world.)
And it’s so fascinating that code which I wrote in 2015 without any intention of ever porting it to some other system just compiles with a 20/30 year old compiler and then the program *works*. 🤯🤯🤯 Granted, the program is simple, but still.
It shows that I don’t really have a lot of knowledge about DOS on this level / from this perspective. On the other hand, it means that I now get to explore this old operating system like it’s brand new. 😅
A portability table for a function, what the heck? I never expected to see something like that. 🤯 (Turbo C++ is from 1992 – I didn’t even know what UNIX was during that time. Only DOS, Windows, and OS/2 existed in my little world.)
And it’s so fascinating that code which I wrote in 2015 without any intention of ever porting it to some other system just compiles with a 20/30 year old compiler and then the program *works*. 🤯🤯🤯 Granted, the program is simple, but still.
It shows that I don’t really have a lot of knowledge about DOS on this level / from this perspective. On the other hand, it means that I now get to explore this old operating system like it’s brand new. 😅
> Something along "spaceship pilot's view of flying into a starfield" would have helped me for sure.
I like that a lot and put it in the README. Thanks! 😊
The port to DOS is done, I’d say:
https://movq.de/v/d4cc4647c6/MVI_6505.MOV.mp4
The
-e flag (/e on DOS) works now. 😃 There you go, an Enterprise!
> Something along "spaceship pilot's view of flying into a starfield" would have helped me for sure.
I like that a lot and put it in the README. Thanks! 😊
The port to DOS is done, I’d say:
https://movq.de/v/d4cc4647c6/MVI_6505.MOV.mp4
The
-e flag (/e on DOS) works now. 😃 There you go, an Enterprise!
> Something along "spaceship pilot's view of flying into a starfield" would have helped me for sure.
I like that a lot and put it in the README. Thanks! 😊
The port to DOS is done, I’d say:
https://movq.de/v/d4cc4647c6/MVI_6505.MOV.mp4
The
-e flag (/e on DOS) works now. 😃 There you go, an Enterprise!
It is so scary how much we depend on YouTube. 😢
It is so scary how much we depend on YouTube. 😢
It is so scary how much we depend on YouTube. 😢
> Thanks! The document looked so nice, I just had to read it all.
😅 The magic of LaTeX.
> Even though I never used anything even just this advanced after my uni maths lectures.
Same here. Well, it’s not a surprise in my case – I work as a sysadmin. 🤣 You usually don’t need to go to university to get hired in that field.
> With that visual impression I now know what this program actually does
Well, that probably means that my README sucks. 😅
> Thanks! The document looked so nice, I just had to read it all.
😅 The magic of LaTeX.
> Even though I never used anything even just this advanced after my uni maths lectures.
Same here. Well, it’s not a surprise in my case – I work as a sysadmin. 🤣 You usually don’t need to go to university to get hired in that field.
> With that visual impression I now know what this program actually does
Well, that probably means that my README sucks. 😅
> Thanks! The document looked so nice, I just had to read it all.
😅 The magic of LaTeX.
> Even though I never used anything even just this advanced after my uni maths lectures.
Same here. Well, it’s not a surprise in my case – I work as a sysadmin. 🤣 You usually don’t need to go to university to get hired in that field.
> With that visual impression I now know what this program actually does
Well, that probably means that my README sucks. 😅
https://movq.de/v/d45de49cae/doc.pdf
So far, I got a basic version of asciifield working:
https://movq.de/v/f949db49e7/MVI_6497.MOV.mp4
There are some TODOs left. Sadly, none of what I’ve done so far warrants a PDF. 😅 It was pretty straightforward. C is an amazingly portable language.
Haha, right, the CV must have been the last “serious” LaTeX document for me as well …
https://movq.de/v/d45de49cae/doc.pdf
So far, I got a basic version of asciifield working:
https://movq.de/v/f949db49e7/MVI_6497.MOV.mp4
There are some TODOs left. Sadly, none of what I’ve done so far warrants a PDF. 😅 It was pretty straightforward. C is an amazingly portable language.
Haha, right, the CV must have been the last “serious” LaTeX document for me as well …
https://movq.de/v/d45de49cae/doc.pdf
So far, I got a basic version of asciifield working:
https://movq.de/v/f949db49e7/MVI_6497.MOV.mp4
There are some TODOs left. Sadly, none of what I’ve done so far warrants a PDF. 😅 It was pretty straightforward. C is an amazingly portable language.
Haha, right, the CV must have been the last “serious” LaTeX document for me as well …