Written by albertz the 31 Aug 10 at 17:35.
Category: System.
Related project:
Nothing/Others.
Status: New
Rationale
You have the same on MacOSX: There is an "open" command you can use in your shell and it will open a file with the system default application.
On Linux/Unix, it is quite similar to what xdg-open does.
For people who don't know about xdg-open and/or who are familiar with MacOSX and/or who want the shell to behave more natural, it would be nice to have the command "open" just behave this way.
1. So "open" breaks the expectation of a former mac user. Changing the functionality breaks the expectation of a Linux user...
2. Changing "open" might also break other software
3. If you prefer open to do something else don't force it to everyone else - just set an alias on your local machine. Btw I use the alias o=gnome-open (o is short and gnome-open rocks :p)
4. in /bin should only be fundamental functionality to boot a basic system up (that is not x, not gnome,...) So it would be /usr/bin/ anyway .
overall -1
Darwin Survivor(Brainstorm moderator)
wrote on the 1 Sep 10 at 09:43
I've been through the conversion phase and I know how painful it can be when there are a couple things that you can never remember. The problem is that while this seems like a simple change, it is a very slippery slope. If this kind of change is approved, it could lead to adding everything from "del/move/copy" from windows to turning linux into an attempted clone of every other OS in the world.
Regardless of the reasons behind the suggestion, the change itself appears to be quite reasonable. How many actually use the open command as it is now? I at least would definitely use the suggested one.
Darwin Survivor(Brainstorm moderator)
wrote on the 2 Sep 10 at 09:13
You know, there has been a recent increase in the number of suggested terminal and filesystem (case sensitivity) changes. It might be a cool idea if ubuntu created a few standard .bashrc files that people could download. Each could be targeted at new users from different operating systems.
Mac users could get an "open" alias, windows users could get an "exec" alias, etc.
a .bashrc wont fix filesystem case sensitivity.. This must be an option built into the kernel or filesystem (because you can't change from a case insensitive filesystem back to a sensitive filesystem without proper checks safely).
Darwin Survivor(Brainstorm moderator)
wrote on the 2 Sep 10 at 23:26
Ok, just to clarify, what part of the case-sensitive filesystem are you worried about? Are you worried that people will accidentally create 2 files with different cases (expecting a "replace file" dialog) or that people will not be able to find their files because they searched with the wrong case?