• Füttern

1 Naßes Futter
Einmal oder zweimal pro Tag eine Portion naßes Futter zwischen beiden teilen (ich füttere sie normalerweise einmal um 9 Uhr Morgens und einmal um 7 Uhr Abends) Naßes Fütter ist in der Küche.

2 Trockenes Futter
Checken Sie bitte ob der Futterautomat funktioniert. Manchmal stoppt er und zeigt ERR-01, in diesem Fall, aus und einstecken Sie es bitte zum Neustart - normalerweise zeigt es die aktuelle Zeit.

Je 3 Tage checken Sie ob es genugend Trockenfutter im Futterautomat gibt’s. Das Trockenfutter ist neben dem naßen Futter in der Küche.

• Wasser

Bitte wechseln Sie das Wasser im Wassercontainer je 3 Tage, also wärend diese Woche nur ein Mal, ich mach’s wenn ich wieder da bin.

• Klo

Je 3 Tage fügen Sie bitte etwa Klumpenstreu ins Klo, folgen Sie diesem Algorithmus:
1 Schalten Sie das Klo aus (einfach aus der Steckdose, weißer Kabel)
2 Fügen Sie bitte etwa Klumpenstreu hinzu - wichtig, nicht mehr als die MAX Linie zeigt
3 Schalten Sie das Klo wieder ein.
4 (Optional) Drücken Sie die Knopf unter dem Display - dann dreht sich das Klo und man kann checken of alles richtig gegangen ist.

Auch wenn Sie das Klumpenstreu hinzufügen, entleeren Sie bitten den Abfallbeutel (Die Müllsäcke sind oben auf dem Regal, weiße Beutel). Nur ein Mal reicht.

• Spielen

Bitte spielen Sie so lange und oft wie Sie wollen! Die beiden lieben es! Der graue magt Pinseln und Mäuse und der getiegerte magt Bälle.

So, the first rule of consious habits: “Make it visible”. As a happy user of org-mode I couldn’t imagine a better place to put them, then org-habit.
To use org-habit with spacemacs you need to enable it first as an org-module. Thankfully, there is a handy shortcut to display the contents of the variable, in our case - it’s org-modules:
SPC h d v - then type org-modules I remember this mnemonic shortcut as SPC + Help + Describe + Variable.
Scroll all the way down to the Customize variable line and click it. After you’ve seen the contents of org-modules variable and actually see that org-habit is not enabled - put the tick in front of it and save (C-x C-s).

Now all is left is to write down your habits. Let’s say I want to wear my posture corrector every day. Let’s look at this example habit:

     ** TODO 15mins with posture corrector
        SCHEDULED: <2020-06-20 Sat .+1d>
        :PROPERTIES:
        :STYLE:    habit
        :END:  

It’s just a regular TODO entry, with a couple of changes:
1) it’s scheduled to the time I want it to repeat (in my case, daily, for more details on scheduling see this) 2) it includes a special tag :STYLE: habit

Now, that we’ve created an actual habit, let’s take a look at it in the agenda view:
, a a - to open agenda

This funny blue-yellow-red stripe is called “consistency graph” - at first I didn’t get what it means, but then I understood that it depicts a row of several days in the past and in the future. Green (or blue if it’s a new habit) on the left are days when checking the habit as DONE meant that you did it on time.
One yellow thingy is likely today (means that habit is risking being late - org has so little faith in me :sigh:).

And the rest of red pieces depic all those days in the future when ticking the habit off would mean that you lost were late.
The amount of days before and after today is changable by chaning the variables org-habit-presceding-days and org-habit-following-days.
I guess they are there to make you motivated?.. (Don’t break the chain!..) Anyway, I don’t enjoy seeing so much red in my agenda so I changed the content of org-habit-following-days to 0.

Alright, now my agenda will bully me into following my habits every day! One pity is that in spacemacs+evil you cannot use K to toggle habits in agenda view, I have to invoke the command by clicking M-x org-habit-toggle-habits. Also it is likely not supported by Orgzly - an outliner that is semi-equal to org-mode on my phone.

What habits do you want to form? What do you want to get rid of? What are your ways to track habits? Letme on know via email.

P.S. I hightly recommend James’ newsletter - it really delivers what it promises.

I had a couple of basic image-improving changes to be performed on 5 of my photos. All of my photos have name of ‘IMG_*.jpg’. I put the processed photos into a separate folder just not to mix them up, folder is called conv.

Improve brightness/contrast/threshold:

convert ./IMG_*.jpg -level 25%,75%,2.0 ./conv/img.jpg

Command explained:

• convert is a utility made for converting images, it’s part of the imagemagick.
• ./IMG_*.jpg is a regular expression for the input files.
• -level is imagemagick’s option that tells us that we want to change the image’s levels (brighness, contrast, …).
• numbers 25% and 75% stand for white point and black point. white point means “take all pixels that are equal to this value or lighter and make them completely white”, and black point means “take all pixels that are equal to this value or darker and make them completely black”. This will increase contrast and brightness of the image.
• 2.0 stands for gamma, it’s for making the image lighter or darker in general, see more here.
• ./conv/img.jpg is the name of the resulting image. We’ll get a bunch of images with the names img_1.jpg in the folder conv.

See more on image levels here.

Crop photos:

convert ./IMG_*.jpg -crop 1330x1100+320+0  ./conv/img.png

Command explained:

• convert - as we already know is the name of the converting utility.
• ./IMG_*.jpg are the names on the input files
• -crop is the name of the option
• 1330x1100 - is the requested size of the cropped image.
• +320+0 - is the center of the crop.

See more on crop here.

• installed android studio to /mnt/opt (my / filesystem is almost full :sweat_smile:)
• installed sdk
• installed adb (sudo dnf install android-tools)
• created plugdev group (sudo groupadd plugdev)
• added myself to plugdev group (sudo usermod -aG plugdev $LOGNAME)

Connected my phone to my computer, turned on USB debugging and all and there was… nothing.

Then I did lsusb to see if my phone is even reconizable via usb: no.
Changed usb cable, ran lsusb again -> yes!
Ran adb devices - my device was not shown. I have Fedora, so the udev rules are not originally where they should be so I liked them:

• copied udev rules: sudo cp /usr/share/doc/android-tools/51-android.rules /etc/udev/rules.d
• restarted udev: sudo udevadm control --reload-rules
• found phone on adb devices -> yeah!, but android studio still does not see it :thinking_face:
• started android studio with sudo - still does not work
• works only if I start Android studio with root
• works if I do this: export ANDROID_HOME=<the Android/Sdk folder> in ~/.profile and source ~/.profile - many thanks to Yu Shen. It seems that my “non-standard” path to sdk/android studio (/mnt/opt) was in the way. But in the end it worked out 🐱.

1. Install latexmk: sudo dnf install latexmk
2. Add latex layer to spacemacs:
   • SPC f e d to open the ~.spacemacs file;
   • add latex to the dotspacemacs-configuration-layers variable;
   • SPC f e R to download layer and apply changes.
3. Open a .tex file and compile a pdf with , b or latex/build

If you, like me, enjoy working with 2 windows with code in the first one and the resulting pdf in the second one then do this:

1. Open a .tex file: C-x C-f
2. Divide your window in two: SPC w /
3. Go to the second window and open a pdf that you just build there. If you see pdf as plan text - enable doc-view-mode
4. Change the .tex, press , b to rebuild and see changes applied in the second window.

it's a png so zoon in

Pro tip: regulate the width of both screens with going into window-transient-state (SPC w ,) and pressing [ and ].

Story behind

I like compiling things and having my documents version-controlled, that’s why I like tex. I tried TexMaker and TexStudio but they both have funny UI. I use spacemacs for my day-to-day, so I tried to give it a shot. Turned out it’s quite decent.

df -h will show you disk usage per filesystem.
du -h <foldername>/* will show you file sizes in the specified folder.
docker system prune may free astonishing amount of disk space sometimes.

1. Unmount the partition you want to cut.
2. Cut a part of exising ext4 partition in gparted and make it “Unallocated”.
3. Install windows in the “unallocated” space. This will create 2 new partitions: boot partition for windows and the actual windows partition.
4. Reboot into linux. Linux will not notice the newly installed windows just yet.
5. Update grub - sudo grub2-mkconfig -o /boot/grub2/grub.cfg
6. Reboot and you will see windows in grub menu.

Story behind

Until this very day I thought that installing windows after linux will make my life a living hell for a good couple of days. Never have I been so wrong. The cutting of my HDD went without any errors, which was probably the most risky part.

The moral of the story is: installing windows after linux is possible and even easy. Try it for yourself before you say it’s not :)

sudo dnf install ccze

Using ccze couldn’t have been easier!

journalctl -u <unitname> -f | ccze

You can even colorize files with tail:

tail -f -n 50 file.txt | ccze

The only drawback is that you cannot input the enter lines in log, which was pretty handy in journalctl… Also, the colors that I have in ccze are not original colors from my logger, ccze reparsed by logs and added its own colors.

Still looks better than plain white text :)

class Apple{ 
    std::string id;
    public:
    static constexpr std::string_view table = "apple_tbl";
};
class Banana{ 
    std::string id;
    public:
    static constexpr std::string_view table = "banana_tbl"; 
};

class DBDriver 
{
  template<typename T>
  bool has() 
  {
    return db->query("Do you have %s?", T::table);
  }
  
  bool remove(std::string_view id) 
  {
    return db->query("Remove %s of type %s then!", id, T::table)
  }

  private:
  mysql::driver *db;
};

So what is there to do in go? I figured, if we have a function that takes an apple- or bananaID we can just partially apply it and pass it into a more general remove function like so and have minimal repeating code:

package main

type driver struct {}
func (d *driver) hasApple(appleID string) bool {
    // some quering
    return false
}
   
func (d *driver) hasBanana(bananaID string) bool {
    // some quering
    return false
}
    
func (d *driver) deleteApple(appleID string) {
    // some deletion
}

func (d *driver) deleteBanana(bananaID string) {
    // some deletion
}

var db = driver{}

func deleteFruit(get func() bool, remove func()) {
    if get() {
        remove()
    }
}


func DeleteApple(appleID string) {
    get := func() bool {
        return db.hasApple(appleID)
    }
    remove := func() {
        db.deleteApple(appleID)
    }
    
    deleteFruit(get, remove)
}

func DeleteBananas(bananaID string) {
    get := func() bool {
        return db.hasBanana(bananaID)
    }
    remove := func() {
        db.deleteApple(bananaID)
    } 
    deleteFruit(get, remove)
}

Does it work? Yes! Is it a good practice/idea? You tell me!

• a concise and quick installation process
• newest versions of software already available for download with dnf
• git, make and etc already pre-installed

My other laptop, dell xps 13 (2018) works with it perfectly, including the graphics/sound card, so I decided to try it out with my msi gs43vr (2017).

Hardware: msi gs43vr
Software: Fedora 30-1.2

Aaand here goes the list of issues I’ve encountered.

1. Graphical install hangs on Started GNOME Display Manager..
   You will need to start the fedora installer in basic graphics mode with Troubleshooting -> Start fedora in basic graphics mode.
2. After installation, gnome-initial-setup pop ups every time after reboot.
   Just touch ~/.config/gnome-initial-setup-done. This will apply to current user only.
3. When rebooted or shut down and then turned on, fedora froze with blank screen and only a blinking cursor for 2mins.
   At first I thouthg it’s graphics driver’s problem. Installation of a proper NVIDIA driver didn’t work though (I followed this guide).
   What worked for me is removing rhbs quiet from /etc/default/grub. Don’t forget to run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg to update grub.
4. Super button not working
   Install gnome-tweaks and go to Keyboard & Mouse -> Overview Shortcut and toggle it.

Lessons Learned

• rpmfusion drivers completely smashed my setup.

Persisting issues I’d like to have some help with:

1. Same blinking cursor + blank screen on shutdown.
2. Screen brightness regulation buttons (f4&f5) do not work, although volume regulation, keyboard lights and sleep buttons work.
3. Suspend does not work(stuck forever on saving pages), however hibernate does.
   All of the above stopped when I installed the NVIDIA drivers according to this guide.

Still worth it!