Leopard Terminal.app problem

I have two issues.
In Tiger Terminal, it is possible to select text and drag and drop on the current command line. Is this possible in Leopard Terminal.
Also, I am in the habit of drag and dropping filenames from Finder into Terminal windows. When I do this in Terminal, it looses track of the cursor location. e.g. I create a new folder "untitled folder" and drag it to Terminal, do Ctrl-A to go the the start of the line and type cd, Terminal displays
/Usecd rs/pheon/Desktop/untitled\ folder
I hit return and I cd to untitled\ folder. No real problem apart from being ugly and difficult.
Any solutions?
Alan

You might want to ask in the Unix forum too:
http://discussions.apple.com/forum.jspa?forumID=735

Similar Messages

Leopard Terminal.app no longer supports ANSI print escape sequences?!!

I print my email using pine's "attached-to-ansi" option, which used to work great in Tiger with Terminal.app. It no longer works in Leopard. It also breaks things like the "ansiprt" Unix command.
This is a start/stop escape sequence that diverts text between the start/stop sequences to the printer. See http://www.termsys.demon.co.uk/vtansi.htm as a reference.
Is there some Terminal.app setting I need to use to enable this? Some specific terminal type perhaps?
Suggesting that I use enscript or other techniques don't work, as I use the Terminal to ssh into my mail server, then run pine on the mail server.
Anyway, any idea how to get this very desirable feature back?
Thanks,
-John

HI,
I tried to set "Escape non-ASCII input" without any change. I didn't see an option to change "Escape non-ASCII output". I tried a few other things without success either using a different terminal type and so forth. I looked in the .term file and didn't see anything text related to ANSI or ASCII or escape.
If I change a Terminal preference do I need to quit and restart Terminal to test the change, or does the change take place as soon as I change it in the menu? I tried quitting and restarting after checking "Escape non-ASCII input" and when I restart the box was unchecked. I couldn't find a "save preferences option either.
In Tiger, my terminal type was xterm-color- same in Leopard. I had checked off "Escape non-ASCII characters" under Tiger.
Here's exactly what I do, *which used to work in Leopard*.
I run Terminal.app on my MacBook, and ssh to a mail server. On the mail server, I run the pine command to read my mail. Pine has an option to print email using ASCII escape sequences. Terminal.app sees these escape sequences and diverts the text to the default printer on my MacBook.
Under Leopard, the Terminal doesn't catch the ANSI escape code, and just spews the text to the terminal window. Nothing has changed on the mail server side. I;m using the sane ssh command.
Enscript won't work, as the printer connected to the mail server is often as not in a different state than my MacBook.
Not all terminal emulators support the ANSI print escape sequences. Terminal didn't before Tiger, if I remember correctly. I used to use a very nice terminal emulator called Data Comet which did it.
ANSI printing used to be a fairly common way to print to a local printer connected to via a parallel cable. Besides pine, the Unix command ansiprt http://kb.iu.edu/data/abye.html could be used to print remote files on the local printer. Some terminal emulator programs used the idea to hook the ANSI escape sequence to the printing system, extending the functionality to use any printer accessible by the local system.
Thanks again for all your help. I hope I've clarified what I'm trying to do.
-John

Snow Leopard mail.app problem

I just upgraded 2 iMacs at home with Snow leopard and am having a problem with mail.app. I have 13 e-mail accounts on my box, and my wife has 6 e-mail accounts on her Mac. We have never had problems with e-mail before and Leopard and Tiger would go through the POP accounts in order, 4 at a time, until all the mail was downloaded in all the accounts.
What is happening now is that the mail.app is trying to get ALL the mail at once and trying to access all 13 POP accounts on my Mac, and all 6 on my wife's. It will only grab the first 4 POP accounts and show errors for the rest (and take them offline). I get the "*Unable To Receive Mail - There may be a problem with the mail server or network...*" error for the remaining accounts. The only way I can get the rest of the mail is to go through each account, control-left click, and select "Get New Mail from "[email protected]". Needless to say, this is a real pain in the butt as I do get a lot of mail and prefer it to come in properly in the background.
This is happening on both iMacs so it can't be an isolated thing. Anyone know of a fix for this??

I'm having the exact same issue. I've spent hours rebuilding mailboxes, passwords, and keys. I can often go days before the mail will actually be seen in these offline boxes. Apple - we need this fixed!

Problem with font in terminal.app

Hello all
I tried to use the font Inconsolata (downloadable from http://www.levien.com/type/myfonts/inconsolata.html) with the terminal.app. Prior to the update to snow leopard everything was alright. But now this font doesn't render anymore in the terminal.app (although it worked once till the next restart also under snow leopard!). Strange thing is, the font works absolutely normal in all other apps (e.g. macvim oder texteditor). So the font seems to be ok. But why does the font not work any more in the terminal.app? Is there a special font-cache for the terminal? I already tried to delete the user and the system font cache.
A picture might help to understand the problem:
http://dl.dropbox.com/u/11881979/Bildschirmfoto%202010-09-27%20um%2021.54.47.png
Some hints on how to remedy this problem?
Greetings
Jerri

That is very strange. OpenType was the format that had the least issues as Apple worked out the early bugs in the complete 64 bit rewrite of the font engine in Snow Leopard. Type 1 PostScript was where the majority of the trouble was.
As I noted above, I had no trouble with the font, so can only assume there's some sort of issue with your system. At least the TrueType version works.
The only thing not done was reinstalling the OS. If you want to take the time to try that, back up the drive and run the OS X installer from the desktop. That will put a fresh copy of OS X on the drive while keeping all of your third party apps, preferences and such intact. Then apply all available updates.

Problem with Terminal.app after upgrade

Hi,
I just installed Tiger over Panther. Everything went and seems just fine, except:
When I try to run Terminal, I see:
You are not authorized to run this application.
The administrator has set your shell to an illegal value.
I am not sure I understand from the message what is the problem:
a) Not authorized should mean Unix user permissions, right?
(In Finder's info window, I see :
- you can read/write
- Owner: system
- Group: admin
- Access: r/w
Seems bad as I am supposed to rwx, but that I guess is just Finder-specific simplification:-).
From the other hand,
b) an "illegal value" (whatever it is - say /bin/mabooka) should be possible to just change - ?
How?
The Terminal is not giving me any options except "Quit".
The box is single-user, the admin is myself...
Please help if you saw something similar... Thanks!

Thanks Ali,
It was hard to find the solution in search list, but it was there.
The correct answer is:
================
Re: Terminal: Not authorized to run app... shell has an illegal value?!!
Posted: Jun 3, 2006 6:57 PM in response to: Eric Bigham
Helpful
Click on Terminal.app to select it, CMD+I, and check the ownership and permissions. It should show that you have R&W. If so, then drag ~/Library/Preferences/com.apple.Terminal.plist file to the desktop, log out and back in, and try launching it again.
================
Also it was entertaining to read and then use Netinfo Manager:
Using this utility, I've found that my shell was set to "bin/tc" (instead of /bin/tcsh, as I set it years ago on Panther).
Apparently:
1) there is a bug in installation (who else could change "tsch" to "tc"?!?);
2) there is a bug in the message ("You are not authorized..."): -- nothing to do with authorization.
In any case, the problem's been solved, many thanks.

ANSI Colors in Leopard's Terminal.app

Has anyone figured out a way to customize the ANSI colors in the Leopard Terminal? The TCColorArray plist setting seems to be ignored.
I've even gone so far as to copy the Terminal.app from Tiger onto Leopard. Still no go, even Tiger's terminal is ignoring TCColorArray when running on Leopard (which I find very strange).
Could this be a termcap issue?

The following will rid your Terminal of blue directory listings:
1. Add the following to ~/.profile :
alias ls='/bin/ls -G'
export LSCOLORS=exfxcxdxbxegedabagacad
2. Change the color(s) displayed by `ls` considering the following:
For each pair of characters in the string 'exfxcxdxbxegedabagacad', the first character in the pair represents the foreground color, the second character in the pair represents the background color. Changing the character changes the color; see the following chart:
a black
b red
c green
d brown
e blue
f magenta
g cyan
h light grey
A bold black, usually shows up as dark grey
B bold red
C bold green
D bold brown, usually shows up as yellow
E bold blue
F bold magenta
G bold cyan
H bold light grey; looks like bright white
x default foreground or background
Each character pair in the string 'exfxcxdxbxegedabagacad' represents a type of file displayed by `ls`. The breakdown of character pairs follows:
Pair 1 (ex) - directories
Pair 2 (fx) - symbolic links
Pair 3 (cx) - sockets
Pair 4 (dx) - pipes
Pair 5 (bx) - executable files
Pair 6 (eg) - block special
Pair 7 (ed) - character special
Pair 8 (ab) - executable with setuid bit set
Pair 9 (ag) - executable with setgid bit set
Pair 10 (ac) - directory writable to others, with sticky bit
Pair 11 (ad) - directory writable to others, without sticky bit
So, following this through to conclusion, the following is the list of default color pairs:
ex - blue/default - directories
fx - magenta/default - symbolic links
cx - green/default - sockets
dx - brown/default - pipes
bx - red/default - executable files
eg - blue/cyan - block special
ed - blue/brown - character special
ab - black/red - executable with setuid bit set
ag - black/cyan - executable with setgid bit set
ac - black/green - directory writable to others, with sticky bit
ad - black/brown - directory writable to others, without sticky bit
Finally, to change the listing of directories from blue to cyan, change the first character pair (ex) to (gx) in .profile :
export LSCOLORS=gxfxcxdxbxegedabagacad
3. To have the color change take effect, quit and restart Terminal, or run the following command:
. ~/.profile
Message was edited by: Apple Scruffs

I plugged in a USB drive, tried to open Finder, got the message Finder.app can't be opened - 10810, went into terminal.app, messed up, now terminal screen blank. how do i regain terminal in order to fix finder problem?

With my iMac running, I plugged in a USB drive. When I clicked on finder, I got the message Finder.app can't be opened - 10810. I removed the USB drive. I messed up while in Terminal.app trying to fix Finder problem. Now my terminal screen is blank, just the cursor, but no action after typing a command & clicking enter. Help!

I finally figured out a way to Restart (normal way wasn't working...) & that Restart DID FIX both the Terminal problem AND the Finder problem. So easy, yet so elusive. Thanks so much.

Problem with Terminal.app - unable to input '^' (Shift + 6)

Hello everyone,
I'm experiencing a strange problem with Terminal since this morning: I'm not able to input symbol '^' (Shift + 6) in any terminal application. Both Terminal.app and iTerm.app show the same problem. I'm able to input '^' in all other applications, as you can see, without any problem. Is it something related to key bindings? Anybody with similar problems?
Thanks,
Luca

What terminal emulation are you using? Which shell? I suggest you look into whatever terminal emulation you are using. Try googling for the type of terminal emulation you are using to see if that sheds any light on this issue.

Emacs problem in Terminal.app

When I edit a text file in the (text-only version) of emacs running in Terminal.app, what happens all the time is that characters in my file get overwritten by spaces (on the terminal only). Pressing Ctrl-L recentres and refreshes the display and it's OK - until it happens again, which is usually right away.
E.g. if I open the file and press down rightarrow, and hold it for autorepeat, the cursor will gradually move through the file, but as I scroll over certain characters, they will be overwritten by spaces on the screen.
The problem only happens in Terminal.app, not also in xterm.
It doesn't matter whether $(TERM) is set to xterm, xterm-color, vt100 etc. in Terminal.app.
I remember this working in previous versions of Mac OS X, but not in 10.4.5 (and as I recall it's not worked for me for a while).
Is this a bug? Does anybody else see this? Or is there some setting I might have inadvertently changed.

The problem was traced to a
stty -tabs
line in my .login file. It appears that emacs outputs tabs to move around the screen, and those were being expanded to spaces which overwrote my text. Vi apparently does not use tabs in the same way, which is why the problem was limited to emacs.
The reason the problem manifested itself in Terminal.app but not in xterm is that tcsh executed inside a new Terminal.app window executes .login, whereas one executed inside a new xterm window does not.

Terminal.app won't display OpenType fonts (.otf)

Where the characters should be, blanks are displayed. This is a serious problem for me because, while I use Monaco in my terminal, the fallback font for Japanese characters is Hiragino, which is an OpenType font: as a result, Japanese text is not visible in my terminal.
Here is a screenshot: http://i.imgur.com/wlNPV.png
Note that, since I set the system's language to Japanese, most of the text in Terminal's preferences is also invisible.
The problem only seems to occur in Terminal.app, and does not affect other users on the same machine (I tried logging in as guest). It occurs with all OpenType fonts I tried, not just Japanese ones.
Strangely, if I delete Terminal's preferences, the problem almost disappears (except that it still says ル in the window's title bar instead of ターミナル); however, if I close and relaunch Terminal, the problem immediately reoccurs, even though the preferences file is pristine.
I tried resetting the ATS cache (atsutil databases -remove) and restarting in safe mode, but the problem still occurs. I've tried googling around, and I found some other people mentioning the same problem, but no solution. Can you help?

I've got the same problem with my new MBP 2011 with Snow Leopard and it really annoys me as I'm dealing with multilingual texts every day.
What surprises me is that I had no problems at all since MacOs 10.1 and now it appears in 10.6 !
Back in the old days I had to put a .inputrc file for displaying Japanese characters but that was not a big deal.
When I create a new account, it works for a few hours (Japanese characters display well even with menlo or courier fonts set as default). But after a few manipulations here and there (that do not seem related to terminal or fonts like setting my iTunes account) and a couple of reboots, the problem reappears again, ie the Japanese characters do not display again.
I can temporarily solve the problem by using the Osaka font but 1 it is not nicely displayed with irregular spaces between characters and 2 when I want to display other characters (thai, khmer or whatever), I have to change the default font again. This is a real pain in the neck.
I read in another thread that there is a solution to convert the OpenType Font you wish to use into a TrueType font but it is not a solution for me neither as there is no existing font that covers all the unicode characters.
Is Apple aware of this bug? Did they acknowledge that there is a problem?
If someone finds a solution, I'll be really happy.

Leopard Terminal Features Gone

I used to be able to save my connection and window settings all together in Terminal in Tiger. I could simply double-click a saved terminal, and it would open the terminal app, make my SSH connection and display the background and other colors (which help remind me which remote machine I am on) that I had saved with that connection. Where have all these features gone? Can anyone tell me how to save a remote connection in the new Terminal?

Your Mail is not gone. The problem you are having following the upgrade to Leopard (10.5.6) from Tiger (10.4.11), is probably what has been covered by the support document at the link below:
http://support.apple.com/kb/TS2537
If you also find any files named to include MessageSorting (which would mean you once have upgraded from a version of OSX earlier than 10.4), remove those, also, but never restore those.
To find the correct location for the Mail folder, open a Finder window, click on the icon of a house in the Sidebar (this is known often as "Home"), click on Library in that Home user directory, and then to open the Mail folder found there.
Ernie

Keyboard trouble in Terminal.app

Hello there.
After using UNIX-like operating systems for many years I finally got a Mac. I use Terminal.app a lot for administrating remote servers over SSH.
Now I have two problems:
1. For going to the beginning/end of the line I always have to press "Apple+Home" or "Apple+End". Is there a way to do this just with "Home"/"End"? I figured xterm does it that way an OSX too, but is pretty limited and does not support tabs.
2. When using an application like vim (locally or on a remote server, does not matter) I cannot use "Apple+Home" or "Apple+End" at all to go to the beginning of the line in the editor window, which is far more annoying and frustrating than the first problem.
It would be nice if anyone could help me there.
For now I solved these issues by installing Linux/KDE for administrating/programming on my iMac but it would be nice if I could also get this job done on Leopard.
Thanks,
direx

First, I would point out that there are other terminal emulators available for Mac OS X. I personally use iTerm <http://iterm.sf.net>.
1. For going to the beginning/end of the line I always have to press "Apple+Home" or "Apple+End". Is there a way to do this just with "Home"/"End"? I figured xterm does it that way an OSX too, but is pretty limited and does not support tabs.
I guess it all depends on which line you are trying to get to the beginning or end of. For me, it is the bash shell, and for that I just use the supported command line editing commands (which I set to vi mode). The other is the vi/Vim editor and I just use the main keyboard commands for moving to beginning or end of a line.
But my preference is not yours. I do not have a solution for your desires. Maybe a hotkey mapping utility that translates Home/End into some Terminal key sequences, bypassing the Terminal's grabbing of those keys for scroll back/forward.
2. When using an application like vim (locally or on a remote server, does not matter) I cannot use "Apple+Home" or "Apple+End" at all to go to the beginning of the line in the editor window, which is far more annoying and frustrating than the first problem.
Unless Apple+Home or Apple+End send a standard ANSI escape sequence, Vim can not see the key combo.
If you want to use gvim you might be able to see meta keys that do not have normal ANSI escape sequences.
If you want to test that a key combo is sending an escape sequence, then run the following command and type away to see what escape sequences are sent
cat -vte
If you do not see anything, then the key combo is not sending anything that Vim can see.
This trick does not apply to gvim.
NOTE: xterm is an X11 based terminal emulator (on any Unix you care to name). That means it can decide to do additional things with meta keys. Also some xterm implementations even pass mouse position information. Terminal.app more closely resembles a terminal (I'm playing fast and loose with my analogy).
Message was edited by: BobHarris

Terminal.app takes up CPU 100% and can't seem to launch

I have OSX10.5.1 installed on my iMac.
I've been using it without any significant problem since upgrade to Leopard.
But all of sudden, the BIG problem.
When I tried to run Terminal.app, the terminal window does not poped up for a long time.
I checked iStat on my dashboard, and the Terminal.app was taking up 100% of CPU.
I could not believe my eyes.
So, I double-checked using top, which I was able to start by using xterm.
It was true. Terminal.app was possessing CPU about 100%.
I did not do anything but my routine stuff.
Anyone has a clue about what is going on my Leopard?
Any small hint will be appreciated.
Thanks.

I have just rebooted the system and now I can launch Terminal.app.
It is anyway resolved.
Shame on Leopard.
Rebooting is just as Windows-ish solution to a problem.

No japanese fonts in Terminal.app

Hi,
I installed fresh Snow Leopard and I like it.
But I got something strange problem on Terminal.app. Japanese fonts are not displayed!
I tried completely new OS installation for 3 times and nothing changed...
Can anybody help me? Thank you.
http://img38.imageshack.us/gal.php?g=37982559.png

Try trashing any .plist with terminal in its name found in Home/Library/Preferences.
Try creating a new user account and see if you have the same problem when logged into it.
You could try running the Japanese language translation installer again. It can be found in the OptionalInstalls.mpkg on the Snow Leopard DVD.

Terminal.app VERY SLOW to bring prompt after it launches

Hi,
Has anyone else noticed that, after launching Terminal.app, it takes a very long time to get to a shell prompt? The window opens, blank, and just sits there for like 10-15 seconds until the shell prompt comes up.
What gives? It was definitely not this slow in early Leopard levels or any previous x86 build of OS X..

Well, to be fair, I am a solipsist.. Therefore my problems are everyone's problems..
Anyways, that appears to have done the trick, but it has gotten rid of all my prefs.. I would like to see what pref or update change frobozz'd my preferences plist, since I haven't changed terminal prefs since at least 10.4 (probably earlier, since this Macbook inherited from a Powerbook that had 10.2 initially).. Wouldn't surprise me if it were a font issue... Shall have to inspect the file..

Leopard Terminal.app problem

Similar Messages

Maybe you are looking for