I was using macOS mail rules to sort mail into āFeedā and āPapertrailā inbox subfolders but iOS mail badges are frequently incorrect or delayed. Does it work better when using server rules?
Sander van Dragt's Notes
-
-
If you want the best tasting beer, do some gardening beforehand !
-
What was a sensible precaution yesterday remains the same today.
-
Splitting up the example cuttlefish blog application from the cuttlefish framework, so that I can include more features to specialise both, as well as build multiple application types.
-
Found this cool Firefox Extension called Tab Stash, it's a performant open source variety of OneTab (which is neither): Lets you switch tasks by managing group of tabs. Essential.
-
GitHub stars, are they bookmarks or thumbs up?
-
Psh 0.3.0 Released
I've released Psh 0.3.0, my php subshell. Tired of switching tooling versions between PHP projects? Psh starts a shell with your project requirements linked ready to go.
-
The trick to relative symlinks
I learned this week that relative symbolic links are relative to the link not the current working directory. What does this mean?
To remind ourselves, the format of
lnis:ln -s {{/path/to/file_or_directory}} {{path/to/symlink}}Example
Say we have the following structure:
config/config.yaml app/index.phpSay we want to create a symlink to
app/config.yaml. If we are familar with thecpcommand we would incorrectly do this:$ ln -s config/config.yaml app/config.yaml #this is incorrectHere, we're asking
lnto create a symlink inapp/config.yamlthat points toapp/config/config.yamlbecause the 'source' parameter is relative to the link being created, not the current working directory. As that file does not exist the command fails!Correct example:
$ ln -s ../config/config.yaml app/config.yaml #this is correct $ cd app; ln -s ../config/config.yaml config.yaml; cd - #this is clearerThe first correct example can be difficult to comprehend unless we're familiar with this concept: From the perspective of the
app/config.yamlfile, we need to first go to the parent directory then into the config directory.This is clarified by the third example: by changing into the destination directory, we align the current working directory with the path to the source.
Notes
- If we create absolute symbolic links by providing the full path to the source file, this is avoided, however these links are more fragile. For example when syncing links the absolute path to the source is likely different on another device.
-
Someone should really come up with an improved version of
lnthat works conceptually more similar tocpin terms of relative paths. -
Syncing Wallpaper Images Spoon
As a macOS user with a multi monitor setup and a laptop I frequently switch between 1 to 3 screens. I use task related spaces (general, coding, organisation, social) and to reinforce this habit I installed some Unsplash wallpaper images relating to the task.
In some undefined situations I lose the wallpaper image on certain screens on certain desktops (I have already disabled reordering and removing spaces) but dragging wallpapers across multiple screens on multiple spaces is too much work; and why not see if this can be automated.
Thanks to Hammerspoon and a few minutes time you can benefit from my script:
-- SYNC WALLPAPER -- function sync_wallpaper() wp = hs.screen.primaryScreen():desktopImageURL() for index,screen in ipairs(hs.screen.allScreens()) do if screen:desktopImageURL() ~= wp then print('Syncing Wallpaper') screen:desktopImageURL(wp) end end end hs.spaces.watcher.new(sync_wallpaper):start() -- /SYNC WALLPAPER --Add this to your
.hammerspoon/init.luaand switch spaces to sync wallpapers to all screens on that space!By the way
I'm using the following wallpapers: