David Winterbottom

Most-linked posts?

1. An LLM TDD Loop
   2 people · 2 mentions · first linked 2024-10-13
2. /writing/the-most-important-command-line-tip-incremental-history-searching-with-inputrc/
   2 people · 2 mentions · first linked 2016-08-18
3. Effective pull requests and other good practices for teams using github
   2 people · 2 mentions · first linked 2012-10-21
4. Incremental History Searching with .inputrc
   2 people · 2 mentions · first linked 2018-06-14

What Hacker News says?

1. ldiracdelta · 2016-08-18

   If you put this in your `~/.inputrc` [1]: "\e[A": history-search-backward "\e[B": history-search-forward "\e[C": forward-char "\e[D": backward-char you can start typing a previous command and go up through your history for all commands starting with whatever you currently have typed into the bash shell. Reset the scrolling through the history with `ctrl+c`. Personally, I hate that powershell remembers your position…

   Comment linking /writing/the-most-important-command-line-tip-incremental-history-searching-with-inputrc/

   on “PowerShell is open sourced and is available on Linux”
2. spdy · 2012-09-03

   Submitted Cacheback - asynchronous cache refreshing for Django as a story · 47 points

   HN discussion
3. Myrmornis · 2016-09-13

   Agreed, but even nicer than control-r are the readline functions `history-search-backward` and `history-search-forward`. Personally I bind them to up/down which on OS X at least involves: # Put this in some file like ~/.readline-bindings "\e[A": history-search-backward "\e[B": history-search-forward # And this in your ~/.bashrc or ~/.zshrc bind -f ~/.readline-bindings That way if you haven't typed any input it behav…

   Comment linking /writing/the-most-important-command-line-tip-incremental-history-searching-with-inputrc/

   on “Advancing in the Bash Shell”
4. yawnxyz · 2024-10-13

   Submitted An LLM TDD Loop as a story · 6 points

   HN discussion
5. pdkl95 · 2018-06-14

   You should try binding UP/DOWN to history-search-backward and history-search-forward[1]. Adding this to your ~/.inputrc "\e[A": history-search-backward "\e[B": history-search-forward enables searching by the current line's prefix in all programs that use readline (a lot of languages use readline for their REPL). That is, if you type "cp<UP>" you immediately get the previous command that started with "cp", regardless…

   Comment linking /tips/the-most-important-command-line-tip-incremental-history-searching-with-inputrc/

   on “Console.table()”
6. codeinthehole · 2015-10-03

   Submitted A useful template for commit messages as a story · 6 points

   HN discussion
7. niftich · 2017-05-19

   They probably are . But some applications will decode the percent-encoding too early in the process of normalizing, security-escaping, and processing the URL. Encoded slashes in URLs are problematic [1][2][3][4][5]. [1] https://httpd.apache.org/docs/2.4/mod/core.html#allowencoded... [2] http://stackoverflow.com/questions/3235219/urlencoded-forwar... [3] http://codeinthehole.com/tips/django-nginx-wsgi-and-encoded-...…

   Comment linking /tips/django-nginx-wsgi-and-encoded-slashes/

   on “Let's Encrypt is down”
8. fss · 2013-05-03

   Submitted PyPI README badges as a story · 3 points

   HN discussion
9. maerF0x0 · 2016-06-13

   There is already a ag plugin for vim that will jump you to the matches. See: https://github.com/rking/ag.vim or see: http://codeinthehole.com/writing/using-the-silver-searcher-w...

   Comment linking /writing/using-the-silver-searcher-with-vim/

   on “Show HN: Tag – instantly jump to your ag matches”
10. codeinthehole · 2012-10-21

    Submitted Effective pull requests and other good practices for teams using github as a story · 3 points

    HN discussion
11. goku12 · 2025-02-17

    Committing git hooks to the repo is possible. These are the 2 ways in which they're commonly handled: 1. Link the scripts from the worktree to the .git/hooks directory - perhaps using a bootstrap script. Ref: https://codeinthehole.com/tips/tips-for-using-a-git-pre-comm... 2. Declare the directory in the worktree to be the local git hooks directory. Ref: https://knpw.rs/blog/direnv-git-hooks

    Comment linking /tips/tips-for-using-a-git-pre-commit-hook/

    on “Hk, a new Git hook manager”
12. japhyr · 2012-09-09

    Submitted Prefer WebTest to Django's test client for functional test as a story · 3 points

    HN discussion
13. dimitry12 · 2024-10-14

    Submitted Bash script implementing LLM-powered TDD-loop as a story · 2 points

    HN discussion
14. codeinthehole · 2014-01-16

    Submitted Command-line tips for effective release anouncements as a story · 2 points

    HN discussion
15. m0th87 · 2013-06-04

    Submitted Effective pull requests and other good practices for teams using github as a story · 2 points

    HN discussion
16. DanielRibeiro · 2013-04-16

    Submitted Tips for using a git pre-commit hook as a story · 2 points

    HN discussion
17. kamaraju · 2026-05-08

    Submitted Incremental History Searching with .inputrc as a story · 1 points

    HN discussion
18. todsacerdoti · 2023-10-09

    Submitted Vim's Useful Lists as a story · 1 points

    HN discussion
19. codeinthehole · 2018-12-24

    Submitted Easy to change as a story · 1 points

    HN discussion
20. codeinthehole · 2018-06-05

    Submitted Advanced pull-request crafting as a story · 1 points

    HN discussion
21. codeinthehole · 2015-05-05

    Submitted An SSH tip for modern AWS patrons as a story · 1 points

    HN discussion
22. codeinthehole · 2014-06-18

    Submitted Continuously rebuild your project as a story · 1 points

    HN discussion
23. mgrouchy · 2013-08-09

    Submitted Enhancing your git commit editor as a story · 1 points

    HN discussion
24. joeyespo · 2012-07-21

    Submitted Use models for uploads as a story · 1 points

    HN discussion

Search all of HN for codeinthehole.com

Linked by the same people?

• PPaul Grahampaulgraham.com