tarman
tarman copied to clipboard
matejc
Backwards and shift-arrow navigation
Directory permissions cease the screen from populating each area, so there is not yet a conflict with that future implementation. My keyboard (HP netbook) also doesn't have PageUp/PageDown, so I was looking at holding down shift to do the same thing. Let me know what you think.
Backwards navigation:
lets say, we run tarman in /home/matej/workarea/tarman_synd/ directory.. and we select README.rst, then creates NewArchive.tar.gz right there, and reopen the tarman and select that archive and go to the deepest file which in this case is this README.rst and now we are here: /home/matej/workarea/tarman_synd/NewArchive.tar.gz/home/matej/workarea/tarman_synd
This is meant to work like that, by running tarman in some directory, you make it so-called the root of archive.
Maybe you could solve this .. by scanning the checked files on creation of archive and dynamically set the root to the highest file located in directory tree, i.e.: you have 2 files selected.. /home/matej/a/b/c/file1 and /home/matej/a/file2 then root can be set dynamically to the /home/matej/a and in archive you will have paths: b/c/file1 and file2. But I guess... this produces more problems than it solves, 1. user will not expect this and 2. there will be no way to set the root inside archive.
Shift+<arrow> is used for selecting files - generally in file browsers.
For keyboard keys you can look into ncdu curses application - http://dev.yorhel.nl/ncdu
Thanks for the try! :) And please do not take this personal, I am not enjoying turning down any contributions.
No worries at all, again this is just messing around with improvements for me :)
So if I understand correctly, there is a predefined "root_directory" which is being used to satisfy two functions: one to cease further parent directory changing, and one as a working directory in which to contstruct the tar file. My intention was to apply the change to the former; therefore, what if we have separate variables for each function?
I'll take a look at the keyboard shortcuts, I would like to add at least one more pair.
Thanks for looking into it!
One root directory is there for a reason, if you have /a/b/c/d/file2 and /a/b/file1 files and you run cd /a/b/c; tarman, your root for the archive will be /a/b/c and what is the use of going up if we can not archive file1 in the first place, because of root being /a/b/c?
One "root_directory" would be dynamically changing depending on the screen to which the user navigates and initiates a tar file creation (latter from my previous comment), and one (ideally the unit root directory '/') would simply be to allow the user to navigate to some parent directory. This grants the user the ability to create a tar file in any directory without the strict requirement be made that the tar-initiating-directory in question is some subdirectory of the path argument or $HOME (no path argument).
OK, you have a green light from me, but do not waste too much time on this, this application is meant to be for quick archive management therefore is quite ok if user quits and reopens tarman on other location, but I agree this would be a nice little feature.