octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: default ~/.octaverc template


From: Keith Goodman
Subject: Re: default ~/.octaverc template
Date: Fri, 29 Apr 2005 09:32:48 -0700

> Are you suggesting that Octave should install a default ~/.octaverc
> file for users the first time it runs (presumably only if the file
> does not already exist)?

How does Octave know it is the first time a user has run Octave (does
it look for .octave_hist)? What I'm really trying to ask is if I want
to submit a patch that installs an ~/.octaverc file if none exists,
which function or script should I be looking at?

If the ~/.octaverc template doesn't make it into Octave, I'll submit
it to the sources mailing list. We can point new users to it if they
ask about customizing Octave.

Here's what I have so far:

## Local startup file for Octave. This file is typically used to
## customize the behavior of Octave.
##
## This file should contain any commands that should be executed each
## time Octave starts. The commands in this file take precedence over
## the commands in the system-wide Octave startup file.


## Remove extra blank space around column number labels. The default
## value is 'format loose'.
##
## format compact;

## Output precision (default is 5)
##
## output_precision = 5;

## Do not warn if divide by zero
##
## warn_divide_by_zero = 0;

## Suppress verbose help message.
##
## suppress_verbose_help_message = 1;

## Turn off pagination.
##
## more off;

## Set command-line prompt.
##
## PS1 = ">> ";

## Do not save all current variables to the file "octave-core" if Octave
## crashes or receives a hangup, terminate or similar signal.
##
## crash_dumps_octave_core = 0;

## What is the maximum number of commands the history file should
## contain? The default is 1024.
##
## history_size = 256;

## Octave should try to ring your terminal's bell before printing an error
## message. The default value is to not try.
##
## beep_on_error = 1;

## Do not warn if the name of a function defined in a function file differs
## from the name of the file.
##
## warn_function_name_clash = 0;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]