Programming guidelines and style Post: 303001740

4 More Discussions You Might Find Interesting

1. Forum Support Area for Unregistered Users & Account Problems

Guidelines For Posting Here

This area is not for technical questions. It is reserved for unregistered users who have a question or registered users who have trouble with their account. Other posts will be deleted by the moderators.

2. What is on Your Mind?

Guidelines for Posting Here

This area is not for forum specific technical questions. Please post forum specific technical questions in the best forum, not in the lounge. However, if your idea or question is not covered clearly in a forum, please post it here. Discuss whatever is on your mind. Technical topics welcome...

3. Shell Programming and Scripting

Unix Shell Scripting Guidelines

Hi, I was wondering if any of you guys have developed shell scripting guidelines for writing unix shell scripts effectively. This includes naming standards, comments, indentation, error handing after unix comands, use of exported variables, sending notifications, functions, logging etc... ...

4. Programming

Building Block style programming Book

Hello to all, Here is my situation. Some time in the mid-80's I stumbled across a small white programming book - can't remember the name but it was unique in that it started right out giving instructions on creating building blocks in code as a foundation for a complete system. The book was...

LEARN ABOUT SUSE

openvt

OPENVT(1)							     Linux 1.x								 OPENVT(1)

NAME

       openvt - start a program on a new virtual terminal (VT).

SYNOPSIS

       openvt [-c vtnumber] [-s] [-u] [-l] [-v] [--] command command_options

DESCRIPTION

       openvt  will  find the first available VT, and run on it the given command with the given command options, standard input, output and error
       are directed to that terminal. The current search path ($PATH) is used to find the requested command. If no command is specified  then  the
       environment variable $SHELL is used.

   OPTIONS
       -c vtnumber
	      Use the given VT number and not the first available. Note you must have write access to the supplied VT for this to work.

       -e     Directly execute the given command, without forking.  This option is meant for use in /etc/inittab.

       -s     Switch to the new VT when starting the command. The VT of the new command will be made the new current VT.

       -u     Figure out the owner of the current VT, and run login as that user.  Suitable to be called by init. Shouldn't be used with -c or -l.

       -l     Make the command a login shell. A - is prepended to the name of the command to be executed.

       -v     Be a bit more verbose.

       -w     wait  for command to complete. If -w and -s are used together then openvt will switch back to the controlling terminal when the com-
	      mand completes.

       --     end of options to openvt.

NOTE

       If openvt is compiled with a POSIX (GNU) getopt() and you wish to set options to the command to be run, then you must  supply  the  end	of
       options -- flag before the command.

EXAMPLES

       openvt can be used to start a shell on the next free VT, by using the command:

       openvt bash

       To start the shell as a login shell, use:

       openvt -l bash

       To get a long listing you must supply the -- separator:

       openvt -- ls -l

HISTORY

       Earlier, openvt was called open.  It was written by Jon Tombs <jon@gtex02.us.es or jon@robots.ox.ac.uk>.  The -w idea is from "sam".

SEE ALSO

       chvt(1), doshell(8), login(1)

19 Jul 1996							       V1.4								 OPENVT(1)