- Status Closed
- Percent Complete
- Task Type Bug Report
- Category
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 1.0 Gem (Stable)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#15 - Quick Key Combo: Ctrl+Alt+Ins = 2 terminals
Try it out, I get two terminals directly over top of each other. I think some people might not have an “Ins” or Insert key, does anyone have a different default key that they use to bring up a term (x2) window?
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
On the last version of 0.5 ? (0.5 dev beta-2) only launch’s one terminal for me... tested on e16 and e17, liveCD mode
What version of Elive ? installed or live ?
I used 0.5 Beta-1, not Beta-2 (the newest) and it was the installed version. When I “remembered” the terminals “location” with the built in elive option (Alt + Right Click) I think... lol. Before I remembered the windows, they would line up side by side, now with this option chosen, the are over top of each other directly. Thanatermesis, I believe when I Used the new Beta-2 LiveCD, I got 2 windows with (Ctrl + Alt + Ins), I could be wrong :\ and when I use (Ctrl + Alt + E) I get one window. I hope this info helped, post again if you are confused with my problem :P Peace.
Mmmh... well, anyways if is a problem of a old version of Elive, in simple words, “this problem is solved”, i remember this stuff but long time ago and i have fixed it
I have tried this on e16 and e17 of the last iso of Elive, but nothing similar to 2 terminals, i close this ticket because the problem looks simply fixed, anyways try to make a look again and if you found it, on the last iso build, reopen the ticket explaining the steps for reproduce the problem here