02-28-2019
Quote:
Originally Posted by
Corona688
What does 'jumping to the newline' mean?
Sorry, I didn't describe it clearly.
I mean after running my script, I input any coomands and then press enter, it shows nothing. I can't even use exit command to close the terminal.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm working on OpenOffice Localization; In that I need to work most of in 'tcsh'
Since I have almost work till now in 'bash', I want to explore 'tcsh' much more ..
An body suggest me a way ? books ?
Thanks,
:) (1 Reply)
Discussion started by: kartik
1 Replies
2. UNIX for Advanced & Expert Users
As in Windows we have Video memory and we can access it through C programs, do we have anything similar to that in Unix and similar operating systems. If we have some sort of Video memory in Unix flavours, then how can we access it through C programs. (4 Replies)
Discussion started by: rahulrathod
4 Replies
3. UNIX for Dummies Questions & Answers
I recently purchased a book titled Hacking: The Art of Exploitation. When I got it home I read the preface and found out that i shouldnt have bought it. It says the code examples in this book were done on an x86 based computer (I have a mac). Is there anything I can do to make my mac run similar to... (2 Replies)
Discussion started by: Cyberaxe
2 Replies
4. Shell Programming and Scripting
I need to write a tcsh script which would compare files in the two folders and then send me a mail saying which of the files are missing.For eg
1) I have this folder1 containing all the files which must land on folder2 on a daily basis.
2) If a file is present in folder1 but not in... (6 Replies)
Discussion started by: kumarsaravana_s
6 Replies
5. UNIX for Dummies Questions & Answers
am working in tcsh
while writing a script, what is diff between foll two starting line
#!/bin/csh
#!/bin/csh -f
Also can I use the same line for script in tcsh or I have to necessarily use
#!/bin/tcsh
I guess even #!/bin/sh will also do. Kindly clarify (3 Replies)
Discussion started by: mahendrakamath
3 Replies
6. Shell Programming and Scripting
I want to search line-by-line for a string in a file, and I want to do this to a series of files in a directory. I'm doing this in tcsh
This works fine to do the search:
while read i; do grep $i file2; done <file1.txt
This also works fine to read a directory:
foreach file ('/bin/ls... (1 Reply)
Discussion started by: moldoverb
1 Replies
7. Shell Programming and Scripting
Hi!
I want to log out of the tcsh shell without updating the history?
Thanks,
Jack. (3 Replies)
Discussion started by: jacki
3 Replies
8. Shell Programming and Scripting
Does anyone no way my .tcsh_history file is filling up with a bunch of crap?? It is filled with lines like:
! ls eccracrascratcd ! ls mecd /hchoo "cratch2/mecd /sch2/mecd /sh2/mecd /scratchcd /scratch2/mecd /scratcraecd /ls mo "ls" >
! ls eccratch2/mecd /sc/ls"d /scratch2/mecd histecho "ls" o... (2 Replies)
Discussion started by: Bic121
2 Replies
9. Shell Programming and Scripting
Dear all,
I have piece of command from tcsh, which I would like to be in my .bashrc file.
However, I am comletely blank about the tcsh commandline.
if (-e ~/forum/dir/code.sh) then
source ~/forum/dir/code.sh
endif
Any piece of suggestions how to convert it to sh way?
Thank you
emily (5 Replies)
Discussion started by: emily
5 Replies
10. Shell Programming and Scripting
Hallo,
I try to write a program which processes an input-file linewise.
I created the following minimal example:
hash-problem:#!/bin/tcsh
foreach text ("`cat $1`")
echo $text
endUsually, it works as expected, but there are two problems:
1. If the argument of hash-problem has an... (3 Replies)
Discussion started by: DanielDD
3 Replies
win(1) General Commands Manual win(1)
NAME
win - Terminal emulator
SYNOPSIS
win [-v] [-t name] [command [argument ...]] address
OPTIONS
-v If the -v option is present, win prints its version number and date and exits.
-tname If the -t option is present, win uses +name as the final part of the tag name of its window.
DESCRIPTION
win must be able to connect to a running wily(1). win attaches to a window. If the -t option is present, the final part of the tag name
is name. If command is present, the final part of the tag name is +command. Otherwise, the final part of the tag name is +win. The first
part of the tag name is the current working directory.
win runs a program in a child process. The child process is the leader of a process group and is connected to win by a pseudo-terminal.
If command is specified, the child process runs
$SHELL -c 'command argument ...'
otherwise it runs
$SHELL -i
If SHELL is not found in the environment, /bin/sh is used.
TERM=win is placed in the environment of the running program.
Output from the running command appears in the window. The point after the last output from the running command is known as the output
point. Further output from the running command appears just before the output point. The output point is initially at the end of the win-
dow.
Normal wily editing commands work in the window. When a newline, interrupt character, or end-of-file character is created after the output
point, the text between the output point and the last newline, interrupt character, or end-of-file character in the window (inclusive) is
passed to the running program as input.
The interrupt character is control-C and the end-of-file character is control-D. The pseudo-terminal initially is configured so that these
are recognized with their normal meanings.
The B2 commands beginning with the |, <, or > characters or an upper case letter are executed normally by wily. Other B2 are first termi-
nated with a newline, if they are not already, and are then appended to the buffer (and thereafter passed to the running program).
RETURNS
win returns zero if it is able to successfully create the child process, otherwise it returns non-zero.
EXAMPLES
Run a terminal emulator within wily
win
Run FTP within wily
win ftp
Run rlogin within wily
win -t host.domain rlogin -8 host.domain
SEE ALSO
wily(1) Tag(1) Man(1)
BUGS
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
rlogin seems to need -8 and, annoyingly, sets echo and onlcr. The latter can be fixed in your .rcrc:
if ( ~ $TERM win ) {
stty -echo -onlcr
}
win doesn't follow changes to the terminal attributes. In particular, there is no way to stop echoing or to change its concept of the
interrupt and eof characters.
WEdestroy messages aren't yet passed by wily. Thus, Del and Delcol can delete the window yet leave win running.
There is a race condition; the user can press newline and then delete text before win has a chance to read it.
AUTHOR
win was originally written by Gary Capell (gary@cs.su.oz.au). Alan Watson (alan@oldp.nmsu.edu) rewrote it and added support for arguments,
pseudo-terminals instead of pipes, and execution of certain B2 commands by wily. The pseudo-terminal support in 9term, written by Matty
Farrow (matty@cs.su.oz.au), was a great help.
1R1.1L1 of 1D1 win(1)