4ffy

joined 3 years ago
3
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]
 

It has been almost two years since the last ReactOS newsletter. Despite no new releases, the project is still active. Much work has been done on different parts of the operating system, from improvements on the 64-bit port to protections against registry corruption.

 

From dired, preview different file types in a side window. The user can control the delay before previews appear, the maximum size of previewed files, and which file types should be excluded from preview.

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago) (3 children)

I have to shout out Wiby. It is focused on like weird personal websites from the early 2000s, that kind of thing. Absolutely not a general-purpose search engine, but mashing the "surprise me" button will take you to all sorts of fun places.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

I recently wrote a literate R document where I added features to a plot one at a time and then showed the result of each. That's a lot of repetitive code. This could have both cut down on copy-pasting and helped to propagate changes in an earlier plot to the later ones. Next time for sure.

[–] [email protected] 1 points 2 years ago

First, you should be familiar with the basic process of compiling and installing software from source. For C or C++ projects, this can be as simple as ./configure, make, make install for projects that use GNU Autotools, or something like cmake -B build, cd build, make, make install for CMake projects.

I generally split PKGBUILDs into three important parts. There's the metadata at the top then there's the build and package functions. build is where everything up to the make (or equivalent build-the-thing) command goes and package is where the make install bits go.

There's also the prepare and check functions, but those aren't used as often.

As for the actual documentation, the Arch Wiki page for PKGBUILD covers most of the metadata stuff and the page for Creating Packages covers most of the build and package stuff.

[–] [email protected] 0 points 2 years ago* (last edited 2 years ago) (1 children)

I've been using Devil for a little while now. The right control key is pretty far from the home row on my keyboard, so the usual touch typing motions are inconvenient. I feel like Devil, which I have mapped to semicolon, lets me reclaim some of that.

I have caps lock as control as well, so that gives me control access on both sides of the home row. The two sides behave a bit differently since caps lock is an actual modifier, but that hasn't been an issue for me.

[–] [email protected] 5 points 2 years ago (3 children)

This is the main reason that one should learn to read PKGBUILDs. Any AUR helper like Yay or Paru should give the option. Just make sure that the package downloads from an official source and contains only the necessary build and install instructions.

But I agree. Some people treat the AUR as just another repository, when it most definitely is not.

[–] [email protected] 1 points 2 years ago

I bought a Pixel 7 for the sole purpose of GrapheneOS. I really have no complaints. It Just Works and I feel slightly less uncomfortable carrying a phone with me.

[–] [email protected] 1 points 2 years ago

Shoutouts to the 0.08% of people who are apparently using Haiku for professional work.

 

Now with bloom.

view more: ‹ prev next ›