On 6 Oct, Peter Wu wrote: > Hello, > > When I run a program with scanf() function in linux, > the program goes through without pause. It doesn't wait for me > to input for scanf(). > I tried the different option for command.go.subsystem, it doesn't work. > > However, the same program works fine in windows in scite. > > Any suggestions? > Thanks.
There is a possibility we use in our students lab. We don't use the output pane of SciTE which seems to be limited but we run the executable in an xterm. Here is an excerpt of my cpp.properties CFLAGS=-pedantic -Wall -g cc=g++ $(CFLAGS) -c $(FileNameExt) -o $(FileName).o GoCmd=[[ -x $(FileDir)/$(FileName) ]] && xterm -T $(FileName) +ls +sk -sl 512 -geometry 80x40-0+0 -hold -e $(FileDir)/$(FileName) GoNeeds=[[ $(FileNameExt) -nt $(FileName) ]] && g++ $(CFLAGS) $(LDFLAGS) $(FileNameExt) -o $(FileName) command.compile.*.cpp=$(cc) command.build.*.cpp=$(make.command) command.go.*.cpp=$(GoCmd) command.go.needs.*.cpp=$(GoNeeds) Some comments: The shell construct [[ -x $(FileDir)/$(FileName) ]] && .... makes sure, the xterm is only started if there is an executable. This is helpful if students still have compile time errors. But this has a slight disadvantage: One cannot use SciTE's cancel button (don't ask me why) but one has to close the xterm window ( a tiny button 'x' in most window managers ) But if one uses directly GoCmd=term -T $(FileName) +ls +sk -sl 512 -geometry 80x40-0+0 -hold -e $(FileDir)/$(FileName) SciTE's cancel button does work. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany _______________________________________________ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest