In Konqueror, open a directory containing several compressed files.
Select all of the files.
Open the popup context menu (right-click).
There is no option to compress those files into a new archive.
Bug or misconfiguration?
Darrell
In Konqueror, open a directory containing several compressed files.
Select all of the files.
Open the popup context menu (right-click).
There is no option to compress those files into a new archive.
Bug or misconfiguration?
Darrell
Sounds like a "feature" to prevent recompression of compressed files, which almost always inflates the resultant archive to a larger size than if it was compressed once.
Any thoughts from others on this list?
Tim
In Konqueror, open a directory
containing several compressed files.
Select all of the files.
Open the popup context menu (right-click).
There is no option to compress those files into a new
archive.
Bug or misconfiguration?
Sounds like a "feature" to prevent recompression of compressed files, which almost always inflates the resultant archive to a larger size than if it was compressed once.
Any thoughts from others on this list?
About where in the code would I try to study this? The "Compress" menu option does not appear at all. Only the Extract option. Kind of weird I never ran into this before.
I needed to create single archives of my Slackware 3.5.13 packages for easier downloading. I selected the files in Konqueror and then did the proverbial deer in the headlights act. I just stared. :)
I had to archive the files manually in konsole. Doable for me, but not for many people. That's why I'm asking whether this is a bug or configuration problem. To me, there is no reason why a person can't archive a set of archived files.
Darrell
In Konqueror, open a directory
containing several compressed files.
Select all of the files.
Open the popup context menu (right-click).
There is no option to compress those files into a new
archive.
Bug or misconfiguration?
Sounds like a "feature" to prevent recompression of compressed files, which almost always inflates the resultant archive to a larger size than if it was compressed once.
Any thoughts from others on this list?
About where in the code would I try to study this? The "Compress" menu option does not appear at all. Only the Extract option. Kind of weird I never ran into this before.
I needed to create single archives of my Slackware 3.5.13 packages for easier downloading. I selected the files in Konqueror and then did the proverbial deer in the headlights act. I just stared. :)
I had to archive the files manually in konsole. Doable for me, but not for many people. That's why I'm asking whether this is a bug or configuration problem. To me, there is no reason why a person can't archive a set of archived files.
Darrell
Correct. This sounds like a bug.
The issue is probably in the konqueror service menu handling/mimetype code in tdeutils or tdebase--I suspect that when compressed files are detected the service menu providing "Extract" overrides the default service menu that provides the "Compress" options.
Tim
On Sat, Jan 14, 2012 at 2:25 AM, Timothy Pearson < kb9vqf@pearsoncomputing.net> wrote:
In Konqueror, open a directory
containing several compressed files.
Select all of the files.
Open the popup context menu (right-click).
There is no option to compress those files into a new
archive.
Bug or misconfiguration?
Sounds like a "feature" to prevent recompression of compressed files, which almost always inflates the resultant archive to a larger size than if it was compressed once.
Any thoughts from others on this list?
About where in the code would I try to study this? The "Compress" menu option does not appear at all. Only the Extract option. Kind of weird I never ran into this before.
I needed to create single archives of my Slackware 3.5.13 packages for easier downloading. I selected the files in Konqueror and then did the proverbial deer in the headlights act. I just stared. :)
I had to archive the files manually in konsole. Doable for me, but not
for
many people. That's why I'm asking whether this is a bug or configuration problem. To me, there is no reason why a person can't archive a set of archived files.
Darrell
Correct. This sounds like a bug.
The issue is probably in the konqueror service menu handling/mimetype code in tdeutils or tdebase--I suspect that when compressed files are detected the service menu providing "Extract" overrides the default service menu that provides the "Compress" options.
Has a bug report been filed? If a bug, then it could at least show an option not to compress but to simple mesh together in a TAR file.
Best regards, Tiago
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Has a bug report been filed? If a bug, then it could at least show an option not to compress but to simple mesh together in a TAR file. Best regards,
No bug report filed because I can't reproduce the error. Can you?
That's why I like to run things by others here in the list. Sometimes just weird things happen, sometimes there 's a short between the headphones.
Perhaps some day I'll reproduce the event and then I'll try to be more observant about environment, user, settings, etc. I know I saw what I described, but right now there is a "Compress" option in the pop up menu. I have no explanation. :)
Darrell
On Sat, 21 Jan 2012 16:55:18 -0800 (PST) Darrell Anderson humanreadable@yahoo.com wrote:
Has a bug report been filed? If a bug, then it could at least show an option not to compress but to simple mesh together in a TAR file. Best regards,
No bug report filed because I can't reproduce the error. Can you?
That's why I like to run things by others here in the list. Sometimes just weird things happen, sometimes there 's a short between the headphones.
Perhaps some day I'll reproduce the event and then I'll try to be more observant about environment, user, settings, etc. I know I saw what I described, but right now there is a "Compress" option in the pop up menu. I have no explanation. :)
I can reproduce the behaviour you described in KDE 3.5.10, so it did exist at some point but may now have been fixed (or not). However, I should probably note that I get the "Extract" option replacing "Compress" only if all the files I select are recognized as being compressed--if I select, say, two .zip files and a .txt, the "Compress" option remains available.
I can reproduce the behaviour you described in KDE 3.5.10, so it did exist at some point but may now have been fixed (or not). However, I should probably note that I get the "Extract" option replacing "Compress" only if all the files I select are recognized as being compressed--if I select, say, two .zip files and a .txt, the "Compress" option remains available.
What you describe rang a bell. I tried a directory only with compressed files. I still can't repeat the problem here with either 3.5.10 or R14_GIT. My head hurts. :)
Darrell
On Sat, 21 Jan 2012 19:54:04 -0800 (PST) Darrell Anderson humanreadable@yahoo.com wrote:
I can reproduce the behaviour you described in KDE 3.5.10, so it did exist at some point but may now have been fixed (or not). However, I should probably note that I get the "Extract" option replacing "Compress" only if all the files I select are recognized as being compressed--if I select, say, two .zip files and a .txt, the "Compress" option remains available.
What you describe rang a bell. I tried a directory only with compressed files. I still can't repeat the problem here with either 3.5.10 or R14_GIT. My head hurts. :)
Mine is starting to do the same. The obvious (but likely not helpful) question is, what did you change?
What you describe rang a bell. I tried a directory
only with compressed files.
I still can't repeat the problem here with either
3.5.10 or R14_GIT. My head
hurts. :)
Mine is starting to do the same. The obvious (but likely not helpful) question is, what did you change?
I always ask myself that. :) In this case, the appropriate question is what was the exact scenario that caused this anomaly? I saw what I described, but now can't duplicate the exact situation. Someday I'll absent mindedly do just that and then I'll take notes. :)
Darrell