Add some actual sphinx documentation. This is basically the README
split up into sections. Once this is actually published somewhere,
we can remove some of the content from the README and link to an
on-line reference instead.
Change-Id: I25e5ff842e94a5a05aa62c164952df93efc49e98
If a change is opened by id and already exists locally, perform
a high-priority background sync of the change to make sure it's
up to date. This should help avoid the problem where a user
returns to a change in an unsubscribed project and it appears out
of date.
If the change doesn't exist locally, it is synced in the foreground
so that case is already covered.
Change-Id: Idb5daa4309b712e39eb7cde56afcb94fdb41f179
When a foreground sync is happening (because of a search for
a specific change number, including via "gertty --open") display
a message telling the user what's going on.
Change-Id: I4c12c73ec92cba8a8b3f3d69f036d1442323787e
The sync counter up to this point has not counted the currently
running sync task. Keep track of that in a thread-safe way
so the counter is accurate and the user can actually know if the
system is fully synced.
Change-Id: I22a1c5d15c46f3e1785c439e72f8a9e5503d6935
If you run "gertty --open <URL>" it will instruct a running
Gertty to open the change at that URL.
Change-Id: Ie82aa53f497717e7355646d6d6fd12473ececad0
In environments without py27, gertty was unable to run. This patch
addresses all the Py3K issues discovered when getting gertty running in
a py34-only environment.
Change-Id: I32a06f9768bdeaf8e95ddf9a9e54c79059fbaa2f
This way vi users can contribute vi keybindings here and everyone
will be able to benefit. Use "gertty -k vi" or add "keymap: vi"
to the config file.
Change-Id: Iac5db63f8f5394ab874079a6047ddc3a14ec7c22
So that the project list page is more responsive, cache counts of
open and unreviewed changes for projects.
Change-Id: I270f4009d6c7cca9d9868a181db94f779662b643
Due to a math error, comments at the start of the file when outside
of the diff context may have not been displayed. This corrects
the error.
Change-Id: Ic879d3c434faaa5d884547889a602a7157d1b2a8
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I5c3610f0122712f32ac98cc5d859ee9d79e74990
The example for multi-key handling, setting quit to ":q", did not
work because the key buffer clearing at the project screen was
interfering with the key buffering for unhandled input at the top
level. Correct this by only clearing the keybuffer in the project
screen if that screen handled a command. Otherwise, let the
unhandled input handler clear it if necessary.
Change-Id: I104141ceaa87e6178ca74467a55cb7a944ad0128
Commit I0cd0884e0e1f4f0fa82f93e5f7438ff00c5a992aadded support for
sequences of keys input but config file validation was not updated to
reflect the change.
Change-Id: I9c648686737262148a16d3228413da5939677000
Detect the gerrit version on startup and on any reconnection.
When submitting commit message edits, use the change edit API
in 2.11 or greater as the old API has been removed.
Change-Id: Idcba9fc6d424311658b0470410c820015bac9590
Add a simple interactive search to the diff view. This is bound
to C-s by default. It highlights text, but does not yet navigate.
Change-Id: Ic795bb5d18911590237b6595f812e10fd4baa1ce
Create a global app kill ring and a custom edit widget that can
kill and yank from it. Also, add Emacs beginning/end of line
keys to the default keymap.
Change-Id: I18d8d47694c89ede4dcec7eaf5d3fb2210ef4438
Exherbo has a setup where gerrit is at
https://galileo.mailstation.de/gerrit/ and jenkins is at
https://galileo.mailstation.de/jenkins/. gertty falsely thinks that the
jenkins link is a change and when clicked it weirdly starts to sync
random projects for 10 minutes before telling me that the change is not
found. This patch fixes it by matching on the full url.
Change-Id: I4261fce74d6cfaec736e478747592b001d82400d
Being able to refine a search query is useful, but so is being able
to quickly open a specific change from anywhere. Separate these
commands. C-o opens a blank search input; M-o opens a search input
pre-filled with th ecurrent query in list view.
Change-Id: I49d0f076354322a2652de515d476548926a99182
If a change has comments on a file that is not in a patchset,
Gertty will fail to sync the change because local db entries for
files are only created if the file is actually in the revision.
If a comment appears for an unknown file, create an entry in
the db for that file. Note, this will cause the change to appear
in "file:" queries that match that file. It's not clear to me
that is incorrect.
Change-Id: I4916b85a5cbd72ced6682448b774752f3f6cc821
The addition of the ability to review multiple changes at once from the
change_list view duplicates the reverse_order keybinding. They both use
'r'.
Change the reverse_order binding to 'R'.
See, https://storyboard.openstack.org/#!/story/2000290
Change-Id: I3728948a55060ff9f1bd28352474fc4479e68ab9
This change allows a user to click the permalink on the review screen
and have it open up in a web browser.
Change-Id: I4c0fe35f062043a47368d68fecbbcdbf8d955267
James E. Blair