at 10.40a EDT on 2003 December 16 Tuesday Jan Reichert said:that is the point, it will identify old scripts as subject to convertSlangStrict in chime2jmol.pl
sub convertSlangStrict { my $text= shift; $text=~ s/(\d+)([a-z])(?!\])\b/$1:$2/ig; return $text; }
and if it is an old script, that is no #!rasmol -version 2.7.2.2 header (this use of version parameter has to be implemented in RasMol). Regards, Jan
this ignores Chime scripts, and hand-coded scripts, that do not use a shebang and are around in great numbers.
Regards, Jan
this seems like an awful lot of work to avoid using a carat to indicate insertion codes. why? especially since there are no scripts that currently use them for rasmol, chime, or jmol. so...
why is the carat so unwelcome here? and how often are insertion codes used in pdb files, that it warrants such scripting convolutions to get rid of the carat snytax?
somewhat bewildered,
:tim
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
