On Mon, Oct 20, 2014 at 12:37 PM, go <[email protected]> wrote:
> 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.
>
>
OK, I understand now. It seems to me the easy way to do this would be to
just allow a more obvious mechanism to save the history to a file of the
user's choice and then restore it into the Script Editor (rather than the
console). Then you should be able to run any given command or block of
commands from that at will. And you see them all in front of you. I have
not done much with the Script Editor myself, and I think actually maybe it
is not very useful. But it could be useful, and it is way better than a
simple single-line option. Certainly it should be possible to implement
PAGE UP the way you describe also. I will look into it.
------------------------------------------------------------------------------
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
