On Sun, 18 Jan 2009 17:23:58 +1100 <tpgww@xxxxxxxxxxx> wrote: > On Sun, 18 Jan 2009 17:06:58 +1100 > <tpgww@xxxxxxxxxxx> wrote: > > One further question, below. > > > > When clicking on image files with jpg or jpeg suffixes, emelfm2 sometimes > > > throws up an 'ambiguous filetype' dialog, asking "What would you like to > > > do with ..' > > > > > > If I click 'open', it opens and displays the file using the app I have > > > set as the first action in config - in my case this opens with xzgv. > > > > > > emelfm2 does not exhibit this behavior with all jpegs, some it just > > > opens. I am not sure what the differentiating factor is. > Does the file have executable permission ? (in which case, there's currently > no check for it being a 'real' executable item, so you need specify whether > to run it) I often bump into this issue when browsing Fat/NTFS partitions, where image files get the "what would you like to do...?" dialogue since they are both executable and recognised by extension. How about a configuration setting that goes something like: "Don't attempt to execute files with a known extension"? That would "solve" the ambiguity problem when dealing with this scenario (plus, I am not sure what kind of executable file with a known extension you'd really want to execute, even .exe files would be opened with wine rather than be executed directly). Walther. > > Does the dialog open repeatably with particular file(s) ? > > If so, what is the name of such a file ? > > What does 'info' menu-item tell you about such file ? > > What is the tooltip for the 'open' button in the dialog ? > > Have you enabled the case-insensitive option ? > > > > > The check for which action to run involves a left-to-right scan for each > > '.' in the filename (ignoring a leading '.' if any). There's no trimming of > > any whitespace, which could be a cause for a mismatch. > > > > > Can the dialog be disabled and the likely filetype assumed with the > > > action just being taken? > > No. If the filetype/action are known, there should be no dialog, and if not > > known, you do need it. > > > > > If not, can short circuiting this dialog and just executing the likely > > > action instead be added as an option? > > Again, if an appropriate action exists, there should be no dialog. We > > should find and fix the source of the problem, I think. Hence the questions > > above. > > > > I gather you are using emelFM2 v.0.4. The current release is 0.5 and 0.5.1 > > is imminent. It would be easier for me to investigate and debug current > > code, so any change of an upgrade at your end ? > > Regards > Tom > > > -- > Users can unsubscribe from the list by sending email to > emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by > logging into the web interface. -- Users can unsubscribe from the list by sending email to emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by logging into the web interface.