Sponsored Content
Top Forums Shell Programming and Scripting Spawning new shells from the command line in OpenStep 4.2 Post 55152 by Rocketman8541 on Friday 3rd of September 2004 06:11:48 PM
Old 09-03-2004
Spawning new terminal windows from the command line in OpenStep 4.2

Hi all,

Im trying to figure out what the command would be to launch terminal windows from the command line in Open Step 4.2 . (looking for something similiar like /usr/bin/xterm or /usr/bin/dtterm etc)

echo $TERM = vt100

echo $SHELL = /bin/csh

Im combing over alot of OpenStep 4.2 and other apple related docs with little success.

Let me know if anybody needs further info to answer this question any help is appreciated !

EDIT: Im trying to launch new terminal windows not just change shells

Last edited by Rocketman8541; 09-13-2004 at 03:55 PM..
 

10 More Discussions You Might Find Interesting

1. Solaris

spawning new shells using dtterm in Solaris 8

Hi all, First time poster here. Great forum. Im trying to spawn new shells and pass commands to the new shells in a solaris 8 environment utilizing dtterm and its option -e. I can successfully spawn a window utilizing the following code: /usr/dt/bin/dtterm -display <ip.address> & ... (4 Replies)
Discussion started by: Rocketman8541
4 Replies

2. Shell Programming and Scripting

Spawning a shell script

Hi there, I have a shell script which I need to run it from two different places on the same server, are there any specific rules I need to apply? What is the best practice to achieve this task. Regards (5 Replies)
Discussion started by: JimJim
5 Replies

3. UNIX for Advanced & Expert Users

spawning the same program

We have a program (reader) that reads audio files in a real-time continuous stream from a sender program. If the reader gets weird we want the sender to be able to send one command that will stop the current reader and start a new one that will be able to continue reading in the files. The sender... (9 Replies)
Discussion started by: laforge
9 Replies

4. UNIX for Advanced & Expert Users

Crontab spawning multiple at processes

Hi - I need help. My user crontab is spawning multiple at processes (and multiple mencoder program starts, that exit, then restart, repeatedly), locking up my system. For example I have this entry in my crontab: $ sudo crontab -u victoria -e * * * * * ~/recordings/pvr1 * * * * *... (10 Replies)
Discussion started by: gstuart
10 Replies

5. UNIX for Dummies Questions & Answers

Difference in command syntax different shells

hi, i am aa unix amateur and i am using tsh, csh and bash most of the time. i have been looking over the net to find a summary of the differences in command syntax for example: in csh and tsh you do alias whatday date while in bash and ksh you do alias whatday=date i just want more... (2 Replies)
Discussion started by: hobiwhenuknowme
2 Replies

6. UNIX for Dummies Questions & Answers

Differences in BASH and ASH shells regarding if command?

Guys I now have a script that's working in a BASH environment, however one line doesn't appear to be working on an embedded device that has a busybox therefore ASH shell. I've googled but there's very little I can find regarding the ASH shell. In BASH the following line works... if ] ;... (6 Replies)
Discussion started by: Bashingaway
6 Replies

7. Programming

Problems compiling OpenStep program.

I use Ubuntu 10.4, and I installed GNUStep, Gorm (a gui builder) and ProjectCenter (the GNU alternative to Xcode) because I want to develop Objective-C apps. I opened the ProjectCenter and I created an application that displays only an empty window. I sourced the GNUstep.sh and I compiled the app. ... (0 Replies)
Discussion started by: mghis
0 Replies

8. Shell Programming and Scripting

lost the $ prompt - am I spawning shells??

When trying to get the correct syntax to cron a script that creates a file with the date stamp as its output, sometimes I get these results: - from the command line, I may encounter an error that leaves me without the usual $ prompt. Am I in a new shell? I try to exit it with 'exit' or :q! and... (1 Reply)
Discussion started by: landog
1 Replies

9. UNIX for Dummies Questions & Answers

MAN command for various shells

Whenever I run manual page on a command I get information about arguments, syntax and so on. However, I wounder if that information is valid only for a certain shell and if yes, then for which one? In other words, would I have different man outputs for csh, ksh, bash and others? Thanks (7 Replies)
Discussion started by: rdogadin
7 Replies

10. Shell Programming and Scripting

Spawning a TTY shell

Hi there, I would like to understand the purpose of spawning a TTY shell? Does it mean that it will help to open up a new Windows on the current interactive shell such that when the session gets lost the other won't Any explanation will be helpful. (3 Replies)
Discussion started by: alvinoo
3 Replies
echo(1B)					     SunOS/BSD Compatibility Package Commands						  echo(1B)

NAME
echo - echo arguments to standard output SYNOPSIS
/usr/ucb/echo [-n] [argument] DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output. echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi- ronment variables. For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows: o echo your current-working-directory's full pathname o pipe the output through tr to translate the path's embedded slash-characters into space-characters o pipe that output through wc -w for a count of the names in your path. example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w" See tr(1) and wc(1) for their functionality. The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's echo() also understands a as the audible bell character; however, these commands do not have an -n option. OPTIONS
-n Do not add the NEWLINE to the output. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscpu | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5) NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases. SunOS 5.11 3 Aug 1994 echo(1B)
All times are GMT -4. The time now is 12:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy