tome export
This commit is contained in:
parent
52278c3a53
commit
7a52afab5f
960 changed files with 3670 additions and 2229 deletions
|
|
@ -82,15 +82,15 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "\n <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"/blog\/going-full-vim\">I switched to using Neovim full time<\/a> in July 2021.<\/p>\n\n<p>More recently, I've used a script that creates and attaches to tmux sessions based on the directories in my Code directory, making it easy to switch between projects.<\/p>\n\n<p>It was based on others by <a href=\"/podcast\/25-jess-archer-drush-laravel-prompts\">Jess Archer<\/a> and ThePrimeagen, although Prime recently created a new version of his as its own project, so I decided to switch to his version.<\/p>\n\n<p>But there was one issue - the paths to search for directory names is hard-coded and don't match mine.<\/p>\n\n<p>I started by duplicating his and changing the paths, but that would mean missing any future updates and having to maintain my version separately.<\/p>\n\n<p>Until I realised I could use his version and apply patches to it for my changes and customisations.<\/p>\n\n<p>This is something I'm familiar with from my Drupal contributions, as we used to attach patch files to issues before moving to GitLab and merge requests.<\/p>\n\n<p>I was able to make my changes and easily <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/5fd27efa502bd48eb7d897acec8aa3344bef2247\">apply the patch easily as part of my Nix derivation<\/a>.<\/p>\n\n<p>This means I'll get any future updates to the script, keep my changes and Nix will automatically apply my patch whenever I rebuild my system.<\/p>\n\n<p>I really like this approach, as I'm no longer duplicating the script and don't have the maintenance overhead whilst still making any customisations I need.<\/p>\n\n<p>In fact, there are Linux applications such as dwm, dmenu and st (a simple terminal), all written by suckless.org, that use this approach as the main method of configuration and customisation.<\/p>\n\n<p>They release the core package and people write and contribute patch files to customise it as they need.<\/p>\n\n<p>Although patches are no longer used on Drupal.org, they're still a great way to customise and contribute to open source software.<\/p>\n\n ",
|
||||
"value": "\n <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"\/blog\/going-full-vim\">I switched to using Neovim full time<\/a> in July 2021.<\/p>\n\n<p>More recently, I've used a script that creates and attaches to tmux sessions based on the directories in my Code directory, making it easy to switch between projects.<\/p>\n\n<p>It was based on others by <a href=\"\/podcast\/25-jess-archer-drush-laravel-prompts\">Jess Archer<\/a> and ThePrimeagen, although Prime recently created a new version of his as its own project, so I decided to switch to his version.<\/p>\n\n<p>But there was one issue - the paths to search for directory names is hard-coded and don't match mine.<\/p>\n\n<p>I started by duplicating his and changing the paths, but that would mean missing any future updates and having to maintain my version separately.<\/p>\n\n<p>Until I realised I could use his version and apply patches to it for my changes and customisations.<\/p>\n\n<p>This is something I'm familiar with from my Drupal contributions, as we used to attach patch files to issues before moving to GitLab and merge requests.<\/p>\n\n<p>I was able to make my changes and easily <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/5fd27efa502bd48eb7d897acec8aa3344bef2247\">apply the patch easily as part of my Nix derivation<\/a>.<\/p>\n\n<p>This means I'll get any future updates to the script, keep my changes and Nix will automatically apply my patch whenever I rebuild my system.<\/p>\n\n<p>I really like this approach, as I'm no longer duplicating the script and don't have the maintenance overhead whilst still making any customisations I need.<\/p>\n\n<p>In fact, there are Linux applications such as dwm, dmenu and st (a simple terminal), all written by suckless.org, that use this approach as the main method of configuration and customisation.<\/p>\n\n<p>They release the core package and people write and contribute patch files to customise it as they need.<\/p>\n\n<p>Although patches are no longer used on Drupal.org, they're still a great way to customise and contribute to open source software.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"/blog\/going-full-vim\">I switched to using Neovim full time<\/a> in July 2021.<\/p>\n\n<p>More recently, I've used a script that creates and attaches to tmux sessions based on the directories in my Code directory, making it easy to switch between projects.<\/p>\n\n<p>It was based on others by <a href=\"/podcast\/25-jess-archer-drush-laravel-prompts\">Jess Archer<\/a> and ThePrimeagen, although Prime recently created a new version of his as its own project, so I decided to switch to his version.<\/p>\n\n<p>But there was one issue - the paths to search for directory names is hard-coded and don't match mine.<\/p>\n\n<p>I started by duplicating his and changing the paths, but that would mean missing any future updates and having to maintain my version separately.<\/p>\n\n<p>Until I realised I could use his version and apply patches to it for my changes and customisations.<\/p>\n\n<p>This is something I'm familiar with from my Drupal contributions, as we used to attach patch files to issues before moving to GitLab and merge requests.<\/p>\n\n<p>I was able to make my changes and easily <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/5fd27efa502bd48eb7d897acec8aa3344bef2247\">apply the patch easily as part of my Nix derivation<\/a>.<\/p>\n\n<p>This means I'll get any future updates to the script, keep my changes and Nix will automatically apply my patch whenever I rebuild my system.<\/p>\n\n<p>I really like this approach, as I'm no longer duplicating the script and don't have the maintenance overhead whilst still making any customisations I need.<\/p>\n\n<p>In fact, there are Linux applications such as dwm, dmenu and st (a simple terminal), all written by suckless.org, that use this approach as the main method of configuration and customisation.<\/p>\n\n<p>They release the core package and people write and contribute patch files to customise it as they need.<\/p>\n\n<p>Although patches are no longer used on Drupal.org, they're still a great way to customise and contribute to open source software.<\/p>\n\n ",
|
||||
"processed": "\n <p>I'm a long-time Vim and tmux user.<\/p>\n\n<p>I used them before <a href=\"http:\/\/default\/blog\/going-full-vim\">I switched to using Neovim full time<\/a> in July 2021.<\/p>\n\n<p>More recently, I've used a script that creates and attaches to tmux sessions based on the directories in my Code directory, making it easy to switch between projects.<\/p>\n\n<p>It was based on others by <a href=\"http:\/\/default\/podcast\/25-jess-archer-drush-laravel-prompts\">Jess Archer<\/a> and ThePrimeagen, although Prime recently created a new version of his as its own project, so I decided to switch to his version.<\/p>\n\n<p>But there was one issue - the paths to search for directory names is hard-coded and don't match mine.<\/p>\n\n<p>I started by duplicating his and changing the paths, but that would mean missing any future updates and having to maintain my version separately.<\/p>\n\n<p>Until I realised I could use his version and apply patches to it for my changes and customisations.<\/p>\n\n<p>This is something I'm familiar with from my Drupal contributions, as we used to attach patch files to issues before moving to GitLab and merge requests.<\/p>\n\n<p>I was able to make my changes and easily <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/dotfiles\/commit\/5fd27efa502bd48eb7d897acec8aa3344bef2247\">apply the patch easily as part of my Nix derivation<\/a>.<\/p>\n\n<p>This means I'll get any future updates to the script, keep my changes and Nix will automatically apply my patch whenever I rebuild my system.<\/p>\n\n<p>I really like this approach, as I'm no longer duplicating the script and don't have the maintenance overhead whilst still making any customisations I need.<\/p>\n\n<p>In fact, there are Linux applications such as dwm, dmenu and st (a simple terminal), all written by suckless.org, that use this approach as the main method of configuration and customisation.<\/p>\n\n<p>They release the core package and people write and contribute patch files to customise it as they need.<\/p>\n\n<p>Although patches are no longer used on Drupal.org, they're still a great way to customise and contribute to open source software.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
"feeds_item": [
|
||||
{
|
||||
"imported": "1970-01-01T00:33:45+00:00",
|
||||
"imported": "1970-01-01T00:32:50+00:00",
|
||||
"guid": null,
|
||||
"hash": "e5fa9a4299d210679c2b24528450155b",
|
||||
"target_type": "feeds_feed",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue