Re: Should "set ..." trigger a replot event?

[Karl R. <ra...@un...>]

Am 28.11.2014 um 18:31 schrieb Philipp K. Janert:
> Should changing an option with "set ..." automatically
> replot the graph?
> 
> Traditionally, changing an option with "set ..." does 
> not have any immediate visible consequences - not until
> the next plot, splot, or replot (or refresh) event do
> the changes become visible.
> 
> This is a major point of confusion for new users, and
> frequently an annoyance even for experienced users.
> 
> Hence, would it make sense to re-draw the graph 
> automatically after "set"? Or (better!) have an
> internal variable/option (eg "set autorefresh") 
> that controls this behavior?
> 
> Obviously, for batch processing, autorefresh does
> not make sense. Also, a previous plot must exist.
> 
> So, here is the list of conditions that I could foresee:
> 
> 1) IF the terminal is an interactive terminal
> 2) and if a previous plot exist in the history
> 3) and if autorefresh is not False
> THEN automatically run refresh after each set.
> 
> Thoughts?

I could see an "autorefresh" mode would be nice to have in some cases,
but if it was the default, I´m sure it´d annoy me on a daily basis.

Btw., you can always end your "set .." command with ";rep" ;-)

(What the heck is the ambiguous "re" supposed to do? It´s neither
"replot" or "refresh", nor "reset". Is it "reread"?)

  Karl