-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zip archives with files having phrase `makefile' in name treat them as makefiles #4419
Comments
|
|
|
I have checked that patch and it seems to work but I found analogical cases to those with .pdfs. Whenever you pack .pdf or .webm or .1/.2/.[0-9], or .jpg/.png/.gif/.bmp/.pnm/any image, same thing happens. I guess it has nothing to do with a suffix and everything with a recognized extension. Zip, rar, 7z, tar, whatever archive should not automatically execute any file in it in any case. |
Replying to cieply:
What do you mean exactly? |
I said about pdfs in a first post. It happens with other extensions as well. If there is a file, with known suffix and is zipped then on enter it will be executed. It might make sens with .gz, .bz2, etc. but not with multi file archives like tar, zip, rar.
Now you can't enter these archives. Instead they get "executed". what is executed? Some external, gui unarchiver in my case, which I don't necessarily want to use, using mc. You can't even view contents with F3. You get an error: <standard input>:2: warning: can't find character with input code 3
Same with files like pdfs, images, and so on.
Sometimes if you add more files it stops doing that.
But in any way, it wasn't the case before. |
Replying to cieply:
Everything fine for me. I can enter to these archives.
In #4141 format of mc.ext was changed and mc.ext parser was rewritten. Such behaviour was fixed too. |
Not for me though.
Well, there is only 4.8.28 available for download.
BTW. if changes are so deep, why won't you call new version 4.9? Maybe keeping build count. That would be 4.9.29. Major version and then minor are more important than "build" or whatever you call the last number. |
We will try to make a new release over the holidays. It's long due, but very unfortunately, I was not able to find time to support andrew_b so far. Had to deal with some unexpected infra migration in the time allocated for release instead. |
It was a digression. I put it in right thread (#4357).
I wondered how to fix it, not when a new release is going to be. |
|
|
Wanted to bump this issue as version 4.8.30 still has this problem. Although constructions like 'blabla-makefile' are not a problem anymore, 'makefile' or 'makefile...blabla' are.
F3
ENTER
Also noticed that rar and 7z have no issue with these names.
Wonder whether it has something to do with uzip. |
Makefile. makefile and Makefile.zip are handled with following section in mc.ext.ini:
Regex=^[Mm]akefile means that file name begins with Makefile or makefile. Makefile.zip is matched to that.
Fix is handle of Makefile as whole word:
Makefile.zip isn't handled as zip-file because sections [zip-by-shell] and [zip-by-type] are below [Makefile]. |
|
|
the regex was intentionally loose, to match Makefile.in and such.
the problem is part of a bigger topic, currently discussed in #4128. |
Important
This issue was migrated from Trac:
cieply
(worker@….pl)I found this issue recently.
Zip archives with files having phrase `makefile' in name treat them as makefiles and upon enter mc tries to read paramaters for makefile and execute it.
I attached few samples.
Just try to enter/view them and you will see.
Even worse it is with compressed pdfs. They don't even need to use `.pdf' extension, they will be picked up anyway. Trying to view zipped pdf ends up with error window "Syntax Warning: May not be a PDF file (continuing anyway)" and one cannot view nor enter it. All one can do is to manually unzip it end then it can be read.
Example:
These shouldn't work like that. One should be able to enter to zip archive and view it if they want, not to be treated like scripts.
Note
Original attachments:
cieply
(worker@….pl) onDec 13, 2022 at 1:33 UTC
The text was updated successfully, but these errors were encountered: