Dear Bob,
While I do appreciate the option of saving state very much,
system state and command history are ORTHOGONAL CONCEPTS.
I did not mean to use the command history to restore the state of Jmol.
As Jmol is really a programming language, I suggested to improve
its command line functionality. You already do a lot about this,
tab-completion and syntax checking are both in this category.
With a wealth of commands/command options, the user's previously
typed commands (that were often found not easily) are of real value.
It would be nice if these could be recalled from previous sessions.
I still think that this would be a simple and straightforward
improvement.
Maybe somewhat more difficult to implement, but here is another useful
feature.
Recall a command not one-by-one, but based on the letters already typed
+ PAGE UP.
Both these command line functionalities are present
in many REPL-based languages and both are heavily utilized.
Please reconsider the original suggestion from this viewpoint.
This is not a critique of the current state of Jmol,
rather a useful and realistic suggestion, offered by good will.
Best regards,
Gabor Oszlanyi
On 2014-10-20 00:24, Robert Hanson wrote:
> The rote recall of commands from a history is possible in Jmol, but it
> is not recommended. (See SHOW HISTORY and WRITE HIS.)
>
> Rather, we save the "state" of the system. This is also a Jmol script,
> but it is not a history. It reproduces the state exactly as you left
> it, far more efficiently than a history. See SHOW STATE and WRITE SPT
>
> Bob Hanson
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
