Do

typing a path to a file is different to selecting the file from the results window

Bug #349203 reported by Jonathan Austin on 2009-03-26
2
Affects Status Importance Assigned to Milestone
Do
Low
Unassigned

Bug Description

If I type '/etc/X11/xorg.conf' in to Do and then try and do 'Open With', that isn't an option

BUT

If I do
/etc/X11/ <cursor left to enter the folder> xorg.conf and then try 'open with' it IS there

This seems counterintuitive, it is much more work to press the cursor not the slash as I am really in the habit of typing paths with / in them

Robert Dyer (psybers) on 2009-06-18
Changed in do:
importance: Undecided → Low
status: New → Fix Committed
Robert Dyer (psybers) wrote :

Not sure why I marked this as fixed, I'm still seeing this behavior...

Changed in do:
status: Fix Committed → Confirmed
Joe Soulbringer (joesolbrig) wrote :

This bugs should be marked unfixed and expanded to note that Do simply gets the file type wrong too often.

I'm seeing that Do sometimes has the default action of "running" a ".pdf" file, which does nothing and sometimes the default action of opening a different ".pdf" file, which successfully opens it in the PDF reader.

I'm investigating this behavior...

On Tue, 2009-07-28 at 01:24 +0000, Joe Soulbringer wrote:
> This bugs should be marked unfixed and expanded to note that Do simply
> gets the file type wrong too often.
>
> I'm seeing that Do sometimes has the default action of "running" a
> ".pdf" file, which does nothing and sometimes the default action of
> opening a different ".pdf" file, which successfully opens it in the PDF
> reader.
>
> I'm investigating this behavior...
>
This is almost certainly because the pdf that Do tries to "run" is
marked as executable. Do trusts that this means that it can be run, and
since "run" is almost always the most used action, that's the default
action that gets picked.

There really isn't any good way for Do to determine that the pdf marked
as executable can't actually be executed except by attempting to run it,
something that won't be a particularly good idea if it turns out that
you _can_ run it - simply browsing files would start lots of
applications!

Joe Soulbringer (joesolbrig) wrote :

Well indeed, chmod solved that problem...

Robert Dyer (psybers) wrote :

Yes, Chris is correct here. I'd like to add in that if you try opening a PDF in Nautilus marked as non-exec, it opens it in the PDF viewer. If you double click a PDF file marked +x it will prompt you to run, display, cancel, etc.

For GNOME Do however, we don't really want to prompt you so selecting 'run' as the default action makes the most sense, as annoying as that may be for files with incorrect permissions. :-)

I'd also like to point out we have run on a tangent from the bug report. Please add information pertaining to the reported bug if you have any.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers