na 1.2.3 → 1.2.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0cc9bb0b48d32bab1e3ece2c1a9ab357dfde238e88a02ceeb5c5a172d4a6e747
-  data.tar.gz: 53300e826f4d4c56b30f846aa94039cb054d99c3d930709de419261409c4d9b3
+  metadata.gz: 27d214430ffba43bf8e743634313b8371ac65357842243ae6dd09b75108fd629
+  data.tar.gz: 0c2f0cc88fd3607b95a8859f7f8a29da809f0d1b89e500a361213ccf9482dc03
 SHA512:
-  metadata.gz: b16ed47431b61a853e03b44efd04c44909814e2bfbde897833f43f640a75a0932c2db14c9cbdfc25834d20bb5d4147ba10ebe84b137d9f6bcdda4266bb80d64d
-  data.tar.gz: 6f97489661677a3cd9fabfb01b1f99c39ff7b1e034d9936fdf1fa578c82fdbceb9c208c050d5e3b7a0bec956a3ea35534ba89c8764de85b41a2c9eceaf8bd207
+  metadata.gz: 402192eda881da608848f35c511f06416d84d3262729698c544017f4ea4ecb7036b9c0d34a8ec0bd8039c0a93a7b95d0d634f8ad1df0813c09b26735cc66662e
+  data.tar.gz: 5882c92767ec069b19e5d6b7d04ed561df8f1d26339016df27627553418442156f63608bf96064146cebd4b9f6922cb690700467c36f1444ae2a6c7efc9bf5d9

data/CHANGELOG.md

@@ -1,3 +1,11 @@
+### 1.2.4
+
+2022-10-26 07:28
+
+#### FIXED
+
+- Backup file naming
+
 ### 1.2.3
 
 2022-10-25 17:05

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    na (1.2.3)
+    na (1.2.4)
       chronic (~> 0.10, >= 0.10.2)
       gli (~> 2.21.0)
       mdless (~> 1.0, >= 1.0.32)

data/README.md

@@ -9,7 +9,7 @@
 _If you're one of the rare people like me who find this useful, feel free to
 [buy me some coffee][donate]._
 
-The current version of `na` is 1.2.3
+The current version of `na` is 1.2.4
 .
 
 `na` ("next action") is a command line tool designed to make it easy to see what your next actions are for any project, right from the command line. It works with TaskPaper-formatted files (but any plain text format will do), looking for `@na` tags (or whatever you specify) in todo files in your current folder. 
@@ -63,7 +63,7 @@ SYNOPSIS
     na [global options] command [command options] [arguments...]
 
 VERSION
-    1.2.3
+    1.2.4
 
 GLOBAL OPTIONS
     -a, --[no-]add          - Add a next action (deprecated, for backwards compatibility)
@@ -382,7 +382,7 @@ You can specify a particular todo file using `--file PATH` or any todo from hist
 
 If more than one file is matched, a menu will be presented, multiple selections allowed. If multiple actions match the search within the selected file(s), a menu will be presented. If you have fzf installed, you can select one action to update with return, or use tab to mark multiple tasks to which the action will be applied. With gum you can use j, k, and x to mark multiple actions. Use the `--all` switch to force operation on all matched tasks, skipping the menu.
 
-Any time an update action is carried out, a backup of the file before modification will be made in the same directory with a `~` appended to the file extension (e.g. "marked.taskpaper" is backed up to "marked.taskpaper~"). Only one undo step is available, but if something goes wrong (and this feature is still experimental, so be wary), you can just copy the "~" file back to the original.
+Any time an update action is carried out, a backup of the file before modification will be made in the same directory with a `.` prepended and `.bak` appended (e.g. `marked.taskpaper` is copied to `.marked.taskpaper.bak`). Only one undo step is available, but if something goes wrong (and this feature is still experimental, so be wary), you can just copy the "~" file back to the original.
 
 You can specify a new project for an action (moving it) with `--proj PROJECT_PATH`. A project path is hierarchical, with each level separated by a colon or slash. If the project path provided roughly matches an existing project, e.g. "mark:bug" would match "Marked:Bugs", then that project will be used. If no match is found, na will offer to generate a new project/hierarchy for the path provided. Strings will be exact but the first letter will be uppercased.
 

data/lib/na/next_action.rb

@@ -751,7 +751,9 @@ module NA
     ## @param      target [String] The file to back up
     ##
     def backup_file(target)
-      FileUtils.cp(target, ".#{target}~")
+      backup_file = ".#{File.basename(target)}.bak"
+      dir = File.dirname(target)
+      FileUtils.cp(target, File.join(dir, backup_file))
     end
 
     ##

data/lib/na/version.rb

@@ -1,3 +1,3 @@
 module Na
-  VERSION = '1.2.3'
+  VERSION = '1.2.4'
 end

data/src/README.md

@@ -9,7 +9,7 @@
 _If you're one of the rare people like me who find this useful, feel free to
 [buy me some coffee][donate]._
 
-The current version of `na` is <!--VER-->1.2.2<!--END VER-->.
+The current version of `na` is <!--VER-->1.2.3<!--END VER-->.
 
 `na` ("next action") is a command line tool designed to make it easy to see what your next actions are for any project, right from the command line. It works with TaskPaper-formatted files (but any plain text format will do), looking for `@na` tags (or whatever you specify) in todo files in your current folder. 
 
@@ -158,7 +158,7 @@ You can specify a particular todo file using `--file PATH` or any todo from hist
 
 If more than one file is matched, a menu will be presented, multiple selections allowed. If multiple actions match the search within the selected file(s), a menu will be presented. If you have fzf installed, you can select one action to update with return, or use tab to mark multiple tasks to which the action will be applied. With gum you can use j, k, and x to mark multiple actions. Use the `--all` switch to force operation on all matched tasks, skipping the menu.
 
-Any time an update action is carried out, a backup of the file before modification will be made in the same directory with a `~` appended to the file extension (e.g. "marked.taskpaper" is backed up to "marked.taskpaper~"). Only one undo step is available, but if something goes wrong (and this feature is still experimental, so be wary), you can just copy the "~" file back to the original.
+Any time an update action is carried out, a backup of the file before modification will be made in the same directory with a `.` prepended and `.bak` appended (e.g. `marked.taskpaper` is copied to `.marked.taskpaper.bak`). Only one undo step is available, but if something goes wrong (and this feature is still experimental, so be wary), you can just copy the "~" file back to the original.
 
 You can specify a new project for an action (moving it) with `--proj PROJECT_PATH`. A project path is hierarchical, with each level separated by a colon or slash. If the project path provided roughly matches an existing project, e.g. "mark:bug" would match "Marked:Bugs", then that project will be used. If no match is found, na will offer to generate a new project/hierarchy for the path provided. Strings will be exact but the first letter will be uppercased.
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: na
 version: !ruby/object:Gem::Version
-  version: 1.2.3
+  version: 1.2.4
 platform: ruby
 authors:
 - Brett Terpstra
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-10-25 00:00:00.000000000 Z
+date: 2022-10-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake