The command line is not only powerful, it can also be dangerous. Learn how to use commands for deleting files and folders correctly to make sure your time with Terminal is a productivity godsend. Nov 18, 2001 The Windows Terminal is a new, modern, fast, efficient, powerful, and productive terminal application for users of command-line tools and shells like Command Prompt, PowerShell, and WSL. Its main features include multiple tabs, Unicode and UTF-8 character support, a GPU accelerated text rendering engine, and custom themes, styles,.
posted 7 years agoSCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
[Asking smart questions] [About Bear] [Books by Bear]
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
[Asking smart questions] [About Bear] [Books by Bear]
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
[Asking smart questions] [About Bear] [Books by Bear]
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
Joe Harry wrote:I found out a way to horizontally and vertically open multiple window panes in a single big monolithic window. But I'm not able to get to that window when I close open iTerm2. I can get back the same old window by clicking Window, restore old window. But I would want to save that once click. Let me check if I could explore more on saving that one click.
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7Personal blog
Click here to return to the 'Create terminal groups for managing multiple windows' hint |
Why not use iTerm? It's freeware, and you get tabs.. Nothing could be finer than having 10 tabs open in a single window.
Because iTerm's tabbing doesn't actually solve the problem at hand. The point of having multiple windows open is to be able to see them all, not have them all in one spot. Though I suppose you could apply the same technique to iTerm as well, it also has the bonus side-effect of allowing you to command-tab through the terminal groups. Garmin adm to gpx converter download free for mac windows 7.
WOW, I tried out 'screen' and this is an awesome utility for any unix/linux terminal management. Thank you, this will save me time!
You can also find an article on installing and using screen at:
http://www.sun.com/bigadmin/features/articles/gnu_screen.html
the only problem I have with screen is I cannot figure out how to make it retain the history of past scrolled lines in *all* windows it has open.
for example, lets assume I have two windows open and there is activity happening in both (lines scrolling by). If I now switch from the current window to another one and try to scroll up to see previous lines that have scrolled by, I can't! It forgets those lines and only shows lines from the window I just switched from.
I really hope someone can tell me how to do this, it's the only thing I haven't managed to figure out even from the man pages. iTerm is really slow for me as well and the combination of GLTerm and screen is just 'perfect'.
I don't know if this is the best way to access the buffer, but what I do is use screen's copy/paste command.
Use the meta key (typically ^a), then '[' to access copy mode.
From there, the arrow keys move the cursor or ^y scrolls up line by line.
When you're done reading scrollback, hit esc, or spacebar twice.
Be careful not to leave the screen in copy mode because it will freeze the shell and sometimes interfere with your process (e.g. ircII or whatever).
You can increase the size of your scrollback per window in your .screenrc file using the 'defscrollback #' command, where # is the number of lines you want. The more you ask for, the more memory each screen will consume. Or you can specify it on a per-screen basis using ^a, ':', 'scrollback #', (return). Use 'man screen' for more details.
HTH,
Thom Brooks
I don't know if this is the best way to access the buffer, but what I do is use screen's copy/paste command.
Use the meta key (typically ^a), then '[' to access copy mode.
From there, the arrow keys move the cursor or ^y scrolls up line by line.
When you're done reading scrollback, hit esc, or spacebar twice.
Be careful not to leave the screen in copy mode because it will freeze the shell and sometimes interfere with your process (e.g. ircII or whatever).
You can increase the size of your scrollback per window in your .screenrc file using the 'defscrollback #' command, where # is the number of lines you want. The more you ask for, the more memory each screen will consume. Or you can specify it on a per-screen basis using ^a, ':', 'scrollback #', (return). Use 'man screen' for more details.
HTH,
Thom Brooks
iTerm is great but it's rendering is *so slow* I can't work with it. A shame. If only Term.app would support tabs..
If it is ok to use the X-Server, you may use the KDE-konsole which provides many consoles in one window.
What context sensitive menu do you mean--the one in the Dock?
I just use the File -> Library menu to open my saved terminals (new in 10.3).
And yes, having the sessions with different colours is great for a quick reminder of their purpose and finding with Exposé.
I've done this before as well, but using the renaming method in addition makes it even better because it allows you to command-tab between sets of terminal windows, something that simply setting up terminal groups doesn't do.
To get your .term files to show up in the File -> Library menu in Terminal the files need to be stored in ~/Library/Application Support/Terminal.
When developing OSX Java apps I've had this problem. My solution has been to rename the application from Terminal. If you do it from Finder then Finder will remember the old data still. If you do it from the Terminal then Finder will think it's a new file and refresh the icon (and other metadata).
ex:
mv Test.app Test2.app
- Joshua
I've been happy using the tabbed feature of iTerm and manage groups of terminals with multiple tabbed iTerm windows.
http://iterm.sourceforge.net/ Wordpress ローカル環境 mac xampp.
If you really use the terminal enough that this is even an issue, do yourself a favor and check out GLTerm:
http://www.pollet.net/GLterm/
It is *THE* number one app on my macs, even though it hasn't been updated for a long time it works perfectly, and it's the fastest terminal app I've ever seen for any platform..
I use a prompt and aliases that set the titlebar of each window to exactly what that window is currently doing.. Combined with the dock flyout menu I can find exactly what I'm looking for very quicky..
I wish it were OSS because there's still a few things I'd like to tweak, but it's the best $10 I've ever spent on software.
- Mike
*sorry for reposting this*
the only problem I have with screen is I cannot figure out how to make it retain the history of past scrolled lines in *all* windows it has open.
for example, lets assume I have two windows open and there is activity happening in both (lines scrolling by). If I now switch from the current window to another one and try to scroll up to see previous lines that have scrolled by, I can't! It forgets those lines and only shows lines from the window I just switched from.
I really hope someone can tell me how to do this, it's the only thing I haven't managed to figure out even from the man pages. iTerm is really slow for me as well and the combination of GLTerm and screen is just 'perfect'.
I've used screen for a decade, and I don't believe there is any way to accomplish this. The reason is that the scrollback buffer is outside of screen's control: a (any) Terminal application just says to the UNIX host 'Hi, I have a text window 80 (or so) columns wide and 44 (or so) rows high, tell me what you'd like to display in it!' Any text within the window is available to UNIX (and screen), and anything even one line above the window* is gone forever from UNIX's awareness- it exists only as a memory structure in whatever terminal emulator you are using- the usual interface to it is the scrollbar.
When screen swaps the text on your screen as you attach to a new session, it has no way of swapping the text in your scrollback buffer. This is indeed the big drawback of screen, and not one that can be easily circumvented. (I suppose you could somehow convince some terminal emulators to give you a window say 500 lines high, but that would lead to really lousy performance and most likely some bizarre display problems.)
Ultimately, your scrollback ends up being a series of fragments of the screens you have recently visited. Tis the nature of the beast.
*the only exception here is this: if you type screen into a window Y rows high, and then later reattach to the session (screen -x) in a window that is fewer than Y rows high, screen will still attempt to provide those rows that were present in the first window from which you launched screen. Same goes for width of the window. If you do the opposite and reattach with a larger window, the original vertical size of the screen will be indicated by a dashed line at the bottom of the new window.
---
gigabling megashiznit
Ahh grasshopper.. You are trying to view screen's history from the terminal. This is impossible. You should instead view screen's history with screen itself. It does keep history.
The way I generally do it is to go into 'copy mode' ^A[ and scroll up (page up works too) from there. Enter twice to leave copy mode.
I'm sure there's a better way to do it but that's what I've always done.
OMG that is so SO cool. I couldn't be happier to be proven wrong!
Hats off to you and macosxhints.com (which, have you noticed, comes up rather a lot in random unix searches.?)
best and happy ^A[-ing,
David
---
gigabling megashiznit