This is barely a bug, but still seemed worth a quick mention. I've got a project file in my /opt/ directory, which I'm using for fooling around with my local apache installation. I do not have write permission in /opt/, because I'm not logged in as admin (a habit from the early days of great bash disasters). When I go to 'create a file' in the project drawer and choose a location within /opt/ to create it, clicking 'ok' fails silently – no error message or request to authorize. In other circumstances I've seen TextMate ask for authorization as admin, and it would be nice if it did the same here.
Like I said, hardly a crucial issue, there are a million ways around it, but it seems like it ought to work.
I'm using build 1414, if that makes any difference.
Yrs, Eric
On Aug 28, 2007, at 5:18 AM, Eric Abrahamsen wrote:
[...] When I go to 'create a file' in the project drawer and choose a location within /opt/ to create it, clicking 'ok' fails silently – no error message or request to authorize [...]
The problem is that file creation is handled 100% by a shell command, and TM itself has very little knowledge about what the script will actually do. This was done in the name of flexibility, e.g. the file creation could also create a header, use whatever preprocessor it wanted for the template, setup stuff, etc. -- but it has the downside that each template basically has to re-invent all what one could want to do when creating files (like asking for authorization when the folder is not writable by current user, etc.).
The current template system is planned to be replaced by a better abstraction, and I will keep the authorization aspect in mind.
Thanks! Interesting to get a look at the inner workings....
On Aug 29, 2007, at 2:03 AM, Allan Odgaard wrote:
On Aug 28, 2007, at 5:18 AM, Eric Abrahamsen wrote:
[...] When I go to 'create a file' in the project drawer and choose a location within /opt/ to create it, clicking 'ok' fails silently – no error message or request to authorize [...]
The problem is that file creation is handled 100% by a shell command, and TM itself has very little knowledge about what the script will actually do. This was done in the name of flexibility, e.g. the file creation could also create a header, use whatever preprocessor it wanted for the template, setup stuff, etc. -- but it has the downside that each template basically has to re-invent all what one could want to do when creating files (like asking for authorization when the folder is not writable by current user, etc.).
The current template system is planned to be replaced by a better abstraction, and I will keep the authorization aspect in mind.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Allan Odgaard -
Eric Abrahamsen