{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/432", "result": {"data":{"issuesJson":{"id":"8f9d8042-0ebf-5a0d-adf6-9a4df8896b81","title":"peco/peco: 简单的交互式过滤工具。","number":432,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Repospeco/peco
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

peco

\n

Simplistic interactive filtering tool

\n

NOTE: If you are viewing this on GitHub, this document refers to the state of peco in whatever current branch you are viewing, not necessarily the state of a currently released version. Please make sure to checkout the Changes file for features and changes.

\n

This README is long and comprehensive. Use the Table of Contents to navigate to the section that interests you. It has been placed at the bottom of the README file because of its length.

\n
\n

If you use peco, please consider sponsoring the authors of this project from the \"Sponsor\" button on the project page at https://github.com/peco/peco. Sponsorship plans start at $1 :)

\n
\n

Description

\n

peco (pronounced peh-koh) is based on a python tool, percol. percol was darn useful, but I wanted a tool that was a single binary, and forget about python. peco is written in Go, and therefore you can just grab the binary releases and drop it in your $PATH.

\n

peco can be a great tool to filter stuff like logs, process stats, find files, because unlike grep, you can type as you think and look through the current results.

\n

For basic usage, continue down below. For more cool elaborate usage samples, please see the wiki, and if you have any other tricks you want to share, please add to it!

\n

Demo

\n

Demos speak more than a thousand words! Here's me looking for a process on my mac. As you can see, you can page through your results, and you can keep changing the query:

\n

\"Executed

\n

Here's me trying to figure out which file to open:

\n

\"Executed

\n

When you combine tools like zsh, peco, and ghq, you can make managing/moving around your huge dev area a piece of cake! (this example doesn't use zsh functions so you can see what I'm doing)

\n

\"Executed

\n

Features

\n

Incremental Search

\n

Search results are filtered as you type. This is great to drill down to the
\nline you are looking for

\n

Multiple terms turn the query into an \"AND\" query:

\n

\"Executed

\n

When you find that line that you want, press enter, and the resulting line
\nis printed to stdout, which allows you to pipe it to other tools

\n

Select Multiple Lines

\n

You can select multiple lines! (this example uses C-Space)

\n

\"Executed

\n

Select Range Of Lines

\n

Not only can you select multiple lines one by one, you can select a range of lines (Note: The ToggleRangeMode action is not enabled by default. You need to put a custom key binding in your config file)

\n

\"Executed

\n

Select Filters

\n

Different types of filters are available. Default is case-insensitive filter, so lines with any case will match. You can toggle between IgnoreCase, CaseSensitive, SmartCase, Regexp and Fuzzy filters.

\n

The SmartCase filter uses case-insensitive matching when all of the queries are lower case, and case-sensitive matching otherwise.

\n

The Regexp filter allows you to use any valid regular expression to match lines.

\n

The Fuzzy filter allows you to find matches using partial patterns. For example, when searching for ALongString, you can enable the Fuzzy filter and search ALS to find it. The Fuzzy filter uses smart case search like the SmartCase filter. With the FuzzyLongestSort flag enabled in the configuration file, it does a smarter match. It sorts the matched lines by the following precedence: 1. longer substring, 2. earlier (left positioned) substring, and 3. shorter line.

\n

\"Executed

\n

Selectable Layout

\n

As of v0.2.5, if you would rather not move your eyes off of the bottom of the screen, you can change the screen layout by either providing the --layout=bottom-up command line option, or set the Layout variable in your configuration file

\n

\"Executed

\n

Works on Windows!

\n

I have been told that peco even works on windows :) Look ma! I'm not lying!

\n

\"Showing

\n

Installation

\n

Just want the binary?

\n

Go to the releases page, find the version you want, and download the zip file. Unpack the zip file, and put the binary to somewhere you want (on UNIX-y systems, /usr/local/bin or the like). Make sure it has execution bits turned on. Yes, it is a single binary! You can put it anywhere you want :)

\n

THIS IS THE RECOMMENDED WAY (except for macOS homebrew users)

\n

macOS (Homebrew, Scarf)

\n

If you're on macOS and want to use homebrew:

\n
brew install peco\n
\n

or with Scarf:

\n
scarf install peco\n
\n

Debian and Ubuntu based distributions (APT, Scarf)

\n

There is an official Debian package that can be installed via APT:

\n
apt install peco\n
\n

or with Scarf:

\n
scarf install peco\n
\n

Void Linux (XBPS)

\n
xbps-install -S peco\n
\n

Arch Linux

\n

There is an official Arch Linux package that can be installed via pacman:

\n
pacman -Syu peco\n
\n

Windows (Chocolatey NuGet Users)

\n

There's a third-party peco package available for Chocolatey NuGet.

\n
C:\\> choco install peco\n
\n

Building peco yourself

\n

Make sure to clone the source code under $GOPATH (i.e. $GOPATH/src/github.com/peco/peco). This is required
\nas the main binary refers to an internal package, which requires that the source code be located in
\nthe correct package location.

\n

Navigate to the directory above, then run:

\n
make build\n
\n

This will do the following:

\n
    \n
  1. Run go build to create releases/$VERSION_NUMBER/peco
    2. \n
\n

You can copy the binary to somewhere in your $PATH, and it should just work.

\n

The above installs the correct versions of peco's dependencies. Then build it:

\n
go build cmd/peco/peco.go\n
\n

This compiles a peco binary in the root of the cloned peco repository. Copy this file to an appropriate location.

\n

go get IS NOT RECOMMENDED

\n

Please DO NOT use go get to install this tool. It bypasses the developers' intention of controlling the dependency versioning.

\n

Command Line Options

\n

-h, --help

\n

Display a help message

\n

--version

\n

Display the version of peco

\n

--query

\n

Specifies the default query to be used upon startup. This is useful for scripts and functions where you can figure out beforehand what the most likely query string is.

\n

--print-query

\n

When exiting, prints out the query typed by the user as the first line of output. The query will be printed even if there are no matches, if the program is terminated normally (i.e. enter key). On the other hand, the query will NOT be printed if the user exits via a cancel (i.e. esc key).

\n

--rcfile

\n

Pass peco a configuration file, which currently must be a JSON file. If unspecified it will try a series of files by default. See Configuration File for the actual locations searched.

\n

-b, --buffer-size

\n

Limits the buffer size to num. This is an important feature when you are using peco against a possibly infinite stream, as it limits the number of lines that peco holds at any given time, preventing it from exhausting all the memory. By default the buffer size is unlimited.

\n

--null

\n

WARNING: EXPERIMENTAL. This feature will probably stay, but the option name may change in the future.

\n

Changes how peco interprets incoming data. When this flag is set, you may insert NUL ('\\0') characters in your input. Anything before the NUL character is treated as the string to be displayed by peco and is used for matching against user query. Anything after the NUL character is used as the \"result\": i.e., when peco is about to exit, it displays this string instead of the original string displayed.

\n

Here's a simple example of how to use this feature

\n

--initial-index

\n

Specifies the initial line position upon start up. E.g. If you want to start out with the second line selected, set it to \"1\" (because the index is 0 based).

\n

--initial-filter IgnoreCase|CaseSensitive|SmartCase|Regexp|Fuzzy

\n

Specifies the initial filter to use upon start up. You should specify the name of the filter like IgnoreCase, CaseSensitive, SmartCase, Regexp and Fuzzy. Default is IgnoreCase.

\n

--prompt

\n

Specifies the query line's prompt string. When specified, takes precedence over the configuration file's Prompt section. The default value is QUERY>.

\n

--layout top-down|bottom-up

\n

Specifies the display layout. Default is top-down, where query prompt is at the top, followed by the list, then the system status message line. bottom-up changes this to the list first (displayed in reverse order), the query prompt, and then the system status message line.

\n

For percol users, --layout=bottom-up is almost equivalent of --prompt-bottom --result-bottom-up.

\n

--select-1

\n

When specified and the input contains exactly 1 line, peco skips prompting you for a choice, and selects the only line in the input and immediately exits.

\n

If there are multiple lines in the input, the usual selection view is displayed.

\n

--on-cancel success|error

\n

Specifies the exit status to use when the user cancels the query execution.
\nFor historical and back-compatibility reasons, the default is success, meaning if the user cancels the query, the exit status is 0. When you choose error, peco will exit with a non-zero value.

\n

--selection-prefix string

\n

When specified, peco uses the specified prefix instead of changing line color to indicate currently selected line(s). default is to use colors. This option is experimental.

\n

--exec string

\n

When specified, peco executes the specified external command (via shell), with peco's currently selected line(s) as its input from STDIN.

\n

Upon exiting from the external command, the control goes back to peco where you can keep browsing your search buffer, and to possibly execute your external command repeatedly afterwards.

\n

To exit out of peco when running in this mode, you must execute the Cancel command, usually the escape key.

\n

Configuration File

\n

peco by default consults a few locations for the config files.

\n
    \n
  1. Location specified in --rcfile. If this doesn't exist, peco complains and exits
    2. \n
  2. $XDG_CONFIG_HOME/peco/config.json
    3. \n
  3. $HOME/.config/peco/config.json
    4. \n
  4. for each directory listed in $XDG_CONFIG_DIRS, $DIR/peco/config.json
    5. \n
  5. If all else fails, $HOME/.peco/config.json
    6. \n
\n

Below are configuration sections that you may specify in your config file:

\n\n

Global

\n

Global configurations that change the global behavior.

\n

Prompt

\n

You can change the query line's prompt, which is QUERY> by default.

\n
{\n    \"Prompt\": \"[peco]\"\n}
\n

InitialMatcher

\n

InitialMatcher has been deprecated. Please use InitialFilter instead.

\n

InitialFilter

\n

Specifies the filter name to start peco with. You should specify the name of the filter, such as IgnoreCase, CaseSensitive, SmartCase, Regexp and Fuzzy.

\n

FuzzyLongestSort

\n

Enables the longest substring match and sorts the output. It affects only the Fuzzy filter.

\n

Default value for FuzzyLongestSort is false.

\n

StickySelection

\n
{\n    \"StickySelection\": true\n}
\n

StickySelection allows selections to persist even between changes to the query.
\nFor example, when you set this to true you can select a few lines, type in a
\nnew query, select those lines, and then delete the query. The result is all
\nthe lines that you selected before and after the modification to the query are
\nleft intact.

\n

Default value for StickySelection is false.

\n

OnCancel

\n
{\n    \"OnCancel\": \"error\"\n}
\n

OnCancel is equivalent to --on-cancel command line option.

\n

MaxScanBufferSize

\n
{\n    \"MaxScanBufferSize\": 256\n}
\n

Controls the buffer sized (in kilobytes) used by bufio.Scanner, which is
\nresponsible for reading the input lines. If you believe that your input has
\nvery long lines that prohibit peco from reading them, try increasing this number.

\n

The same time, the default MaxScanBuferSize is 256kb.

\n

Keymaps

\n

Example:

\n
{\n    \"Keymap\": {\n        \"M-v\": \"peco.ScrollPageUp\",\n        \"C-v\": \"peco.ScrollPageDown\",\n        \"C-x,C-c\": \"peco.Cancel\"\n    }\n}
\n

Key sequences

\n

As of v0.2.0, you can use a list of keys (separated by comma) to register an action that is associated with a key sequence (instead of a single key). Please note that if there is a conflict in the key map, the longest sequence always wins. So In the above example, if you add another sequence, say, C-x,C-c,C-c, then the above peco.Cancel will never be invoked.

\n

Combined actions

\n

As of v0.2.1, you can create custom combined actions. For example, if you find yourself repeatedly needing to select 4 lines out of the list, you may want to define your own action like this:

\n
{\n    \"Action\": {\n        \"foo.SelectFour\": [\n            \"peco.ToggleRangeMode\",\n            \"peco.SelectDown\",\n            \"peco.SelectDown\",\n            \"peco.SelectDown\",\n            \"peco.ToggleRangeMode\"\n        ]\n    },\n    \"Keymap\": {\n        \"M-f\": \"foo.SelectFour\"\n    }\n}
\n

This creates a new combined action foo.SelectFour (the format of the name is totally arbitrary, I just like to put namespaces), and assigns that action to M-f. When it's fired, it toggles the range selection mode and highlights 4 lines, and then goes back to waiting for your input.

\n

As a similar example, a common idiom in emacs is that C-c C-c means \"take the contents of this buffer and accept it\", whatever that means. This adds exactly that keybinding:

\n
{\n    \"Action\": {\n        \"selectAllAndFinish\": [\n            \"peco.SelectAll\",\n            \"peco.Finish\"\n        ]\n    },\n    \"Keymap\": {\n        \"C-c,C-c\": \"selectAllAndFinish\"\n    }\n}
\n

Available keys

\n

Since v0.1.8, in addition to values below, you may put a M- prefix on any
\nkey item to use Alt/Option key as a mask.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameNotes
C-a ... C-zControl + whatever character
C-2 ... C-8Control + 2..8
C-[
C-]
C-~
C-_
C-\\\\Note that you need to escape the backslash
C-/
C-Space
F1 ... F12
Esc
Tab
Enter
Insert
Delete
BS
BS2
Home
End
Pgup
Pgdn
ArrowUp
ArrowDown
ArrowLeft
ArrowRight
MouseLeft
MouseMiddle
MouseRight
\n

Key workarounds

\n

Some keys just... don't map correctly / too easily for various reasons. Here, we'll list possible workarounds for key sequences that are often asked for:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
You want thisUse this insteadNotes
Shift+TabM-[,ZVerified on macOS
\n

Available actions

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameNotes
peco.ForwardCharMove caret forward 1 character
peco.BackwardCharMove caret backward 1 character
peco.ForwardWordMove caret forward 1 word
peco.BackwardWordMove caret backward 1 word
peco.BackToInitialFilterSwitch to first filter in the list
peco.BeginningOfLineMove caret to the beginning of line
peco.EndOfLineMove caret to the end of line
peco.EndOfFileDelete one character forward, otherwise exit from peco with failure status
peco.DeleteForwardCharDelete one character forward
peco.DeleteBackwardCharDelete one character backward
peco.DeleteForwardWordDelete one word forward
peco.DeleteBackwardWordDelete one word backward
peco.InvertSelectionInverts the selected lines
peco.KillBeginningOfLineDelete the characters under the cursor backward until the beginning of the line
peco.KillEndOfLineDelete the characters under the cursor until the end of the line
peco.DeleteAllDelete all entered characters
peco.RefreshScreenRedraws the screen. Note that this effectively re-runs your query
peco.SelectPreviousPage(DEPRECATED) Alias to ScrollPageUp
peco.SelectNextPage(DEPRECATED) Alias to ScrollPageDown
peco.ScrollPageDownMoves the selected line cursor for an entire page, downwards
peco.ScrollPageUpMoves the selected line cursor for an entire page, upwards
peco.SelectUpMoves the selected line cursor to one line above
peco.SelectDownMoves the selected line cursor to one line below
peco.SelectPrevious(DEPRECATED) Alias to SelectUp
peco.SelectNext(DEPRECATED) Alias to SelectDown
peco.ScrollLeftScrolls the screen to the left
peco.ScrollRightScrolls the screen to the right
peco.ScrollFirstItemScrolls to the first item (in the entire buffer, not the current screen)
peco.ScrollLastItemScrolls to the last item (in the entire buffer, not the current screen)
peco.ToggleSelectionSelects the current line, and saves it
peco.ToggleSelectionAndSelectNextSelects the current line, saves it, and proceeds to the next line
peco.ToggleSingleKeyJumpEnables SingleKeyJump mode a.k.a. \"hit-a-hint\"
peco.SelectNoneRemove all saved selections
peco.SelectAllSelects the all line, and save it
peco.SelectVisibleSelects the all visible line, and save it
peco.ToggleSelectMode(DEPRECATED) Alias to ToggleRangeMode
peco.CancelSelectMode(DEPRECATED) Alias to CancelRangeMode
peco.ToggleQueryToggle list between filtered by query and not filtered.
peco.ToggleRangeModeStart selecting by range, or append selecting range to selections
peco.CancelRangeModeFinish selecting by range and cancel range selection
peco.RotateMatcher(DEPRECATED) Use peco.RotateFilter
peco.RotateFilterRotate between filters (by default, ignore-case/no-ignore-case)
peco.FinishExits from peco with success status
peco.CancelExits from peco with failure status, or cancel select mode
\n

Default Keymap

\n

Note: If in case below keymap seems wrong, check the source code in keymap.go (look for NewKeymap).

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
KeyAction
Escpeco.Cancel
C-cpeco.Cancel
Enterpeco.Finish
C-fpeco.ForwardChar
C-apeco.BeginningOfLine
C-bpeco.BackwardChar
C-dpeco.DeleteForwardChar
C-epeco.EndOfLine
C-kpeco.KillEndOfLine
C-upeco.KillBeginningOfLine
BSpeco.DeleteBackwardChar
C-8peco.DeleteBackwardChar
C-wpeco.DeleteBackwardWord
C-gpeco.SelectNone
C-npeco.SelectDown
C-ppeco.SelectUp
C-rpeco.RotateFilter
C-tpeco.ToggleQuery
C-Spacepeco.ToggleSelectionAndSelectNext
ArrowUppeco.SelectUp
ArrowDownpeco.SelectDown
ArrowLeftpeco.ScrollPageUp
ArrowRightpeco.ScrollPageDown
\n

Styles

\n

For now, styles of following 5 items can be customized in config.json.

\n
{\n    \"Style\": {\n        \"Basic\": [\"on_default\", \"default\"],\n        \"SavedSelection\": [\"bold\", \"on_yellow\", \"white\"],\n        \"Selected\": [\"underline\", \"on_cyan\", \"black\"],\n        \"Query\": [\"yellow\", \"bold\"],\n        \"Matched\": [\"red\", \"on_blue\"]\n    }\n}
\n\n

Foreground Colors

\n\n

Background Colors

\n\n

Attributes

\n\n

CustomFilter

\n

This is an experimental feature. Please note that some details of this specification may change

\n

By default peco comes with IgnoreCase, CaseSensitive, SmartCase, Regexp and Fuzzy filters, but since v0.1.3, it is possible to create your own custom filter.

\n

The filter will be executed via Command.Run() as an external process, and it will be passed the query values in the command line, and the original unaltered buffer is passed via os.Stdin. Your filter must perform the matching, and print out to os.Stdout matched lines. Your filter MAY be called multiple times if the buffer
\ngiven to peco is big enough. See BufferThreshold below.

\n

Note that currently there is no way for the custom filter to specify where in the line the match occurred, so matched portions in the string WILL NOT BE HIGHLIGHTED.

\n

The filter does not need to be a go program. It can be a perl/ruby/python/bash script, or anything else that is executable.

\n

Once you have a filter, you must specify how the matcher is spawned:

\n
{\n    \"CustomFilter\": {\n        \"MyFilter\": {\n            \"Cmd\": \"/path/to/my-matcher\",\n            \"Args\": [ \"$QUERY\" ],\n            \"BufferThreshold\": 100\n        }\n    }\n}
\n

Cmd specifies the command name. This must be searchable via exec.LookPath.

\n

Elements in the Args section are string keys to array of program arguments. The special token $QUERY will be replaced with the unaltered query as the user typed in (i.e. multiple-word queries will be passed as a single string). You may pass in any other arguments in this array. If you omit this in your config, a default value of []string{\"$QUERY\"} will be used

\n

BufferThreshold specifies that the filter command should be invoked when peco has this many lines to process
\nin the buffer. For example, if you are using peco against a 1000-line input, and your BufferThreshold is 100 (which is the default), then your filter will be invoked 10 times. For obvious reasons, the larger this threshold is, the faster the overall performance will be, but the longer you will have to wait to see the filter results.

\n

You may specify as many filters as you like in the CustomFilter section.

\n

Examples

\n\n

Layout

\n

See --layout.

\n

SingleKeyJump

\n
{\n  \"SingleKeyJump\": {\n    \"ShowPrefix\": true\n  }\n}\n
\n

SelectionPrefix

\n

SelectionPrefix is equivalent to using --selection-prefix in the command line.

\n
{\n  \"SelectionPrefix\": \">\"\n}\n
\n

Use256Color

\n

Boolean value that determines whether or not to use 256color. The default is false.

\n

Note: This has no effect on Windows because Windows console does not support extra color modes.

\n
{\n    \"Use256Color\": true\n}
\n

FAQ

\n

Does peco work on (msys2|cygwin)?

\n

No. peco/peco#336 (comment)
\n(Updated Feb 23, 2017: \"Maybe\" on cygwin peco/peco#336 (comment))

\n

Non-latin fonts (e.g. Japanese) look weird on my Windows machine...?

\n

Are you using raster fonts? peco/peco#341

\n

Seeing escape sequences [200~ and [201~ when pasting text?

\n

Disable bracketed paste mode. peco/peco#417

\n

Hacking

\n

First, fork this repo, and get your clone locally.

\n
    \n
  1. Make sure you have go installed, with GOPATH appropriately set
    2. \n
  2. Make sure you have make installed
    3. \n
  3. Run make installdeps (You only need to do this once)
    4. \n
\n

To test, run

\n
make test\n
\n

To build, run

\n
make build\n
\n

This will create a peco binary in $(RELEASE_DIR)/peco_$(GOOS)_$(GOARCH)/peco$(SUFFIX). Or, of course, you can just run

\n
go build cmd/peco/peco.go\n
\n

which will create the binary in the local directory.

\n

TODO

\n

Unit test it.

\n

AUTHORS

\n\n

CONTRIBUTORS

\n\n

Notes

\n

Obviously, kudos to the original percol: https://github.com/mooz/percol
\nMuch code stolen from https://github.com/mattn/gof

\n

Table of Contents

\n\n\n\n","updatedAt":"2025-05-21T16:15:32Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"命令行工具","color":"e05879"}},{"node":{"name":"peco","color":"40f4ef"}}]},"comments":{"edges":[]}}},"pageContext":{"number":432,"previous":{"title":"PowerDNS/pdns: PowerDNS 权威、PowerDNS 递归、dnsdist","number":431},"next":{"title":"brendangregg/perf-tools: Linux 性能分析工具集合","number":433}}}, "staticQueryHashes": ["151096407","2861350382"]}