20180321 BER Add a redraw function/key, usually Control-L is used.
    If the screen gets disorted, e.g. by a background process spilling
    some stuff on stderror, you want a completely redrawn screen without
    restarting getan.

20180214 Magnus Schieder
  Reproduced with getan2.1 and getan2.3dev1

  4) Switch to the entries from the project pro2 with tab.
  5) Mark with return and arrow keys ent7 and ent8.
  6) Press m, then 3 and then y to move ent7 and ent8.
  7) Go back to the projects with tab.

  Expectation:
    The focus is on pro2.
    The entries of pro2 are displayed.

  Result:
    The focus is on pro1.
    The entries of pro2 are displayed (ent9)


20180214 Magnus Schieder
  Reproduced with getan2.1 and getan2.3dev1

  4) Switch to the entries from the project pro1 with tab.
  5) Mark with return and arrow keys ent1, ent2, ent3, ent4 and ent5.
  6) Delete the mark of ent3.
  7) Press m, then 3 and then y to move ent1, ent2, ent4 and ent5.

  Expectation:
    ent1, ent2, ent4 and ent5 are moved to.

  Result:
    ent1, ent2, ent3 and ent4 were moved to pro3.
    ent5 stays in pro1.
    (The last marked entry stays in its project)


20180118 BER There should be an indication which entries are shown
    when being in the right pane. When you use tab to go to the entries,
    it cannot be seen anymore in which project I am.
    This is a larger drawback after moving all entries somewhere,
    it is unclear which task's entries are shown now.

20180117 Magnus Schieder

  20170317 BER: Reproduce and then fix a defect that it is surprising which
  entries are moved by `m` or deleted by 'd'.
  It probably has to do how multi-selection are handled. Maybe they
  are not cleared properly at the end of an operation.
  One description: It happens when you have changed a lot of entries
  from different projects (I assume), e.g. by editing the description,
  the length or timedate and then use move where you intend to only move
  one, the unwanted result is several moved entries.

  reproduced with getan 2.1
  20180118BER Reproduced with urwid v1.3.0, python3.4.6, getan 2.2.dev1 r445

  Creating a new database with test data:

  1) Delete getan_test_data.db if it already exists to create a new database.
  2) Execute getan_test_data.py to get the test database getan_test_data.db.
     (getan/test_data/getan_test_data.py)

- Bug 1.0
  2) Open getan with the test database. (getan /path/getan_test_data.db)
  3) Switch to the entries from the project pro1 with tab.
  4) Mark with return and arrow keys ent1 and ent2.
  5) Go back to the projects with tab.

  20180118BER:
    Observation: ent1 and ent2 are not highlighted anymore.

  6) Switch back to the entries of project pro1.
  7) Mark this time ent3 and ent4.
  8) Press m, then 3 and then y to move ent3 and ent4 to pro3.

  Expectation:
    ent3 and ent4 are moved to pro3.

  Result:
    ent1, ent2, ent3 and ent4 were moved to pro3.

- Bug 1.1
  Execute 1) to 7) from 1.0.
  8) Press d to delete ent3 and ent4.

  Expectation:
      ent3 and ent4 are deleted.

  Result:
    ent1, en2, ent3 and ent4 are deleted.