El mar, 17-02-2004 a las 16:41, Dave Camp escribió: > I think it would be reasonably to expect the cwd of executed scripts, > programs, etc. to be the folder being viewed (and ~ in cases where there > is no folder being viewed, such as the run dialog). Setting the cwd to > the location of the binary causes problems (such as apps running in > /usr/bin) and is inconsistent with any current implementations. Good idea, but not enough. 1) This introduces a new corner case (if file is shell script, then...) 2) This behavior should also trigger upon opening documents, not just shell scripts. This is so I can do a Save as... to save in the same folder where the file was. I cannot stress this enough: if I double click a document in /var/XXX/ZZZ, I *expect* the app to share that location instead of changing to $HOME. I don't know what was the guy who "changed nautilus to cwd $HOME before running an app" thinking... perhaps he thought he would hide broken apps' nuisances this way. It is organically better to fix broken apps instead of relying on someone else to provide workarounds. > > -dave > > On Tue, 2004-02-17 at 16:26, Eugenia Loli-Queru wrote: > > You can't base your argument on "people should learn how to write proper > > shell scripts", because if the terminal knows how to deal with "broken" > > shell scripts (which aren't really broken as I showed in that screenshot I > > linked a few days ago), so it should Nautilus. Users expect it to work, > > because it works by using any terminal. > > > > Rgds, > > Eugenia > > > > > > >>>>>>>>>>>>>>>>>> > > El mar, 17-02-2004 a las 13:38, Ross Burton escribió: > > > On Tue, 2004-02-17 at 18:09, Manuel Amador (Rudd-O) wrote: > > > > > Well. You don't have to do that. Just put e.g. "cd `dirname $0`" on > > the > > > > > first line of the script. > > > > > > > > You see, this will fail if directories have spaces. > > > > > > cd "`dirname "$0"`" > > > > > > > This is also a non-sequitur for regular home users. > > > > > > Home users don't write sh scripts, and people who can code shell scripts > > > should know a little about shell escaping and path manipulation. > > > > > > Ross > > > > Ross, this is a good response to someone like Eugenia or me. Not a good > > response to the general public. > > > > LimeWire installs itself as a graphical application. Why on Earth do > > you expect LimeWire users will modify the shell script to cope with a > > Nautilus deficiency? For all they care, the LimeWire icon "works on > > KDE, fails on GNOME, this Linux crap is shit". > > > > Get the point? > > > > The correct, expected behavior from Nautilus or any file manager is that > > "if I double-click an icon, the current directory is the one I had > > opened in my face". People coming from Windows and Mac OS will expect > > that. It's a reasonable expectation with nothing against it. Breaking > > that expectation is wrong. > > > > People who want to save a file which doesn't yet exist may find good use > > in CWDing to the home dir (e.g. for launching apps in the foot menu). > > People who want to work with an existing file (they doubleclicked an > > icon on a nautilus window) find no good use in this. -- Manuel Amador (Rudd-O) GPG key ID: 0xC1033CAD at keyserver.net
Attachment:
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente