You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(2) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(9) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
(2) |
Feb
(3) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(14) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: aaron s. <bei...@gm...> - 2009-09-16 01:25:05
|
Hey All, Quick question. I'm working on some tests with embedding a console in a cocoa app. I haven't come across any real good documentation that shows how to do it, other than some hints that using iTerm is probably the way to go. I've been looking through the source code for iTerm and am curious if anyone would have some pointers on which classes I should use and test with to try to get this working. Ultimately what I'm be trying to do is embed a console in an NSView, that I can use somewhere in this app i'm building. Some help or tips in the right direction would be much appreciated. Thanks much! |
From: Chris S. <chr...@sh...> - 2009-01-07 18:39:49
|
I use Emacs and RST mode and it uses the C-= (Control Equals) key quite a bit. On my Mac laptop, this works fine in native Emacs. But if I use iTerm, C-= is sent as a plain = (Equals) key. Am I missing something or is there a keyboard profile I should be using instead? Thanks. |
From: David N. <dn...@ne...> - 2008-09-25 23:22:03
|
iTerm 0.9.6, OS X 10.5.5 MBP When I first open iTerm and create multiple tabs with command-t it is possible to move between them with command-1, command-2 and so on. However once I assign names to each tab (using command-i) iTerm no longer has this capability. That's true even after changing tab names back to the original "Default" label. Is there some way to preserve command-# behavior? I find it a lot faster than command-arrow keys, as it doesn't require removing hands from keyboard. thanks dn |
From: Marc <ma...@da...> - 2008-09-25 19:33:21
|
Am 25.09.2008 um 21:27 schrieb Marc: > Hi folks, > back in April I've sent an e-mail that talked about a patch but dumb > as I am I forgot to add the patch. Here it is. > > This patch adds a new cursor type that improves the visibility of > the cursor. > > Currently you have to specify the cursor color. This just doesn't > work when you have changing dark and bright backgrounds. The > solution is to do it like other terminal applications, e.g. KDE's > Konsole. The cursor background is the characters foreground color > and vice versa. Together with blinking this ensures that the cursor > is always visible. > > The attached patch does not contain the necessary GUI changes for > the preferences panel. I just couldn't find a good way (one that I > thought would be good enough for other users) to do that UI-wise and > my XCode experience is still very low. So whoever wants to > incorporate the patch needs to add the corresponding GUI stuff or > use "defaults" to set it: > > defaults write net.sourceforge.iTerm CursorType 3 > > Bye, > Marc Same as my other patch... braindead mailing list software, it seems. Here is the patch inline... if that still doesn't work I'll post it on my homepage and send the link. Index: PTYTextView.m =================================================================== RCS file: /cvsroot/iterm/iTerm/PTYTextView.m,v retrieving revision 1.307 diff -u -r1.307 PTYTextView.m --- PTYTextView.m 17 Jun 2007 01:56:31 -0000 1.307 +++ PTYTextView.m 11 Apr 2008 20:25:06 -0000 @@ -761,6 +761,7 @@ int bgstart; BOOL hasBGImage = [(PTYScrollView *)[self enclosingScrollView] backgroundImage] != nil; BOOL fillBG = NO; + unichar aChar; float trans = useTransparency ? 1.0 - transparency : 1.0; @@ -1019,12 +1020,12 @@ else { NSFrameRect(NSMakeRect(floor(x1 * charWidth + MARGIN), - (y1+[dataSource numberOfLines]-[dataSource height])*lineHeight + (lineHeight - cursorHeight), - ceil(cursorWidth), cursorHeight)); + (y1+[dataSource numberOfLines]-[dataSource height])*lineHeight + (lineHeight - cursorHeight), + ceil(cursorWidth), cursorHeight)); } // draw any character on cursor if we need to - unichar aChar = theLine[x1].ch; + aChar = theLine[x1].ch; if (aChar) { if (aChar == 0xffff && x1>0) @@ -1041,7 +1042,47 @@ Y: (y1+[dataSource numberOfLines]-[dataSource height] +1)*lineHeight doubleWidth: double_width]; } - + + break; + case CURSOR_BOXINVERS: + if([[self window] isKeyWindow]) + { + // Active window. Draw the cursor in the character foreground color. + [[self colorForCode:(theLine[x1].fg_color & 0x3ff)] set]; + NSRectFill(NSMakeRect(floor(x1 * charWidth + MARGIN), + (y1+[dataSource numberOfLines]-[dataSource height])*lineHeight + (lineHeight - cursorHeight), + ceil(cursorWidth), cursorHeight)); + } + else + { + // If the window is inactive then just draw a border around the character + // and leave. The border is of the same color as the character. + [[self colorForCode:(theLine[x1].fg_color & 0x3ff)] set]; + NSFrameRect(NSMakeRect(floor(x1 * charWidth + MARGIN), + (y1+[dataSource numberOfLines]-[dataSource height])*lineHeight + (lineHeight - cursorHeight), + ceil(cursorWidth), cursorHeight)); + break; + } + + // Draw any character on cursor if we need to. Draw it in the background color. + aChar = theLine[x1].ch; + if (aChar) + { + if (aChar == 0xffff && x1>0) + { + i--; + x1--; + aChar = theLine[x1].ch; + } + double_width = (x1 < WIDTH-1) && (theLine[x1+1].ch == 0xffff); + [self _drawCharacter: aChar + fgColor: theLine[x1].bg_color + bgColor: -1 + AtX: x1 * charWidth + MARGIN + Y: (y1+[dataSource numberOfLines]-[dataSource height] +1)*lineHeight + doubleWidth: double_width]; + } + break; case CURSOR_VERTICAL: NSRectFill(NSMakeRect(floor(x1 * charWidth + MARGIN), Index: Headers/iTerm/PreferencePanel.h =================================================================== RCS file: /cvsroot/iterm/iTerm/Headers/iTerm/PreferencePanel.h,v retrieving revision 1.56 diff -u -r1.56 PreferencePanel.h --- Headers/iTerm/PreferencePanel.h 15 Feb 2007 03:23:11 -0000 1.56 +++ Headers/iTerm/PreferencePanel.h 11 Apr 2008 20:25:26 -0000 @@ -33,7 +33,7 @@ @class iTermController; @class TreeNode; -typedef enum { CURSOR_UNDERLINE, CURSOR_VERTICAL, CURSOR_BOX } ITermCursorType; +typedef enum { CURSOR_UNDERLINE, CURSOR_VERTICAL, CURSOR_BOX, CURSOR_BOXINVERS } ITermCursorType; @interface PreferencePanel : NSWindowController { -- Marc Haisenko ma...@da... |
From: Marc <ma...@da...> - 2008-09-25 19:31:12
|
Am 25.09.2008 um 20:46 schrieb Marc: > Hi folks, > after updating to Mac OS X 10.5.2 I experienced a huge problem with > iTerm on my MacBook Pro (but not my iMac at work): after starting up > iTerm hung up. The UI rendered, but upon trying to render the > session nothing happened. > > I then got the latest CVS version, but with the same problem. But in > XCode I saw an error message regarding a deadlock in NSLock: > > Thu Sep 25 20:34:52 neotokyo.local iTerm[14091] <Warning>: > CGSResolveShmemReference : reference offset (65296) exceeds bounds > (32768) on shmem obj 0x2f69 > 2008-09-25 20:34:52.793 iTerm[14091:10b] Error (1000) creating > CGSWindow > 2008-09-25 20:34:52.806 iTerm[14091:10b] *** -[NSLock lock]: > deadlock (<NSLock: 0xfcccc0> '(null)') > 2008-09-25 20:34:52.806 iTerm[14091:10b] *** Break on _NSLockError() > to debug. > > But it turned out that the deadlock was only the symptom, not the > cause. After some googling, it seems that the "Error (1000) ..." > stuff is a bug in Mac OS X 10.5.x. It's running inside code that is > started with a [VT100Screen tryLock]. Because of the exception, the > corresponding [VT100Screen releaseLock] is never called. Then the > same thread later tries to run [VT100Screen acquireLock] and there > you have your deadlock. > > I traced the exception to PTYTextView::_renderChar (how do you write > that in Objective-C syntax ?), more precisely to [image lockFocus]. > > The attached patch works around the bug by packing the [image > lockFocus] into a @try @catch block. It retries the lockFocus up to > five times. If that still does not work then the exception is > rethrown. That fixes the hang problem for me. > > Bye, > Marc > > > -- > Marc Haisenko > ma...@da... Damn it, why do my patches get stripped ? So, here it is inline... Index: PTYTextView.m =================================================================== RCS file: /cvsroot/iterm/iTerm/PTYTextView.m,v retrieving revision 1.320 diff -u -r1.320 PTYTextView.m --- PTYTextView.m 23 Sep 2008 23:26:36 -0000 1.320 +++ PTYTextView.m 25 Sep 2008 18:21:07 -0000 @@ -44,6 +44,8 @@ #import "ITConfigPanelController.h" #import <iTerm/Tree.h> +#import <Foundation/NSException.h> + #include <sys/time.h> #include <math.h> @@ -2601,6 +2672,7 @@ BOOL renderBold; BOOL tigerOrLater = (NSAppKitVersionNumber > NSAppKitVersionNumber10_3); NSFontManager *fontManager = [NSFontManager sharedFontManager]; + int retryAttempts = 5; //NSLog(@"%s: drawing char %c", __PRETTY_FUNCTION__, carac); //NSLog(@"%@",NSStrokeWidthAttributeName); @@ -2646,9 +2718,47 @@ nil]; } + + crap = [NSString stringWithCharacters:&carac length:1]; + +retry: + @try + { + [image lockFocus]; + } + @catch (NSException *e) + { + /* Work around a bug in Leopard. Sometimes the call to + * lockFocus fails with the following error messages: + * iTerm[13285] <Warning>: CGSResolveShmemReference : reference offset (65296) exceeds bounds (32768) on shmem obj 0x2f69 + * Error (1000) creating CGSWindow + * + * The net result is that iTerm locks up (deadlock in NSLock + * because due to code flow caused by the uncaught exception + * VT100Screen is locked twice by the same thread). + * Just retry locking, up to five times. If it still doesn't + * work log and rethrow. + */ + if ([e name] == NSInternalInconsistencyException) + { + if (--retryAttempts == 0) + { + NSLog(@"%s: Error while lock focus on image !"); + @throw; + } + else + { + // Unfortunately there's no @retry... + goto retry; + } + } + else + { + // Not the exception we were expecting. + @throw; + } + } - crap = [NSString stringWithCharacters:&carac length:1]; - [image lockFocus]; [[NSGraphicsContext currentContext] setShouldAntialias: antiAlias]; if (bgColor) { bgColor = [bgColor colorWithAlphaComponent: useTransparency ? 1.0 - transparency : 1.0]; -- Marc Haisenko ma...@da... |
From: Marc <ma...@da...> - 2008-09-25 19:27:47
|
Hi folks, back in April I've sent an e-mail that talked about a patch but dumb as I am I forgot to add the patch. Here it is. This patch adds a new cursor type that improves the visibility of the cursor. Currently you have to specify the cursor color. This just doesn't work when you have changing dark and bright backgrounds. The solution is to do it like other terminal applications, e.g. KDE's Konsole. The cursor background is the characters foreground color and vice versa. Together with blinking this ensures that the cursor is always visible. The attached patch does not contain the necessary GUI changes for the preferences panel. I just couldn't find a good way (one that I thought would be good enough for other users) to do that UI-wise and my XCode experience is still very low. So whoever wants to incorporate the patch needs to add the corresponding GUI stuff or use "defaults" to set it: defaults write net.sourceforge.iTerm CursorType 3 Bye, Marc |
From: Marc <ma...@da...> - 2008-09-25 19:18:03
|
Hi folks, after updating to Mac OS X 10.5.2 I experienced a huge problem with iTerm on my MacBook Pro (but not my iMac at work): after starting up iTerm hung up. The UI rendered, but upon trying to render the session nothing happened. I then got the latest CVS version, but with the same problem. But in XCode I saw an error message regarding a deadlock in NSLock: Thu Sep 25 20:34:52 neotokyo.local iTerm[14091] <Warning>: CGSResolveShmemReference : reference offset (65296) exceeds bounds (32768) on shmem obj 0x2f69 2008-09-25 20:34:52.793 iTerm[14091:10b] Error (1000) creating CGSWindow 2008-09-25 20:34:52.806 iTerm[14091:10b] *** -[NSLock lock]: deadlock (<NSLock: 0xfcccc0> '(null)') 2008-09-25 20:34:52.806 iTerm[14091:10b] *** Break on _NSLockError() to debug. But it turned out that the deadlock was only the symptom, not the cause. After some googling, it seems that the "Error (1000) ..." stuff is a bug in Mac OS X 10.5.x. It's running inside code that is started with a [VT100Screen tryLock]. Because of the exception, the corresponding [VT100Screen releaseLock] is never called. Then the same thread later tries to run [VT100Screen acquireLock] and there you have your deadlock. I traced the exception to PTYTextView::_renderChar (how do you write that in Objective-C syntax ?), more precisely to [image lockFocus]. The attached patch works around the bug by packing the [image lockFocus] into a @try @catch block. It retries the lockFocus up to five times. If that still does not work then the exception is rethrown. That fixes the hang problem for me. Bye, Marc |
From: Ben B. <in...@em...> - 2008-09-20 18:09:05
|
Wouldn't a better, more portable approach be to rebind the commands in your screenrc? -Ben ------- Original message ------- From: Claus Atzenbeck <cla...@fr...> To: ite...@li... Sent: 9/20/'08, 9:03 > Hello: > > I'm using several terminals via screen. I can switch to the next one via > "CTRL-a n" and to the previous with "CTRL-a p". I want to bind those to > "CTRL-<home>" and "CTRL-<end>" keys. > > How can I add those commands to iTerm's key mapping settings? I played > around with it, but did not find the appropriate sequence to enter. > > Thanks, > Claus > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Iterm-discuss mailing list > Ite...@li... > https://lists.sourceforge.net/lists/listinfo/iterm-discuss |
From: Claus A. <cla...@fr...> - 2008-09-20 14:04:07
|
Hello: I'm using several terminals via screen. I can switch to the next one via "CTRL-a n" and to the previous with "CTRL-a p". I want to bind those to "CTRL-<home>" and "CTRL-<end>" keys. How can I add those commands to iTerm's key mapping settings? I played around with it, but did not find the appropriate sequence to enter. Thanks, Claus |
From: David N. <dn...@ne...> - 2008-08-06 04:39:33
|
On 8/5/08 12:46 AM, Marc Haisenko wrote: > On Monday 04 August 2008, David Newman wrote: >> Build 0.9.5.0517 on OS X 10.5.4 Intel >> >> How to run a perl script each time a new iTerm tab or window opens? >> >> thanks >> >> dn > > Put it in your ~/.profile ? > Marc > bingo thanks dn |
From: Marc H. <ma...@da...> - 2008-08-05 07:46:45
|
On Monday 04 August 2008, David Newman wrote: > Build 0.9.5.0517 on OS X 10.5.4 Intel > > How to run a perl script each time a new iTerm tab or window opens? > > thanks > > dn Put it in your ~/.profile ? Marc |
From: David N. <dn...@ne...> - 2008-08-04 17:28:51
|
Build 0.9.5.0517 on OS X 10.5.4 Intel How to run a perl script each time a new iTerm tab or window opens? thanks dn |
From: Andrew B. <an...@gm...> - 2008-07-25 03:51:24
|
I'm really annoyed by the labels on tabs in iTerm changing color when things happen in them. Is a way that I can turn such notifications off, just leaving the tab labels plain? Thanks for your help. Peace, Andrew -- ======================= Andrew D. Ball 勃安 deus caritas est http://www.ibiblio.org/adball/blog/ http://filebox.vt.edu/~anball1/ |
From: Marc <ma...@da...> - 2008-04-11 20:50:29
|
Hi folks, attached is a patch that adds a new cursor. It should propably be done differently but it works as I want it to and would like to share it with you nevertheless. The current box cursor suffers from the problem that its background color is fixed. If I set it to a bright color I have a problem with bright backgrounds, and if I set it to a dark color it's the same problem with dark backgrounds. Unfortunately I often find myself having different background colors when using different CLI applications. The solution is to do the same thing as other terminal programs (e.g. KDE's konsole) do: the cursor just inverts the character. So the character where the cursor on has the character foreground as background and the characters background as foreground. If the window is inactive a border in the same color as the character is printed instead. What's missing in this patch is the changes to the PreferencePanel. I think it got converted by my XCode on Leopard to a new format (I'm more of a Linux guy who loves vim, mc and make :-) and am not very familiar with XCode yet... at least I managed to implement what I wanted pretty quickly). All you have to do is to enhance the cursor radio buttons by a new element (I made it two rows and two colums) and give the new element the tag "3". Have fun, Marc -- Marc Haisenko ma...@da... |
From: Richard B. <BrunosJunk@Bronosky.com> - 2008-01-26 05:15:23
|
I spend all day in VIM. I really wish I could find a color scheme that I can live with. No matter what I do I always end up with combinations of foreground and background colors that I cannot read. I hate that the same bright green or dark purple that is used for a foreground color is also used for a background color. I've haven't looked at the code yet, but I'm going to look and see if I can find a way to make ANSI color used for backgrounds actually show up as half way between the ANSI color and the color set as the background preference. Any ideas are appreciated. (Like, "the code you need to modify in the the file blah") Please advise. -- .!# RichardBronosky #!. |
From: Daryl S. <dar...@gm...> - 2007-11-08 23:50:17
|
I thought I recall seeing this in someone else's shell, but perhaps I was mistaken. (Maybe I'm thinking of stderr & stdout in TextMate.) Thanks. -- Daryl On 11/8/07, Ben Beuchler <in...@em...> wrote: > On Thu, Nov 08, 2007 at 03:09:02PM -0800, Daryl Spitzer wrote: > > > How do I configure bash and/or iTerm to display stderr output in a > > different color? > > Bash and the term don't really know what text came from stdout and what > came from stderr. Without capturing both output streams and wrapping 'em > in ANSI (or re-writing the app to output ANSI directly) I don't think it's > possible. > > > I found instructions for getting `ls` output to display in color: put > > the following in ~/.bash_profile: > > Note that ls natively supports colorizing stuff so it can directly output > the necessary ANSI sequences. > > -Ben > > -- > Ben Beuchler There is no spoon. > in...@em... -- The Matrix > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Iterm-discuss mailing list > Ite...@li... > https://lists.sourceforge.net/lists/listinfo/iterm-discuss > |
From: Ben B. <in...@em...> - 2007-11-08 23:40:12
|
On Thu, Nov 08, 2007 at 03:09:02PM -0800, Daryl Spitzer wrote: > How do I configure bash and/or iTerm to display stderr output in a > different color? Bash and the term don't really know what text came from stdout and what came from stderr. Without capturing both output streams and wrapping 'em in ANSI (or re-writing the app to output ANSI directly) I don't think it's possible. > I found instructions for getting `ls` output to display in color: put > the following in ~/.bash_profile: Note that ls natively supports colorizing stuff so it can directly output the necessary ANSI sequences. -Ben -- Ben Beuchler There is no spoon. in...@em... -- The Matrix |
From: Daryl S. <dar...@gm...> - 2007-11-08 23:09:06
|
This is probably more of a bash question than an iTerm question, but perhaps someone here can help me... How do I configure bash and/or iTerm to display stderr output in a different color? I found instructions for getting `ls` output to display in color: put the following in ~/.bash_profile: export TERM=dtterm # ("xterm-color" also works in place of "dtterm"--I have yet to notice a difference) alias ls='ls -G' ...but stderr output continues to come up in the normal text color. -- Daryl Spitzer |
From: Alexy K. <del...@gm...> - 2007-10-05 14:30:21
|
I'd like to change a session/window encoding from Apple Script, but perusing iTerm in AppleScript editor didn't see such an option -- is it there? What would be an example? Cheers, Alexy |
From: Ben B. <in...@em...> - 2007-08-31 01:03:21
|
I've had good success with xterm and xterm-color on FBSD. -Ben ------- Original message ------- From: Yuriy B. Borisov <yok...@yo...> Sent: 8/30/'07, 5:14 > Hello! > > I try use iTerm (version 0.9.5) on my MacBook (Darwin Kernel Version 8.10.1), > but face the challenge. > With "mrxvt" terminal type, don't work arrow key in vim. > Than i set "linux" terminal - arrow key work correctly, but in mutt on my freebsd host drowning "mq>" instead "--". > > What terminal type work correctly whith freebsd? > > Thanks! > > -- > WBR, Yuri B. Borisov > YOKO-UANIC | YOKO-RIPE > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Iterm-discuss mailing list > Ite...@li... > https://lists.sourceforge.net/lists/listinfo/iterm-discuss |
From: Yuriy B. B. <yok...@yo...> - 2007-08-30 10:14:42
|
Hello! I try use iTerm (version 0.9.5) on my MacBook (Darwin Kernel Version 8.10.1), but face the challenge. With "mrxvt" terminal type, don't work arrow key in vim. Than i set "linux" terminal - arrow key work correctly, but in mutt on my freebsd host drowning "mq>" instead "--". What terminal type work correctly whith freebsd? Thanks! -- WBR, Yuri B. Borisov YOKO-UANIC | YOKO-RIPE |
From: David N. <dn...@ma...> - 2007-08-06 13:58:54
|
Just wanted to let everyone posting to this list that I am reading every post. I'm busy finishing a thesis for my Masters degree (as well as work being really funky), so I haven't had time to reply. I am queuing everything. If you're reporting a bug or asking for an enhancement via the list, please also add it to the appropriate section of the SourceForge tracker.... http://sourceforge.net/tracker/?group_id=67789 ( http://tinyurl.com/27p4ez ) I know the other iTerm devs are in similar time crunches, so direct responses are a bit slow for now. Here are some plans that I know are being worked on... Security updates (specifically shell validation) UI enhancements Emulation expansion -David Nedrow Columbus, Ohio, USA |
From: Marc B. <ba...@sm...> - 2007-07-31 13:54:50
|
Hi, First off, I'd like to state that overall I am a very happy iterm user. I was lately trying some tips and tricks to improve my command line=20 settings, one of which is to be able to navigate words forward or=20 backward on the command line. For this it is suggested to add the=20 following to =7E/.inputrc: =5Ce=5B5C=22: forward-word =22=5Ce=5B5D=22: backward-word =22=5Ce=5Ce=5BC=22: forward-word =22=5Ce=5Ce=5BD=22: backward-word This works fine in Terminal.app, but has no effect in iterm. I'm=20 confident that this is probably not a bug, but a feature of iterm that=20 I haven't yet figured out. Any suggestions? Thanks in advance, Marc Baaden --=20 Dr. Marc Baaden - Institut de Biologie Physico-Chimique, Paris mailto:baaden=40smplinux.de - http://www.baaden.ibpc.fr FAX: +33 15841 5026 - Tel: +33 15841 5176 ou +33 609 843217 |
From: Ben B. <in...@em...> - 2007-07-30 21:48:59
|
On Mon, Jul 30, 2007 at 01:35:46PM -0600, Jed Hurt wrote: > So I take that to mean that iTerm doesn't expose an API to control the > full spectrum of colors that it can display? I'm not an iTerm developer. I don't know what APIs may be exposed, but it seems unlikely that you would be able to adjust the values of the individual ANSI colors using escape sequences. It appears AppleScript may be able to adjust some of colors (background, foreground, bold, etc.), but I don't see a way to manipulate the ANSI colors. If you switch your terminal emulation to xterm-256color, you have access to the expanded 256 color palette: mojito:~ insyte$ export TERM=xterm-256color mojito:~ insyte$ tput colors 256 -- Ben Beuchler There is no spoon. in...@em... -- The Matrix |
From: Jed H. <jed...@gm...> - 2007-07-30 19:35:47
|
So I take that to mean that iTerm doesn't expose an API to control the full spectrum of colors that it can display? On 7/29/07, Ben Beuchler <in...@em...> wrote: > It supports 256 colors, like xterm. iuse 256 color themes in vim and 256 color bash prompts. For examples and a list of escape sequences, see the Bash Prompt > HOWTO. > > -Ben > > ------- Original message ------- > From: Jed Hurt <jed...@gm...> > Sent: 7/29/'07, 17:40 > > > Does iTerm support any color control sequences other than the ANSI 16? > > I would like to color text output using a Ruby script, but the ANSI 16 > > are pretty limiting. As iTerm can color text from the session info > > window using the full 32-bit palette, I'm assuming there must be some > > way to do it from within the terminal with scripting? > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Iterm-discuss mailing list > > Ite...@li... > > https://lists.sourceforge.net/lists/listinfo/iterm-discuss > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Iterm-discuss mailing list > Ite...@li... > https://lists.sourceforge.net/lists/listinfo/iterm-discuss > |