|
From: Ethan M. <merritt@u.washington.edu> - 2005-07-27 16:19:06
|
On Wednesday 27 July 2005 02:05 am, Petr Mikulik wrote:
> > Several disambiguating keywords have been added already (e.g. "font",
> > "offset", "at") for exactly this reason. Do you know of any other cases
> > that are violators, like ... notitle "title"?
>
> set label {<tag>} {"<label text>"}
That is unambiguous, since <tag> cannot be a string, and "<label text>"
cannot be a number. The existing code correctly handles this.
> set timestamp {"<format>"} ... {"<font>"}
OK. There's a case I missed when adding the disambiguating keyword "font".
I'll fix that. The "set timestamp" command is also an example of the
documentation lagging the code by not mentioning the keyword "offset".
> set title {"<title-text>"}
> set xlabel {"<label>"}
What is ambiguous in these commands?
--
Ethan A Merritt merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195
|