Opened 5 months ago

Closed 5 months ago

#17692 closed defect (wontfix)

Cmd history lost with two instances

Reported by: Roden Deng Luo Owned by: Eric Pettersen
Priority: normal Milestone:
Component: Command Line Version:
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description 

Hi, Minor and probably edge case. When two ChimeraX instances are open and
operating for a while, after closing both of them, some cmd history is
certainly lost. I noticed it while developing two bundles at roughly the
same time. (I also had this problem in some shell terminal histories
though.)

Roden

-- 

This message and its contents, including attachments are intended solely 
for the original recipient. If you are not the intended recipient or have 
received this message in error, please notify me immediately and delete 
this message from your computer system. Any unauthorized use or 
distribution is prohibited. Please consider the environment before printing 
this email.

Change History (2)

comment:1 by Eric Pettersen, 5 months ago

Component: Unassigned → Command Line
Owner: set to Eric Pettersen
Platform: → all
Project: → ChimeraX
Status: new → accepted

comment:2 by Eric Pettersen, 5 months ago

Resolution: → wontfix
Status: accepted → closed

Each instance of ChimeraX is writing out its own command history as each command is executed in that instance. The last one to execute a command "wins" the command-history war. To try to interleave the two command histories (or even more ambitiously have each instance's history update with commands from the other) would be a large amount of work for dubious benefit since the command line isn't even writing the command history itself -- it's using a chimera.core.history.FIFOHistory object to handle that.

Note: See TracTickets for help on using tickets.