<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>Le 3 nov. 06 à 05:24, Allan Odgaard a écrit :</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">There basically is no way you can currently do what you want -- but since ‘sudo mate’ is (by several users) expected to transfer the super user privileges to TextMate (for just that file), I will look into how this could possibly be pulled off sometime in the future (it would be a nice little feature).</FONT></DIV></BLOCKQUOTE><BR></DIV><DIV>this little feature is allready implemented in SubEthaEdit... (afaik)</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>something i didn't understood, suppose i write a wrapper to mate "sudo_mate" even launching TextMate like that :</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>sudo /Applications/TextMate/TextMate.app/Contents/MacOS/TextMate blahblah</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>textmate isn't aware of the user ? because of internals, that's to say after lauchning the parent process above another child is open which doesn't have the same perms ????</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>best,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Yvon</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>