Opened 10 years ago

Closed 10 years ago

#215 closed defect (fixed)

multi-word selector parsing

Reported by: Eric Pettersen Owned by: Conrad Huang
Priority: blocker Milestone:
Component: Command Line Version:
Keywords: Cc: gregc@…, meng@…
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

I thought there would be no problem with multi-word selectors due to atom spec's "greediness", but the newly implemented "nucleic acid" selector gets rejected with: Expected objects or a keyword

My belief is that multi-word selectors should work, just as they do in Chimera 1.

Change History (2)

comment:1 by Eric Pettersen, 10 years ago

You know, I'd be perfectly willing to _not_ support multi-word selectors with spaces, if multi-word selectors with hyphens worked. They don't work either.

--Eric

comment:2 by Conrad Huang, 10 years ago

Resolution: → fixed
Status: new → closed

Previous requirement for selector names is that they be legal Python identifiers. Changed so that selectors must (a) start with an alphabetic character, and (b) be followed by any number of alphanumeric or hyphen characters. Underscore was made illegal to avoid having some names using hyphens while others use underscores.

Trying to register an illegal selector name now results in a ValueError exception.

Note: See TracTickets for help on using tickets.