364
edits
Projects: Difference between revisions
Prefernces
(→Packaging: configure/make flags) |
(Prefernces) |
||
| Line 320: | Line 320: | ||
* make pkg support more than one src directory | * make pkg support more than one src directory | ||
* make pkg able to supply extra configure and make flags, useful for distributions, including -j for make | * make pkg able to supply extra configure and make flags, useful for distributions, including -j for make | ||
=Preferences= | |||
Octave has several functions for managing user preferences. Many function use persistent variables instead of relying upon the preference features. | |||
* The function {{Codeline|edit ()}} contains a persistent structure used as its personal set of preferences. These can all be moved to the user preference group for the editor. | |||
** "EDITOR" | |||
** "HOME" | |||
** "AUTHOR" | |||
** "EMAIL" | |||
** "LICENSE" | |||
** "MODE" | |||
** "EDITINPLACE" | |||
* The {{Codeline|savepath ()}} function modifies the startup script (rcfile), {{Codeline|~/.octaverc}} and inserts commands to allow the next session to begin with the same path. Instead user preference can be created for startup items and a preference for the user specified path can be added. Perhaps two path preferences should be used. One for the elements that should precede the core path and those that should follow. A start up directory preference might also be added to allow the user to specify where Octave should begin the next session. | |||
** "PREPATH" | |||
** "POSTPATH" | |||
** "STARTUPDIR" | |||
* Searching the m-files for use of {{Codeline|persistent}} should turn up other opportunities to use preferences. | |||
=Always= | =Always= | ||
*Squash bugs. | *Squash bugs. | ||