clicking on executable script opens it in scratch
Bug #1089775 reported by
Simon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Files |
Fix Released
|
Medium
|
Jeremy Wootten |
Bug Description
Steps to reproduce:
1. Create an empty file "test.sh"
2. Paste "#!/bin/bash" in it, save and close it.
3. Set the file to be executable (in right click -> Properties)
4. Double click on the file. It will open in scratch.
5. Close scratch.
6. Double click on the file again.
At step 6, the file will be executed. This should happen on step 4 instead of opening scratch.
Related branches
lp:~jeremywootten/pantheon-files/fix-file-will-not-open
- elementary Apps team: Pending requested
-
Diff: 25 lines (+1/-6)1 file modifiedlibcore/gof-file.c (+1/-6)
description: | updated |
summary: |
- Double clicking on executable script does nothing + Double clicking on executable script opens it in scratch |
Changed in pantheon-files: | |
status: | New → Confirmed |
summary: |
- Double clicking on executable script opens it in scratch + clicking on executable script opens it in scratch |
Changed in pantheon-files: | |
importance: | Undecided → Medium |
assignee: | nobody → elementary UX Team (elementary-design) |
Changed in pantheon-files: | |
status: | Confirmed → In Progress |
assignee: | elementary UX (elementary-design) → Jeremy Wootten (jeremywootten) |
Changed in pantheon-files: | |
milestone: | none → freya-rc1 |
Changed in pantheon-files: | |
status: | In Progress → Fix Committed |
Changed in pantheon-files: | |
milestone: | freya-rc1 → 0.2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The expected behavior when there exists a shell script marked as executable that begins with "#!/bin/bash" is to execute it, not to open it in scratch.
When I follow your steps, the script is never executed - it is always opened in Scratch. This is clearly a bug.
When pantheon-files is closed and reopened, the file works as expected (i.e. double clicking on it executes the script).
If I interchange steps 2 and 3 of your test, the shell script works as it should on the first try (it will be executed).