Sorry, but I kinda liked being able to use Cmd-P for my own purposes :-) Is there a way to disable that shortcut (using the current beta)?
Regards,
Martin
On 2. Nov 2004, at 18:07, M Spreij wrote:
Sorry, but I kinda liked being able to use Cmd-P for my own purposes :-) Is there a way to disable that shortcut (using the current beta)?
You can change any application's menu item key equivalent through System Preferences → Keyboard & Mouse → Keyboard Shortcuts.
You'll probably need to choose another key (instead of just removing it).
Kind regards Allan
Allan Odgaard wrote:
M Spreij wrote:
Sorry, but I kinda liked being able to use Cmd-P for my own purposes :-) Is there a way to disable that shortcut (using the current beta)?
You can change any application's menu item key equivalent through System Preferences → Keyboard & Mouse → Keyboard Shortcuts.
You'll probably need to choose another key (instead of just removing it).
*hits self* hadn't realized that last possibility..
Other question: With the CLI commands I get an errormessage "/bin/bash: line 1: .bashrc: no such file or directory" as first line of the ouput. That file is referenced in the first line of .bash_profile (or more precisely the first line is ". .bashrc" which seems to be some UNIX syntax I don't know about), as I want it to be used every time I open a terminal. The .bashrc file does sit in the same dir as .bash_profile: /Users/mspreij/.bashrc
Me clueless?
Regards, Martin
On 2. Nov 2004, at 18:59, M Spreij wrote:
.bash_profile (or more precisely the first line is ". .bashrc" which seems to be some UNIX syntax I don't know about), as I want it to be used every time I open a terminal. The .bashrc file does sit in the same dir as .bash_profile: /Users/mspreij/.bashrc
Change it to: . ~/.bashrc
Actually, it really should be: [ -f ~/.bashrc ] && . ~/.bashrc
The “. <file>” means “read instructions from file”. The current directory is not always your home directory when executing commands from TextMate (I think I document this somewhere), so you should provide a full path -- the “[ -f <file>]” means “true if file exists” and && has the short-circuit behavior you probably know from some programming language, i.e. if the first expression tests false (the file doesn't exist), the right-hand side won't be executed.
So all in all it really mens: if(exists("/Users/me/.bashrc")) execute("/Users/me/.bashrc")
Kind regards Allan
-
Allan Odgaard -
M Spreij