01micko wrote:Yes.. RTFM .. "Remove fake gz extension" (stated in the 'download' table; "description" row).Lobster wrote:Am I at fault?
I don't like the trend either but hey, I'm _not_ a trend setter.
MochiMoppel wrote:@stemsee MiView? Why not "MM MiEV"? Mitsubish Motors i-MiEV. Oh, I smell trouble.
i call it (and call it with) mmv--renamed it mmv so it's quicker from the terminal. (Double) eM Vee for MochiMoppel (file) Viewer is the rationale for The Bull With The Em Horns (yeah, they're more positioned like ears) Icon--pet gives both a dmv (Department of Motor Vehicles, speaking of mitsubishi (--and i was pretty fond of my 91 dsm gsx) and speaking of many, many files...) and an mmv version of the icon. that ring through the bull's nose is supposed to be in the shape of a directory folder/that directory folder thing's supposed to be a ring in da bull MV's nose.MochiMoppel wrote:New question: Could someone suggest a better name? Quickview is already taken. .
Something like this should handle most of them:MochiMoppel wrote:It does not work for initrd.gz. I would ge grateful for any help to improve this feature since I don't know much about archives.
Code: Select all
--- mm_view_20170406 2017-04-06 15:02:30.573360371 +0200
+++ mm_view_20170406_new 2017-04-06 15:19:08.486695165 +0200
@@ -205,7 +205,7 @@
;;
### ARCHIVES ###
- *│*gzip*|*│*x-xz*|*│*x-bzip2*|*'.deb '*) # .tar, .pet , .txz, .gz , .gzip, .bzip2, .deb
+ *│*gzip*|*│*x-xz*|*│*x-bzip2*|*'.deb '*|*'/initrd'*) # .tar, .pet , .txz, .gz , .gzip, .bzip2, .deb, initrd*
MESSAGE=$'\n\tTry F1 to view package content'
;;
@@ -255,6 +255,19 @@
;;
### LIST ARCHIVE CONTENT ###
+ *'/initrd'*)
+ COMPRESSION=${vSTATUSBAR##*x-} # '/initrd.gz │ application/x-gzip; charset=binary' => 'gzip; charset=binary'
+ COMPRESSION=${COMPRESSION##*application/} # '/initrd.gz | application/gzip; charset=binary' => 'gzip; charset=binary'
+ COMPRESSION=${COMPRESSION%;*} # 'gzip; charset=binary' => 'gzip'
+ case $COMPRESSION in
+ gzip) CMND='gunzip -c -d' ;;
+ bzip2) CMND='bunzip2 -c -d' ;;
+ xz|lzma) CMND='unxz -c -d' ;;
+ lz4) CMND='unlz4 -c -d' ;;
+ *) CMND='cat' ;; # not compressed
+ esac
+ ${CMND} "$vCHOOSER" | cpio -ivt > $MSGFILE # the output isn't really pretty with non-monospaced font
+ ;;
*│*gzip*|*│*x-xz*|*│*x-bzip2*) # extensions .tar, .pet , .txz, .gz , .gzip, .bzip2
COMPRESSION=${vSTATUSBAR##*x-} # '/foo.pet │ application/x-gzip; charset=binary' => 'gzip; charset=binary'
COMPRESSION=${COMPRESSION%;*} # 'gzip; charset=binary' => 'gzip'
Yes, like with the file command.greengeek wrote:Brilliant. Love the F1 functionality (and the prompts to try it...).
I notice if I click on something like /root/Startup/parcellite the view pane displays nothing. Would it be possible to display something like "symlink to.." or even just "symlink"?
Also with /root/Startup/network_tray there is no view pane display (possibly might be in future versions if a suitable viewer/decoder/interpreter is available) - but in the meantime might it be acceptable for the viewer to say something such as: "unsupported file type" or "C encoded file" etc etc?
Code: Select all
file $FILECode: Select all
find $FILENAME -type f -exec file -b '{}' \; -printf '%s\n'
I will use the code for my next update with a small change: I will use the busybox version of cpio. The output format is less ugly and can be easier turned into a palatable format for proportional fonts.Thanks for the reply. I see from your reply to misko_2083 that even for an unviewable file you display the "file" result in the status bar - would you also consider displaying something in the display pane which prompts the user to view the status bar? Maybe something such as "contents not readable" ?MochiMoppel wrote:@greengeek When the target of a symlink is not displayed then not because it's a symlink but because the target is not viewable. And when nothing can be displayed I prefer to display nothing
Hi MochiMoppel,MochiMoppel wrote:Update 2017-04-06 (see also initial post)
Directory info
F1 will add information about the disk usage of a directory's subfolders. Since subfolders are sorted by size this will make is easy to spot the biggest "disk eaters". IMHO a useful feature.
.
At least in case of 'gzip', you can't - file (at least versions 5.04, 5.28 & latest) uses 'x-gzip', however Fatdog uses this patch from Debian:MochiMoppel wrote:can I be sure that MIME is always labeled as 'x-gzip' and 'x-xz' and not 'gzip' and 'xz'?
Code: Select all
Description: Report gz as application/gzip
Author: Daniel Baumann <mail@daniel-baumann.ch>
Bug-Debian: https://bugs.debian.org/688886
Last-Update: 2015-09-18
--- a/magic/Magdir/compress
+++ b/magic/Magdir/compress
@@ -21,7 +21,7 @@
# * Produce shorter output - notably, only report compression methods
# other than 8 ("deflate", the only method defined in RFC 1952).
0 string \037\213 gzip compressed data
-!:mime application/x-gzip
+!:mime application/gzip
!:strength * 2
>2 byte <8 \b, reserved method
>2 byte >8 \b, unknown methodPerhaps using *gzip*) (or even *g*zip*) instead of gzip) in case statement would be more reliable...https://tools.ietf.org/html/rfc6713 wrote:Some applications have informally used media types including application/gzip-compressed, application/gzipped, application/x-gunzip, application/x-gzip, application/x-gzip-compressed, and gzip/document to describe data compressed with gzip.
Yeah, it shouldn't have problems with auto-detecting the used compression method.I also don't know if the tar command really needs the -I option since it seems to sniff the compression program without it.
Then you're gonna hate this - just checked in UExtract and files with the following extensions can be seen as application/gzip:Seems that MIME application/x-gzip can be a lot of things. I don't like that
Accepted. I think my post was badly written - i was not re-requesting symlink info to be displayed, just asking if file types (for non-viewable files) could be highlighted in some way.MochiMoppel wrote:@greengeek As I already tried to explain: In principle there is no relation between symlink and viewability, .
I was expecting too much, I understand now that the program will not display contents of a sym-linked directory in the right-side window.MochiMoppel wrote:
@perdido I'm not sure what you are after. The behavior you describe is normal and intended, but maybe not well understood and the "no subdirectories" message is irritating ( a not dereferenced symlink can't have subdirectories by definition). After lot of hair pulling I concluded that it would be best to avoid any ambiguities by treating links like empty directories: Just a hint that it's a symlink to <target> and no additional F1 info. And while I'm at it I will do the same for the /proc directory. Just a hint that it's a virtual file system. Avoids needless processing and delays for calculating useless information.
Yes, I missed that. I was attempting to use [esc] to go backwards in the directory structure in the left-side window.Regarding [Esc]: Plans? It's already implemented. The [Esc] key serves as the panic key for stopping autoplay and was introduced with Update 2017-02-04 ("To stop the audio: Press ESC key or change to non-audio file or close the window or dbl-click the file, which will stop ffplay and start to play the file in the default player.")
.
Code: Select all
do_tgz_stuff(){
#template
}
do_gz_stuff(){
#template
}
case "$filename" in
*.tar.gz|*.tar.gzip|*.tgz)do_tgz_stuff "$filename";;
*.gz|*.gzip)do_gz_stuff "$filename";;
#more here
esac
Code: Select all
set_handler(){
#$1 is the name of the variable you want to set
#after shift the remaining $@ are executables you want to check for
var="$1"
shift
while ! type -p "$1" 2>&1 >/dev/null; do
shift #not found so go to next candidate
done
#this sets the variable to the value
eval $var=\"\$1\"
}
#example usage
#note that there is no $ when you pass Do_sh to the function
[ "$Do_sh" ] || set_handler Do_sh loksh dash hush ash sh bash
echo "$Do_sh is set as the preferred handler for .sh files"
Thanks. Currently I'm content with the speed. I'm more concerned with the correctness but haven't seen serious problems so far.technosaurus wrote:If you want really fast MIME type detection by extension only first and then by magic values at an offset, you can use my simple MIMEtype program
Yes, I can, but I shouldn'tAlso rather than hardcoding urxvt, bash etc, you can use $TERM and $SHELL ... or for a text editor $EDITOR and web browser $BROWSER
. Using these global variables (if that's what you mean and not locally assigned variables) I would end up in Slacko and maybe other Puppies with mp as $EDITOR and the (non existent) rxvt-unicode as $TERM. Even the global "Puppy variable" $DEFAULTTEXTEDITOR (in Slacko assigned to Geany) would be problematic since I can't be sure that the user hasn't changed his default editor after starting X. Hardcoding gives me control and avoids using programs the script is not designed for.IIRC converting pdf to an image can be done relatively easy with command line tools already available in Puppy, but then the question comes up if this is really worth it. However where I see a real potential are formats for which no suitable program is installed. In such cases an image could be a helpful work around and would be better than viewing nothing at all.for this thread, the output to png and svg are the most significant (convert the first page of a pdf to an image for display)