tcsh problem

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Tcsh Problems with # and []

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...

2. Shell Programming and Scripting

Tcsh to sh

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

3. Shell Programming and Scripting

perl in tcsh

hi, I am completely new for tcsh scripting. Trying to write a code, need to implement following function there, perl -pi.bak -e 's/filei/file(i+1)/g' data I want the "i" to increment and this should change the file name as i = 1; file1->file2 i=2; file2->file3 and so on also...

4. Shell Programming and Scripting

tcsh help

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...

5. Shell Programming and Scripting

Problem with File Names under tcsh loop

Hello, I have a question regarding file naming under a loop in tcsh. I have the following code: #!/bin/tcsh foreach file (test/ProteinDirectory/*) # The * is a bunch of ProteinFile1, ProteinFile2, ProteinFile3, etc. sh /bioinfo/home/dgendoo/THREADER/pGenThreader.sh $file $file ...

6. Shell Programming and Scripting

logging out in tcsh

Hi! I want to log out of the tcsh shell without updating the history? Thanks, Jack.

7. UNIX for Dummies Questions & Answers

About tcsh shell

Hello, Why tcsh shell is not recommended ? then which one is better ? Also can you please let me know how to change own shell and config file?

8. UNIX for Dummies Questions & Answers

Problem with xterm & tcsh & sourcing a script in a single command

Hi friends, I have a script that sets the env variable path based on different conditions. Now the new path variable setting should not done in the same terminal or same shell. Only a new terminal or new shell should have the new path env variable set. I am able to do this only as follows: >cd...

9. UNIX for Dummies Questions & Answers

help in tcsh

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

10. Shell Programming and Scripting

tcsh

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, :)

LEARN ABOUT OSX

tklib_history

history(n)					       Provides a history for Entry widgets						history(n)

__________________________________________________________________________________________________________________________________________________

NAME

       history - Provides a history for Entry widgets

SYNOPSIS

       package require Tcl  8.4

       package require Tk  8.4

       package require history	?0.1?

       ::history::init pathName ?length?

       ::history::remove pathName

       ::history::add pathName text

       ::history::get pathName

       ::history::clear pathName

       ::history::configure pathName option ?value?

       bell

_________________________________________________________________

DESCRIPTION

       This package provides a convenient history mechanism for Entry widgets.	The history may be accessed with the up and down arrow keys.

       ::history::init pathName ?length?
	      Arranges	to  remember  the  history of the named Entry widget. An optional length determines the number of history entries to keep.
	      This may be changed later with ::history::configure. History entries must be added with the ::history::add command before  they  can
	      be seen.

       ::history::remove pathName
	      Forgets all history entries for the Entry pathName and removes the history bindings.

       ::history::add pathName text
	      This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
	      called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).

       ::history::get pathName
	      This command returns a list containing the history entries for the Entry pathName

       ::history::clear pathName
	      This command clears the history list for the named Entry.

       ::history::configure pathName option ?value?
	      This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
	      mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
	      the history, it defaults to

       bell

       entry .e
       bind .e <Return> [list ProcessEntry %W]
       ::history::init .e
       pack .e

       proc ProcessEntry {w} {
	   set text [$w get]
	   if {$text == ""} { return }
	   ::history::add $w $text
	   puts $text
	   $w delete 0 end
       }

KEYWORDS

       entry, history

history 								0.1								history(n)

Shell Programming and Scripting