Originally Posted by zdenekkrejci
...still one thing unclear. You say, that when i go to the terminal, Im the same user as I am in the GUI right?
So why, I can some files for example the OO file run by clicking in the GUI and not in the terminal???
Because the GUI, if we are talking about the desktop environment in general, and such things as icons and files that are on the desktop, is where one normally uses the mouse, and clicks things, to make things happen. This is the entire purpose, the raison d'etre
, of the GUI.
The TERMINAL, is an application in itself, which runs inside the GUI environment (or, if you have switched to a Virtual Terminal, then you are not in the GUI, but it is still a terminal). In all terminals I am aware of, clicking things with a mouse, is not a supported activity. The terminal is (for all intents and purposes in this discussion) is a text-based terminal program. Things are done using commands, not a mouse (except for copy + paste text with mouse, if you like).
There are exceptions: nCurses for example (libraries for creating text & line graphics in a terminal) can react to mouse clicks; so, if you had an nCurses-application which showed a list of OO docs, and was coded such that when you click one, it opens OO, then great. But that is a specific
application running in the terminal, NOT the terminal itself.
In short: text you see in the terminal, be it filenames or whatever, is basically not clickable.
Some terminals (or terminal apps, like maybe man, when configured certain ways, will present clickable links to web URL's when they appear in some text in the terminal, but exactly which terminals (and in what desktop environments), and how this works, I am unsure.
btw. I know now already that I can change the permissions to be able to run it in terminal but why should I do that when I'm the same user? So I should have the same permissions...
You are confusing OWNERSHIP and PERMISSIONS. Permissions include, among others, READ, WRITE, and EXECUTE, on a per-user/group basis.
Just because you OWN a file (assuming we are talking scripts here again?) does not make it executable by the shell, by you or by anyone else. Imagine if we did not have such a thing as an "Executable" bit -- every possible filetype known to man, would have to be either executable, or not. It should be fairly clear that this would not be desirable. The executable bit can be used to control EXACTLY WHO can execute the file or program, in addition to simply whether or not it is executable.
Does this help? I seem to be getting convoluted, the more I write, so before I confuse both of us, I'll stop here and see how this does for you.
EDIT: But, further on the subject of understanding just what the terminal actually *is* - imagine back 40 or 50 years ago or whatever it was, before the GUI came along. Everything was text, on a "terminal" which was a machine with a screen and keyboard, but no brains inside. And there were probably no mice. Well, the modern-day terminal is an "emulator", which emulates the features and abilities of those olden-days terminals, albeit we have a few more features with our fancy, modern terminal emulators! But the main purpose, is to run commands, which are typed in, or saved in a script.