From 5cd15536b668c206ce994fc9b28da25f2cf430d4 Mon Sep 17 00:00:00 2001 From: Roshan Jossy Date: Thu, 28 Dec 2023 00:50:02 +0100 Subject: [PATCH] Format notes in Readme --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e2de9d1..212f577 100644 --- a/README.md +++ b/README.md @@ -261,7 +261,9 @@ To make exclude-patterns like these permanent, you can create a `.fdignore` file /mnt/external-drive *.bak ``` -Note: `fd` also supports `.ignore` files that are used by other programs such as `rg` or `ag`. + +> [!NOTE] +> `fd` also supports `.ignore` files that are used by other programs such as `rg` or `ag`. If you want `fd` to ignore these patterns globally, you can put them in `fd`'s global ignore file. This is usually located in `~/.config/fd/ignore` in macOS or Linux, and `%APPDATA%\fd\ignore` in @@ -284,7 +286,8 @@ option: If you also want to remove a certain class of directories, you can use the same technique. You will have to use `rm`s `--recursive`/`-r` flag to remove directories. -Note: there are scenarios where using `fd … -X rm -r` can cause race conditions: if you have a +> [!NOTE] +> There are scenarios where using `fd … -X rm -r` can cause race conditions: if you have a path like `…/foo/bar/foo/…` and want to remove all directories named `foo`, you can end up in a situation where the outer `foo` directory is removed first, leading to (harmless) *"'foo/bar/foo': No such file or directory"* errors in the `rm` call.