- The reason I have dotfiles is for a few reasons. The first is that I use my PC and a few laptops interchangeably, and having my configurations easily downloadable is a big time saver. The second reason why I have my dotfiles up is because maybe somebody is looking for a certain baseline for their configurations, and if they find it well, I am more than happy to help that person. The third reason is just in case something happens to one of my laptops or my PC. I suggest that if you have configuration files, you should back them up on your preferred git host.
-
-
What are in my Dotfiles?
-
In my Dotfiles, I have created an install script written in Bash that automatically installs all of my configurations and the software I use, giving the end user my setup. I wouldn't suggest the average person use my setup as-is, but rather to take my configs and modify them, thereby making it their own!
-
-
I will not go in-depth about the software I use since I have already done that on the software page. Instead of including all my software, I have only included the essential software in the install script, as different computers serve different purposes. Additionally, I have programmed a part of the script to install any missing firmware, eliminating those annoying warning messages during package installation. While I can't guarantee this will work on all computers, it has successfully fixed all missing firmware on every computer I've tested it on so far. If you still encounter warning messages, please refer to the Arch Wiki page to see what firmware you need to install.
-
-
-
News
-
Changing to starship and other improvments!
Date: 21-08-2024
-
It has been a month since the last update, and right now, as of today, I have finished a pretty big part of my Dotfiles! So I have switched my terminal emulator from Alacritty to st by Suckless Software. The reason why I have done this is because St is just way lighter than Alacritty. I have also got the ranger configuration to work on the first install, which is amazing! And I have switched from synth-shell to starship because it is just more fun to mess around with. But that is all for this update!
-
-
-
Fixing Ownership of directories and files
Date: 22-7-2024
-
Yesterday I tested the config again because I reinstalled arch on my laptop, and I noticed a problem when I wanted to change a config, it was readonly becasue mt user did not have access to the file, this is the same for the wallpaper file. So to fix this I have added a line in the install file that fixes this issue.
-
-
-
Stable install (mostly)
Date: 20-7-2024
-
Today, I tested my install script on my test computer, and it went smoothly. I only found one problem, which was easily fixed: I forgot to use the -r option when copying files to the .config directory. The only remaining issue is with the ranger config, but apart from that, the install script is stable for anybody to use.
+ The reason I have dotfiles is for a few reasons. The first is that I use my PC and a few laptops interchangeably, and having my configurations easily downloadable is a big time saver. The second reason why I have my dotfiles up is because maybe somebody is looking for a certain baseline for their configurations, and if they find it well, I am more than happy to help that person. The third reason is just in case something happens to one of my laptops or my PC. I suggest that if you have configuration files, you should back them up on your preferred git host.
+
+
What are in my Dotfiles?
+
In my Dotfiles, I have created an install script written in Bash that automatically installs all of my configurations and the software I use, giving the end user my setup. I wouldn't suggest the average person use my setup as-is, but rather to take my configs and modify them, thereby making it their own!
+
+
I will not go in-depth about the software I use since I have already done that on the software page. Instead of including all my software, I have only included the essential software in the install script, as different computers serve different purposes. Additionally, I have programmed a part of the script to install any missing firmware, eliminating those annoying warning messages during package installation. While I can't guarantee this will work on all computers, it has successfully fixed all missing firmware on every computer I've tested it on so far. If you still encounter warning messages, please refer to the Arch Wiki page to see what firmware you need to install.
+
+
+
News
+
Changing to starship and other improvments!
Date: 21-08-2024
+
It has been a month since the last update, and right now, as of today, I have finished a pretty big part of my Dotfiles! So I have switched my terminal emulator from Alacritty to st by Suckless Software. The reason why I have done this is because St is just way lighter than Alacritty. I have also got the ranger configuration to work on the first install, which is amazing! And I have switched from synth-shell to starship because it is just more fun to mess around with. But that is all for this update!
+
+
+
Fixing Ownership of directories and files
Date: 22-7-2024
+
Yesterday I tested the config again because I reinstalled arch on my laptop, and I noticed a problem when I wanted to change a config, it was readonly becasue mt user did not have access to the file, this is the same for the wallpaper file. So to fix this I have added a line in the install file that fixes this issue.
+
+
+
Stable install (mostly)
Date: 20-7-2024
+
Today, I tested my install script on my test computer, and it went smoothly. I only found one problem, which was easily fixed: I forgot to use the -r option when copying files to the .config directory. The only remaining issue is with the ranger config, but apart from that, the install script is stable for anybody to use.
Fakefetch is the first real program I have ever created that I use daily apart from config files. I made fakefetch when I saw people complaining about neofetch being slow that is why I have called it fakefetch. In the start it was just 10 lines of bash with the 'echo' commands which is like 'print' function in python if you do not know, so it was bascially bare minimun, and I was not proud of this program I was like 'ok thats done just add it to my .bashrc' and continue using Linux. After about a day I wanted to see if I could add more to it like the uptime, then comes what package manager im using and after a while I just rewrote it in C and low and behold I have made my own mini neofetch program that I can use on all of my computers.
-
What is Fakefetch
-
Fakefetch is an alternative I have made to neofetch, it is written in the C programming language unlike neofetch which is written in bash and due to the fact I have written Fakefetch in C it is way faster then neofetch. In the future I plan to add more features to Fakefetch and make it more user friendly. I do plan on making a Tui customizer at some point to make your own fakefetch script.
-
Why Fakefetch?
-
The main reason why you should use Fakefetch is because it is a very flexible program being written in the C programming language; it is not a large program, only being one file large so far and does not slow down your computer at all unlike Neofetch. Fakefetch is also very hackable thanks to how I have commented on the code, meaning you can make your own Fakefetch versions and make it do whatever you want thanks to it being licensed under the GPL, so you have the right to redistribute it if you make your own versions that you can share with anybody.
-
How to install
-
Step one: The first thing you want to do is clone the gitlab project, you can do this from the following command. $ git clone https://gitlab.com/Shipwreckt/fakefetch
-
Step two: after cloneing the project you want to run the setup.sh with ./setup.sh
-
To configure Fakefetch the file is located at /bin/fakefetch
-
In the next upcoming updates I plan to add an IP address option and a way to configure it in ~/.config/shipwreckt for ease of use.
-
-
News
-
Great rewrite
Date: 8/7/2024
-
First post hello there! So yesterday there was a big update to Fakefetch, which involved me basically reprogramming the whole thing in the C programming language in my efforts to understand it more. Now the program might have some missing features compared to when it was written in bash, but in the coming week I will be adding more code to it and more features, so stay tuned in!
Fakefetch is the first real program I have ever created that I use daily apart from config files. I made fakefetch when I saw people complaining about neofetch being slow that is why I have called it fakefetch. In the start it was just 10 lines of bash with the 'echo' commands which is like 'print' function in python if you do not know, so it was bascially bare minimun, and I was not proud of this program I was like 'ok thats done just add it to my .bashrc' and continue using Linux. After about a day I wanted to see if I could add more to it like the uptime, then comes what package manager im using and after a while I just rewrote it in C and low and behold I have made my own mini neofetch program that I can use on all of my computers.
+
What is Fakefetch
+
Fakefetch is an alternative I have made to neofetch, it is written in the C programming language unlike neofetch which is written in bash and due to the fact I have written Fakefetch in C it is way faster then neofetch. In the future I plan to add more features to Fakefetch and make it more user friendly. I do plan on making a Tui customizer at some point to make your own fakefetch script.
+
Why Fakefetch?
+
The main reason why you should use Fakefetch is because it is a very flexible program being written in the C programming language; it is not a large program, only being one file large so far and does not slow down your computer at all unlike Neofetch. Fakefetch is also very hackable thanks to how I have commented on the code, meaning you can make your own Fakefetch versions and make it do whatever you want thanks to it being licensed under the GPL, so you have the right to redistribute it if you make your own versions that you can share with anybody.
+
How to install
+
Step one: The first thing you want to do is clone the gitlab project, you can do this from the following command. $ git clone https://gitlab.com/Shipwreckt/fakefetch
+
Step two: after cloneing the project you want to run the setup.sh with ./setup.sh
+
To configure Fakefetch the file is located at /bin/fakefetch
+
In the next upcoming updates I plan to add an IP address option and a way to configure it in ~/.config/shipwreckt for ease of use.
+
+
News
+
Great rewrite
Date: 8/7/2024
+
First post hello there! So yesterday there was a big update to Fakefetch, which involved me basically reprogramming the whole thing in the C programming language in my efforts to understand it more. Now the program might have some missing features compared to when it was written in bash, but in the coming week I will be adding more code to it and more features, so stay tuned in!