TMUX added one more window which I cannot close - tmux

I am new to TMUX and tried to ask Google correctly but didn't find the answer.
I've been wording on one of the panes which was separated into two windows. One day, I opened the tmux and found out that the third window suddenly appeared.
And I have no idea how to close it. I've tried ctrl+b + right arrow. But the cursor didn't move there. So I assume it's not a regular window
Could you advise, how should I close it?
Thanks

Related

How to scroll with mouse in tmux (not history, but terminal output)

This seemingly simple question, is one I cannot find an answer to. The solutions suggesting adding
setw -g mouse on
into the config, do not work. Yes, the mouse works, but on history. Not on the shell output. I cannot understand the logic behind this... why is this the default? Lets say I issue an ls command. I need to scroll to see the entire output, but tmux prevents this.
EDIT:
I would also like to know why is this the default behavior? What prevents it from behaving like other terminals do?
I had this problem when using Tmux from within iTerm2 on a Mac. I fixed it by going to "Preferences" in iTerm2 and then to the "Advanced" tab. Within there were a bunch of general topics (and a really long list of stuff), and one of them was "Mouse", or something like that. Within there, there was an option that said "Scoll wheel sends arrow keys when in alternate screen mode." This was set to "Yes". I set it to "No", and the problem of went away (i.e. scrolling on my mouse pad no longer made it go back through my command history).

How to remove '(size WxH from force-height)' from tmux unusable area?

I'm using set force-height 28 in tmux to create some unusable space. After setting force-height the dimensions are shown in the bottom right corner of the unusable space. Any way to not show that text?
There doesn't seem to be anything in the man page about removing that string.
With a quick glance at the tmux source code for printing that string, it doesn't appear as if there are any switches for disabling it. If you really hate that string, you could edit the source code and recompile tmux for your system.

clicking or scrolling on terminal outputs text

this is driving me crazy. Everytime I click on the terminal, I get text output but the click does not happen. I can't select anything, scroll on the terminal or perform any mouse operations.
For example, if I click I get things like "TB#TB", which is "TB" when I click and "#TB" when I release the click. If I scroll I get 'UC'` for every scroll of the wheel. Total rubbish.
I'm using cygwin to connect to a redhat machine and it happens only for this one machine. If I connect to a different one, also running redhat, it doesn't happen, so I think the issue is on the remote machine's side. It's also independent of what shell I'm using.
Any ideas?
EDIT: I discovered that pressing shift returns all the usual mouse functionality. I wonder why.
This is more like a "come down to your machine and solve problem"
You must have save default setting for that particular machine to direct it to shift option. As you said shift solves the problem.
You should reset the settings.
go here.
Putty configuration>windows>selection>click on shift overrides application's use of mouse
hope this helps

Sublime Text 2, disable Build output panel/Console automatic scrolling

Apparently everytime a script returns a new line the Build panel/Console on ST2 scrolls to the bottom, which is good so we can always see the latest output information, however when having huge stacks of information with long history it is natural that before a process finished you may want to scroll back and debug the information print before.
Since ST2 always scrolls to the bottom when a new line is inserted into the console, this becomes impossible to achieve.
My question is if is there any way to disable this 'automatic scrolling' for new lines on the build output panel or if somehow it is possible to make it behave just like terminal, where it will only continuing to scroll if your cursor or scroll location is already on the latest item and it becomes inactive as soon as you scroll up.
I hope that makes sense.
thanks in advance
I turns out I was dumb enough to not find out that by double-clicking the console panel it will then stop the scrolling and let me navigate through it. once I scroll again to the bottom, it continues from there.
I'm reasonably sure that this is hardcoded in, but I can be certain since I'm not Jon Skinner :) Most "consoles" act like this, continuously streaming the information as it is collected. Terminal emulators often include a "scroll on output" option to modify this behavior, but in my experience I haven't found anything like this in ST2 or ST3. If your programs are generating the output, you can always sprinkle in statements like print "==========" or something similar to break up the output somewhat, and perhaps give you an idea of where you are when you scroll back through.

in Qt, How do I make a window be the current window?

My QT app has multiple windows and sometimes, even though the windows are already open but burried under other windows, the user will select an option to open one from the mainwindow menubar in which case I want to simply bring it up and make it the current one. Now using QWidget->raise makes this window go on top of all other windows but it doesnt select it and that is what I need to do. I tried QWidget->setFocus but that doesnt do anything. In the mean time I am using a combination of QWidget->close followed by QWidget->show but I would like to know if there is a command to use with ->raise.
I tried:
pMission->raise();
pMission->setFocus(Qt::ActiveWindowFocusReason);
but it didnt work so i used:
pMission->close();
pMission->show();
Have you ever tried QWidget::activateWindow?
From help file, this function is going to
Sets the top-level widget containing this widget to be the active window.
An active window is a visible top-level window that has the keyboard input focus.
On MacOS Lion with Qt 4.8.0, raise() was the only one that worked for me. activateWindow() and setFocus() did not.
(I don't have enough karma to make this a comment on Mason's answer)

Resources