03-31-2010
Long and interesting but harmless Terminal script
Hi,
I was mucking around with Maven for Eclipse the other day, working on an audio visual project and I was struck by how cool the terminal executing massive amounts of commands is.
I have an odd request. I was wondering if people knew of a terminal script that outputed a lot of data, ideally varied and interesting data (not just text), but which didn't really do anything to one's computer.
I would ideally use this as a live video filter in my VJ work - or alternatively try and screen record the resulting output.
What would infact be even better, is if I could somehow create a screen grab of each new line outputed in terminal then comp those individual screen grabs into a movie file.
Strange request I realise - but any help in the right direction would be much appreciated.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I wrote a script, which would ideally take about 480 hours to runs (It has to do a same thing 60 times.) But the problem is I have to use a VPN Client to get to the network before connecting to the machine. The Client automatically closes after 10 hours, closing my console and thus my... (3 Replies)
Discussion started by: sakya_trips
3 Replies
2. UNIX for Dummies Questions & Answers
Is there a way to tell how long does a shell script(or a shell command)'s execution take? (4 Replies)
Discussion started by: meili100
4 Replies
3. Shell Programming and Scripting
When running a ksh script, how would you time how long it took the script ran for?
Is there a command that can capture this? (1 Reply)
Discussion started by: Jazmania
1 Replies
4. Shell Programming and Scripting
Hi,
I have written a tcsh script that reads 3 directories, lists the files within them and continues on to evaluate each file independently. When I run the script, it gets to a certain directory that contains ~250 files, when you echo the directory, there are 4332 characters. So, when I use the... (1 Reply)
Discussion started by: nixjennings
1 Replies
5. OS X (Apple)
Hello,
I was wondering how to change a user's Long Name through the terminal. I am writing a shell script to change some settings back to the default, and could not find how to do this (or even if you can do this).
I do not want to use applescript. (2 Replies)
Discussion started by: The Reepr
2 Replies
6. Ubuntu
You probably know the answer to this, because I know it exists.
I have super long filenames with md5 hashes and I sucks to type the whole hash in the console. Because... just because :P
What is the shortcut for selecting a file in the current directory? Like you get a sort of loop through the... (1 Reply)
Discussion started by: hellfire1
1 Replies
7. UNIX for Dummies Questions & Answers
Hi!
I have to run a very long script. I use a ssh client on Windows in order to connect to a HP-UX box. What I try to avoid is the possibility that the Windows machine reboots or loses the connection to the Unix machine before the script finishes.
Somebody told me that xterm could help me. He... (2 Replies)
Discussion started by: Ricardo Vargas
2 Replies
8. Shell Programming and Scripting
Hi,
I have a lengthy script which i have trimmed down for a test case as below.
more run.sh
#!/bin/bash
paths="allpath.txt"
while IFS= read -r loc
do
echo "Working on $loc"
startdir=$loc
find "$startdir" -type f \( ! -name "*.log*" ! -name "*.class*" \) -print |
while read file
do... (8 Replies)
Discussion started by: mohtashims
8 Replies
9. War Stories
Hello All,
Finally I am posting an issue and it's solution which I faced last week. Let me explain it by headings.
Issue's background: It was a nice Tuesday for me, went to office as usual started checking emails and work assigned to me. Suddenly a gentleman reached out to me on my desk(in a... (2 Replies)
Discussion started by: RavinderSingh13
2 Replies
10. Shell Programming and Scripting
I was wondering if I could get some feedback on my script to grab time from our MDM... I blocked out all of the important stuff. I really appreciate any guidance, since I am long out of practice.
#!/bin/bash
serial=$1
# get last seen value of ipad
lastseen=$(curl -s -X "GET"... (11 Replies)
Discussion started by: andysensible
11 Replies
LEARN ABOUT REDHAT
set_term
curs_initscr(3X) curs_initscr(3X)
NAME
initscr, newterm, endwin, isendwin, set_term, delscreen - curses screen initialization and manipulation routines
SYNOPSIS
#include <curses.h>
WINDOW *initscr(void);
int endwin(void);
bool isendwin(void);
SCREEN *newterm(char *type, FILE *outfd, FILE *infd);
SCREEN *set_term(SCREEN *new);
void delscreen(SCREEN* sp);
DESCRIPTION
initscr is normally the first curses routine to call when initializing a program. A few special routines sometimes need to be called
before it; these are slk_init, filter, ripoffline, use_env. For multiple-terminal applications, newterm may be called before initscr.
The initscr code determines the terminal type and initializes all curses data structures. initscr also causes the first call to refresh to
clear the screen. If errors occur, initscr writes an appropriate error message to standard error and exits; otherwise, a pointer is
returned to stdscr.
A program that outputs to more than one terminal should use the newterm routine for each terminal instead of initscr. A program that needs
to inspect capabilities, so it can continue to run in a line-oriented mode if the terminal cannot support a screen-oriented program, would
also use newterm. The routine newterm should be called once for each terminal. It returns a variable of type SCREEN * which should be
saved as a reference to that terminal. The arguments are the type of the terminal to be used in place of $TERM, a file pointer for output
to the terminal, and another file pointer for input from the terminal (if type is NULL, $TERM will be used). The program must also call
endwin for each terminal being used before exiting from curses. If newterm is called more than once for the same terminal, the first ter-
minal referred to must be the last one for which endwin is called.
A program should always call endwin before exiting or escaping from curses mode temporarily. This routine restores tty modes, moves the
cursor to the lower left-hand corner of the screen and resets the terminal into the proper non-visual mode. Calling refresh or doupdate
after a temporary escape causes the program to resume visual mode.
The isendwin routine returns TRUE if endwin has been called without any subsequent calls to wrefresh, and FALSE otherwise.
The set_term routine is used to switch between different terminals. The screen reference new becomes the new current terminal. The previ-
ous terminal is returned by the routine. This is the only routine which manipulates SCREEN pointers; all other routines affect only the
current terminal.
The delscreen routine frees storage associated with the SCREEN data structure. The endwin routine does not do this, so delscreen should be
called after endwin if a particular SCREEN is no longer needed.
RETURN VALUE
endwin returns the integer ERR upon failure and OK upon successful completion.
Routines that return pointers always return NULL on error.
NOTES
Note that initscr and newterm may be macros.
PORTABILITY
These functions are described in the XSI Curses standard, Issue 4. It specifies that portable applications must not call initscr more than
once.
Old versions of curses, e.g., BSD 4.4, may have returned a null pointer from initscr when an error is detected, rather than exiting. It is
safe but redundant to check the return value of initscr in XSI Curses.
SEE ALSO
curses(3X), curs_kernel(3X), curs_refresh(3X), curs_slk(3X), curs_util(3X)
curs_initscr(3X)