qutebrowser/qutebrowser

More completions

Open

#32 opened on 2014年10月1日

GitHub で見る
 (25 comments) (12 reactions) (0 assignees)Python (9,161 stars) (1,014 forks)batch import
component: completioncomponent: uigood first issuepriority: 1 - middle

説明

More things should be supported for the completion, for example:

  • URLs (history)
  • Flags for commands
  • Choices for commands
  • Choices for flags with arguments (#1532)
  • Userscript in userscript paths with :spawn --userscript (#1543)
  • Keys for :bind
  • Existing bindings for :unbind
  • Commands for :bind, aliases, etc.
  • Tabs (with a :buffer command)
  • Tabs in current window for :tab-focus
  • Aliased commands
  • Commands after ;;
  • File paths for download, etc. (done for :open via #6038)
  • Closed tabs for :undo
  • back/forward history for :back/:forward (#1561)
  • Search engine names (PR at #2191, after SQL completion)
  • Search engine results/suggestions? - split off to #6049
  • Saving and suggesting prior search terms after specifying a search engine in :open (e.g. after :open -t gmaps new york, the completion after :open -t gmaps would suggest that).
  • Downloads for download-{open,delete,remove,retry}
  • Commands from command history
  • Existing quickmark names when saving a quickmark
  • Elements for list/dict settings
  • Anchors for :scroll-to-anchor
  • Available fonts for font settings
  • Commands and their arguments with :later / :repeat / :run-with-count (see comment below)
  • Arguments for :hint

コントリビューターガイド

技術スタック
python
領域
cli
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
PythonQt basicsqutebrowser internalscommand line parsing
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Explore the qutebrowser source code, particularly the `commands` and `completion` modules, to understand how completions are currently implemented. Pick a specific unchecked item (e.g., 'Flags for commands') and research how to extract available flags from command definitions. Use the existing patterns (e.g., for `:open` and `:buffer`) as reference. Consider existing PRs or comments for additional guidance.