xvoland/extract

Bash/Zsh function for extract: .zip, .rar, .bz2, .gz, .zlib, .tar, .tbz2, .tgz, .Z, .7z, .xz, .exe, .tar.bz2, .tar.gz, .tar.xz, etc.

extract's Issues

Request: zlib support

Hi,

Just wanted to request adding zlib support. Sorry if this isn't the right way to ask. I came across my first .zlib file. There is a tool called zlib-flate, installed as part of qpdf that works - http://manpages.ubuntu.com/manpages/trusty/man1/zlib-flate.1.html - but of course it would be handy to have it within extract :)

Thank you

DMG files

Sorry, don't know how to pull-request, but DMG (Apple Disk iMaGe, like an ISO) is an archive format that can be opened with 7z, so I just added it to the case statement:

.7z|.dmg)

Invalid path argument given to uncompression programs

Since commit 2f89a4a and the "make dir" removal the function gives invalid compressed file path to uncompression programs. ../"$1" should be either transformed to "$1" or turned into a variable (path for instance) :

local path="$1"
# local basename=${1%.*}
# mkdir $basename && cd $basename 
# path="../$1"

extract multiple files

Today I ran:

extract *.zip

but it extracted only the first archive.

Would it be possible to incorporate multiple files extraction?

gzip: stdin: not in gzip format

If .tar not compressed whith gzip:

zip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

touch hello.txt
tar -cvf foo.tar hello.txt
tar -czvf foo2.tar hello.txt

file foo*
foo.tar: POSIX tar archive (GNU)
foo2.tar:  gzip compressed data, from Unix, original size modulo 2^32 10240

Extract on PATH

Would you accept patches to make this executable instead?

I am locally making it "executable", but

Extract/extract.sh

Lines 4 to 5 in dda4c33

	SAVEIFS=$IFS
	IFS=$(echo -en "\n\b")

lines confuse me as how to handle it (or why are they there in the first place).

I think that 42c38af should be solved "externally" [i.e. user is responsible to give a correct path], rather you trying to "mask" it.

adding this to npm?

Would you be interested in adding to this a nodejs npm package, so that it can be easier to install globally? (basically a helper for workstation stuff)

I suppose it would be installed via:

npm install -g extract-cli

What if file has a space character in filename?

Hi,

This extractor works great but if the filename has a space character it fails to extract even if I use " or '.
It says file not exists because it tried to use only the sup before the first space.

If it's not possible due to bash limitation it would be helpful to mention it in README.

Log Files

Awesome Requirements Fulfilled with this Extractor.

Are there any Workarounds to have a logs file to save logs in /var/log directory? Thanks in advance if you can help here.

bash script and function confusion

Hello correct me if I'm wrong but,

• doing PATH=script_dir/extract.sh:$PATH seems highly irregular
• It doesn't actually work, the bash function extract is not being run anywhere

I propose to change the README.md so that the installation step of adding the file to path is:

export PATH="<path_to_file>":"$PATH"

("$PATH" so that any possible preexisting spaces in the path are properly escaped)
and that the extract.sh has an additional line:

extract "$@"

Relying on Extension

While I'm sure it works most of the time, what about files which don't have a traditional extension, or one at all?

EDIT:

Okay, basically, this is what I had in mind. Thought I'd just write it myself as I figured it would be pretty neat:

https://github.com/terminalforlife/miscellaneous/blob/dev/unpack

Do you think this approach is something you would consider incorporating into your function?

problem of extract .tar file

in tar version of 1.26, extract a .tar file with tar zxvf have error of

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

and .tar file must extract with tar xvf in version of 1.26

lessmsi

better for MSI files

https://github.com/activescott/lessmsi

Include a LICENSE

The README.md does specify the MIT license, but you should include the license text since the MIT license requires it be provided in order for others to use your code:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Preferably, it should be in a separate LICENSE file. Plus, GitHub will give you a nifty little icon in the top commit bar, if you do use a LICENSE file.