(Mac) Search contents of Text file within ZIP
(Mac) Search contents of Text file within ZIP
Author
Discussion

dibbers006

Original Poster:

14,640 posts

249 months

Wednesday 22nd April 2020
quotequote all
The initial message was deleted from this topic on 12 December 2023 at 21:54

Trustmeimadoctor

14,370 posts

186 months

Wednesday 22nd April 2020
quotequote all
Possibly agent ransack sorry didnt spot the mac bit

Edited by Trustmeimadoctor on Wednesday 22 April 13:13

768

20,781 posts

127 months

Wednesday 22nd April 2020
quotequote all
unzip -c *.zip | grep something


Might be worth pushing into an elastic instance or similar though if it takes a long time to query over and you do it often.

Mr Pointy

13,420 posts

190 months

Wednesday 22nd April 2020
quotequote all
Buy a PC & let Windows index the zip files so you can search them?

(only slightly not serious)

eps

7,146 posts

300 months

Wednesday 22nd April 2020
quotequote all
How are your command line skills?

robsa

2,468 posts

215 months

Thursday 23rd April 2020
quotequote all
Mr Pointy said:
Buy a PC & let Windows index the zip files so you can search them?

(only slightly not serious)
No need.

grep -l [text to find] [files to look in]

So grep -l PistonHeads *.txt

Grep has options for case sensitivity and recursion

Although if it’s something simple finder will do it with a ‘find by content’ search.

eps

7,146 posts

300 months

Thursday 23rd April 2020
quotequote all
zipgrep to search inside zip files

mattley

3,039 posts

253 months

Thursday 23rd April 2020
quotequote all
What's the actual problem?


mattley

3,039 posts

253 months

Friday 24th April 2020
quotequote all
mattley said:
What's the actual problem?
dibbers006 said:
We've got automation software that routes files around the globe, processing along the way.

But due to the quantity of files and users, it's not always easy to see what issues occur, or where. Especially if they don't notice for a week that something is missing, or a file didn't make it to its destination.

I'm partly responsible for workflow. IT are infrastructure. Which can cause a disconnect.

Users aren't always tech savvy, and the different timezones all add to the high jinx!
So a legacy solution that doesn't scale well and no one's taking responsibility for the inevitable mess.

I can't answer your initial question, but I can offer some direction.

If you're only partly responsible for workflow you need to either be actually responsible for workflow and have the budget to implement a solution, or make someone else responsible for workflow so you can just get on with your job.


The solution is to centralise the data that's being passed around as documents and generally get a grip (i suspect you already know this) .

Also get an IT department that want to support innovation rather than legacy.