I followed the instructions here:
How to run TKDiff from the terminal on mac os
to get tkdiff working from terminal in mac os. The problem is when I run "tkdiff file1 file2 " on the terminal it does not open up a window. Instead, app Wish appears "hidden" in the application dock and I have to click on it in order to display the diff window. After clicking on it everything is fine. But I'd rather the diff window to pop open as soon as I run tkdiff. Anyone know if there is a setting I need to change, or if I'm doing anything wrong?
Related
The issue I am having is when I open a file via emacs it will open another window in the emacs text editor, but lock out the terminal. What I mean by lock out is that the terminal seems to be linked to the window of emacs that had opened up. When I first downloaded the software I did not have this issue and was able to open multiple emacs windows at once but now I have to close out of the current emacs window to open another. Any suggestions on fixing this?
It sounds like you want to have the file pop up in a window when you open it, rather than fill the whole terminal.
If that's the case, you should
install a graphical version of Emacs from http://emacsformacosx.com/
put alias emacs=/Applications/Emacs.app/Contents/MacOS/Emacs in you ~/.bashrc
open files with emacs file.txt &. The file will open in a separate window and you can keep using your terminal
Is there a way to tell a Mac .app bundle to open the command line for the purpose of printing to stdout? I think it does not really matter, but it is a C++ Qt app.
No, there's no way to do that.
An app can launch Terminal.app or similar and make it open a window, but that window won't display the output of the app. The stdout of an app isn't connected to any "command line" or Terminal window or anything. Basically, it's a file descriptor opened to /dev/null. You could re-open it to some other destination, but none will be a command line or Terminal window unless you build it to be so.
I built a Lazarus GUI application using Ubuntu and then took it onto Windows to compile. On Ubuntu I run it from the terminal like this:
./prg arg
It runs fine using the argument arg passed to it. On Windows this is what I did:
Create shortcut to exe
Edit shortcut and include the argument.
To run on Windows, I run the shortcut.
It works fine but there's an additional terminal window opening behind the application, when I run the shortcut. When the application exits, the window closes with it. The terminal window is empty.
On Windows, before compiling I had to uncheck the -WG switch in compiler options. This was because althought the app is GUI-based, there is a simple routine that checks for the argument passed at command line and uses Writeln to output a message if there were errors.
My key question is why is this terminal window coming up on Windows and how do I get rid of it or suppress it?
Thanks!
(1) Make sure you have set {$APPTYPE GUI} in your code. Otherwise there will be always a "terminal" opened on windows.
(2) Maybe you are confusing a "real" shortcut (*.lnk) with cmd/batch file? The latter also opens a terminal that dies when the lauched app closes.
When I open Terminal on Mac, it starts in the root directory. I don't want to have to type cd to change my directory every time I open terminal, I want to be in that directory to begin with.
How do I make terminal start in a specific directory? Also, how do I make terminal always start full screen and in a particular color?
Also, what is the command to open text mate in terminal?
This perhaps better belongs on Ask Different, but here are two options to start a Terminal session at a particular location:
Open Terminal Preferences to the Settings section, and in the Window tab check the "Run command", and enter cd yourdirectorypath in the command field. It will automatically run for any new Terminal window.
Edit the ~/.bash_profile and add the cd yourdirectorypath line at the end.
As for starting fullscreen, if you quit Terminal with a fullscreen window open, it will launch that way.
You can set colour schemes in the preferences, there are many built-in "profiles".
Recently, Vim started behaving strangely.
Whenever I open a file with Vim in the terminal, I see the line that is normally at the bottom of vim:
"<filename>" [dos] ###L, ###C
But instead of the buffer being displayed above, the screen is blank.
When I press Enter, however, the buffer displays normally.
What did I change to make Vim behave this way when I open files, and how can I change it back?
Here's my .vimrc.
I'm on a Mac, running OS X 10.8, using Vim 7.3.