I can reproduce this with tcsh 6.12. After
it only echos the typed commands, without running them.
Looks like a bug.
Try
Doesn't this even make more sense?
Thank you for confirming this.
It seems like no workaround, does it?
I haven't tried postcmd, I ‘ll try this to see what happen. Thanks.
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)
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)
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)
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)
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)
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)
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)
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)
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
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)