|
 |
hi,
William F Pokorny <ano### [at] anonymous org> wrote:
> On 4/14/25 07:47, jr wrote:
> >> ... I loose track of command line settings, camera settinges etc.
> > ... '~/.povray_history', to help with that.
> ...
> As to your particular '?' jr, Something like a ~/.povray_history is
> possible, but does it offer much over the terminal's command history?
> Such a file would be specific to 'povray' and I suppose more persistent?
> The generic, Linux / Unix history capability I do use heavily - to
> render again with the same flags.
I too use the BASH history, but may clear mine between "tasks". and you're
right to question the "suitability" of a file-based approach. perhaps the
command-line could be included when 'all_file=true', instead ?
> (**) - Anything from simple value, vector, string storage (extended
> 'declare' command capabilities) to a new, optional, first parse pass.
> The entire 'first parse' result would be treated as persistent storage.
that's a really good idea, 2-pass parsing, real "benefits" to be had. and with
the speed of modern machines, the user will not even notice. nice.
regards, jr.
Post a reply to this message
|
 |