safe-rm 3.0.0 → 3.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -147,6 +147,8 @@ In `~/.safe-rm/config`
|
|
|
147
147
|
export SAFE_RM_USE_APPLESCRIPT=no
|
|
148
148
|
```
|
|
149
149
|
|
|
150
|
+
By default, on MacOS, `safe-rm` uses AppleScript as much as possible so that removed files could be put back from system Trash app.
|
|
151
|
+
|
|
150
152
|
### Change the Default Trach Bin Other Than System Default
|
|
151
153
|
|
|
152
154
|
```sh
|
|
@@ -190,8 +192,8 @@ $ safe-rm -rf /path/to
|
|
|
190
192
|
To keep the performance of `safe-rm` and avoid conducting unnecessary file system traversing, this would not prevent `/path/to/be/protected/foo` from removing.
|
|
191
193
|
|
|
192
194
|
Pay **ATTENTION** that:
|
|
193
|
-
- Before adding protected rules, i.e. placing the
|
|
194
|
-
- The
|
|
195
|
+
- Before adding protected rules, i.e. placing the `".gitignore"` inside the `"~/.safe-rm/"` directory, it requires `git` to be installed in your environment
|
|
196
|
+
- The `".gitignore"` patterns apply to the root directory (`"/"`), which means that the patterns defined within it need to be relative to the root directory.
|
|
195
197
|
- Avoid adding `/` in the protected rules file, or everything will be protected
|
|
196
198
|
|
|
197
199
|
|