Opening Visor terminal returns all other terminal windows to original size (80x24)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start Visor, keep it hidden
2. open a regular terminal window, resize it to something different
3. open the Visor terminal

What is the expected output? What do you see instead?

Expected: all other terminal windows stay the same size
Outcome: all other terminal windows snap back to original 80x24 size

What version of the product are you using? On what operating system?

Visor 1.9.1, OS X Leopard 10.5.6, Macbook 1,1

Configured to open/close on CTRL+~

Original issue reported on code.google.com by dmitriy....@gmail.com on 21 May 2009 at 6:01

[GoogleCodeExporter]

I have hit the same problem.

It's a quite stressing issue. Do you guys know some work-around?

Original comment by alobbs on 1 Jun 2009 at 6:26

[GoogleCodeExporter]

Same problem here...

Original comment by leca...@gmail.com on 12 Jun 2009 at 9:38

[GoogleCodeExporter]

same here needs fixing

Original comment by rald...@gmail.com on 6 Jul 2009 at 1:07

[GoogleCodeExporter]

same here !
need fix !!!

I think Visor should have its own window size configurations, apart from 
standard Terminal profiles so we can 
configure any geometry we want for the visor windows as the other Terminal 
sessions keeps untouched...
Also, would be cool to assign Terminal configuration profiles to Visor, 
different form the standard selected to 
regular Terminal windows. So we can have differente color and behaviour 
profiles to Visor and Terminal 
windows.

Original comment by opti...@gmail.com on 15 Jul 2009 at 4:02

[GoogleCodeExporter]

For anyone who has this issue, it looks like the code that allowed Visor to use 
a custom window profile by 
default, instead of requiring some user provided workaround, was stripped in 
version 1.9.x.  If you revert to 
version 1.8.1-45209c Visor will no longer cause all of your windows to resize.

The main developer on this project, darwin, has expressed that he doesn't see 
this as a real issue and isn't likely 
to fix it any time soon.

Original comment by bjh45...@gmail.com on 21 Jul 2009 at 5:30

[GoogleCodeExporter]

@bjh45964, thanks a million for the work-around. I'm testing it right away.

BTW, if that isn't an issue.. I don't want to imagine what a real issue it'd 
be. IMHO
this is a hell of a bug - to the point, I had to stop using Visor because of 
such an
annoying misbehavior.

Original comment by alobbs on 21 Jul 2009 at 5:43

[GoogleCodeExporter]

An easier work around is as follows:

1.) Clone your default setting and call it "Visor Settings"
2.) In the Startup tab under Preferences, select "On startup, open: new window 
with settings" to be the newly 
created "Visor Settings"
3.) LEAVE your previously defined default setting as the default

The first terminal window (which is always visor) will now have separate 
profile than the subsequently opened 
windows (which will use the old default). This prevents the window resizing.

Original comment by yna...@gmail.com on 21 Jul 2009 at 5:49

[GoogleCodeExporter]

Reverting to 1.8.1 also solves the problem of Visor activating every time 
Terminal is given focus and when the 
dock icon is clicked on.

Original comment by bjh45...@gmail.com on 21 Jul 2009 at 5:51

[GoogleCodeExporter]

any chance to patch it throught 1.9.x ? 1.8.x has many bugs and downgrade to 
solve this, would pop up old 
bad bugs... ( like the can't close tabs with command+w, etc... ) :(

IMHO this is a bug ! Altought Visor is a plugin it should not interfere with 
the regular Terminal windows 
behaviour...

Try to see the following, using 2 monitors and some terminal windows on 
fullscreen or geometrically placed 
on the secondary monitor to monitor some servers, ssh and stuff, and you would 
use Visor as a popup 
terminal for some tasks on your main window... each time you issue Visor, you 
mess all other Terminal 
windows configuration... which is in my opinion a unnaceptable behaviour !

Original comment by opti...@gmail.com on 21 Jul 2009 at 5:53

[GoogleCodeExporter]

OK, 1.8.1 has the annoying behavior of activating visor every time you close a 
window.  I've reverted now to 1.7-
ae75d3, no window resizing, no activating visor on refocus, no activating visor 
on window close.

Original comment by bjh45...@gmail.com on 21 Jul 2009 at 5:54

[GoogleCodeExporter]

Better you guys move to github issues, I do not visit this any more.

I recognized this as a bug, but I'm probably not going to spend time on fixing 
it. That is my perfect right.

Workaround: create non-visored windows with different profile than startup 
profile (right click on terminal 
app dock icon -> new window). 

Setting window size is needed for correct window sliding and I have only option 
to reset size of all windows 
using startup profile (default one when you run terminal.app). Visor is not a 
plugin. Visor is a hack and I don't 
see easy and robust solution right now.

Original comment by antonin....@gmail.com on 29 Jul 2009 at 6:38

[GoogleCodeExporter]

For anyone still watching this thread, the latest code in github fixes this 
bug.  The plugin now checks for a 
profile named "Visor" and creates it if it doesn't exist.  Looks like a fairly 
elegant fix to an annoying issue.

http://github.com/darwin/visor/commit/25a287e2ac179213a760a419ac116889cc09920a

Original comment by bjh45...@gmail.com on 23 Aug 2009 at 11:31

[GoogleCodeExporter]

solved in Visor 2.0

Original comment by antonin....@gmail.com on 6 Sep 2009 at 6:12

• Changed state: Fixed

[GoogleCodeExporter]

This is NOT fixed in Visor 2.0.

Visor ignores the window settings for columns and rows. If I change these 
settings while Visor is shown then it 
will resize correctly. When I hide and show Visor it returns to the default 
super short window size.

I am using the 'Visor' window profile, SIMBL 0.8.2, Visor 2.0, and Mac OS X 
v10.6.

Original comment by petri...@gmail.com on 9 Sep 2009 at 3:15

[GoogleCodeExporter]

This IS FIXED in 2.0, just change your terminal default profile ( new window 
settings ) to a differente profile than 
Visor .

Original comment by opti...@gmail.com on 9 Sep 2009 at 3:19

[GoogleCodeExporter]

Unfortunately I've introduced a new bug in Visor 2.0:
http://github.com/darwin/visor/issues#issue/22

But this bug is technically fixed.

Original comment by antonin....@gmail.com on 9 Sep 2009 at 3:22