-
-
Notifications
You must be signed in to change notification settings - Fork 862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multi terminal #247
Comments
+1 |
Just a thought, but given the retro philosophy of CRT, people looking for multiple tabs should look to using the "screen" command as we did back when we used those monitors. :) |
👍 |
My two cents: if you do not want to mess with the GNU Screen, I guess the task to open several windows fits more for your WM/DE not for the app itself. |
I want to use this as my main driver, please add tabs! |
Also look into |
I agree with @vphantom. This would take away from the retro experience. |
For those that are interested in multiple cool-retro-terms on their desktop, I've started a branch. https://github.com/adammathes/cool-retro-term/tree/multiterm It works reasonably well on MacOS for me so far but I have not tested what happens on *nix with these changes. And also I have never written any QML/QT before so feedback is welcomed. |
I disagree with @larsbrinkhoff. If implemented like @phroun suggests, it would be awesome and full retro! |
For those who would like to use this terminal as a main one (I know, it's just eye-candy, but it is of the best kind), why wouldn't it be possible to have a terminal option? |
Also, how difficult could be code shift+insert as paste command? |
|
That works too... thanks. |
If you want to open another window of the same app, which, in this case, would be this app, you can try this command (works for OSX, you have to be in the open -n -a cool-retro-term This should open another cool-retro-term window |
I would love CRT to support tabs. |
So are we getting a multi terminal feature or not? |
I agree that tabs are not in the scope of this project and that screen/tmux/... is the solution to that. But when using screen, I find that the default key combo "Ctrl+a Backspace" doesn't work to move to the previous session. "Ctrl+a n" to switch to the next session works fine. Can we have Ctrl+a Backspace? EDIT: I just found out that it works when Ctrl+a are being held down while pressing backspace. Other terminals also accept pressing Ctrl and a succesively. |
I came up with a limited, but very simple way for multiple terminal windows. In MacOS, I copied the application and renamed it to make it a separate app. Now I have two windows to use, which act like separate applications. The downsides are configs won't be shared (you'll have to export in one and import in the other to update your profiles), and you'll need to repeat this depending on how many extra windows you want. The up side is this is a very easy technique that can likely work on any OS. And a bonus, you can now cmd+tab between the terminals, which I actually prefer. It's a bit silly, and you don't get keybindings, but it's simple and works. Two or three terminals is all I usually need, so this works well for me. |
As per #555, I am opening multiple instances absolutely fine via a keyboard shortcut... each trigger fires a new instance. That aside, contending with the issue you're noting about importing the profile, you should look to use the flag to specify this for each instance;
Unless I'm missing something, if you were to create a shortcut (keyboard or old-school), that should suffice without having to duplicate the application. If you open one, you can open another too;
|
Or emacs, you can do multiple buffers plus split the screen plus pretty much anything... |
@frnco |
hi , i'm new for cool-retro-term , cool-retro-term have shortcut key open multi terminal or not ? if not i hope have this feature soon . thank advance !
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/18089712-multi-terminal?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: