Is BBEdit 7 (full version) a Carbon or Cocoa application? If the .app extension is any indicator, you may have to try:
sudo "/Applications/Text/BBEdit 7.0/BBEdit.app/Contents/MacOS/BBEdit"
(alter as appropriate for your configuration)

That was it - thx!

I know little of Unix privileges, but the same that one can change a file owner, group and rest 's priviledges over one file, couldn't I set that WindowServer accessible to everybody?

You do not want to do that. Apple's system demarcation is in place for very specific reasons.

er... could you be more explicit as to what the undesired consequences could be? Saying just do not do this because it is bad is not very constructive...

afaik, there is no way of changing the permissions for the windowserver. File permissions are handled by the operating system; basic process permissions are handled by the operating system too, but they are very basic. They ingore groups, and only the root user can affect another user's process (which is why you can launch an app as root under your windowserver). Anything more has to be built in by the programmer, and will vary depending on the program.

As for "bad things" that might happen if you changed the permissions, I can't really see any. Since a bad person? can't connect to the window server via the internet, there shouldn't be any problems. (for the average user, anyway)

If there IS a way of setting permissions for connections, I would sure like to know about it. :)

Thank you for the answer. That made a little more sense :) However, isn't the window server just an application the file of which can be traced and change its permissions?

Well, yes or no, depending on what you want to do with the permissions.

The only permissions you can set on the executable file (the binary) control who can execute the file, and read and write to the actual file.

The permissions you want to be able to change are for being able to connect to the window server. The server is already executed and running, and at that point, the permissions on the binary executable don't apply. It handles it's own authorizations: any apps you launch ask the server for permission to connect, and if the server decides it doesn't like the username, it denys it.

It may help to remember that the window server is basically just like any server, such as an ssh or ftp server. Just in this case, the logon part is much simpler. :)