[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5554":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":38,"readmeContent":39,"aiSummary":40,"trendingCount":15,"starSnapshotCount":15,"syncStatus":41,"lastSyncTime":42,"discoverSource":43},5554,"tailspin","bensadeh\u002Ftailspin","bensadeh","🌀 A log file highlighter","",null,"Rust",7859,135,19,0,1,6,33,4,70.7,"MIT License",false,"main",[25,26,27,28,29,30,31,32,33,34,35,36,37],"ccze","colorizer","colors","file","follow","grc","highlighter","less","log","log-file","logfile","syntax-highlighting","tail","2026-06-12 04:00:25","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Ftailspin.png\" width=\"230\"\u002F>\n\u003C\u002Fp>\n\n#                                                                                                                                                                                                                                                                                                                                                                  \n\n\u003Cp align=\"center\">\nA log file highlighter\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fmain.png\" width=\"700\"\u002F>\n\u003C\u002Fp>\n\n### Features\n\n- 🪵 View (or `tail`) any log file of any format\n- 🍰 No setup or config required\n- 🌈 Highlights numbers, dates, IP-addresses, UUIDs, URLs and more\n- ⚙️ All highlight groups are customizable\n- 🧬 Easy to integrate with other commands\n- 📦 Also available as a [crate](https:\u002F\u002Fdocs.rs\u002Ftailspin)\n\n#\n\n### Table of Contents\n\n* [Overview](#overview)\n* [Usage](#usage)\n* [Installing](#installing)\n* [Highlight Groups](#highlight-groups)\n* [Customizing Highlight Groups](#customizing-highlight-groups)\n* [Working with `stdin` and `stdout`](#working-with-stdin-and-stdout)\n* [Using the pager `less`](#using-the-pager-less)\n* [Settings](#settings)\n\n***\n\n## Overview\n\n`tailspin` works by reading through a log file line by line, running a series of matchers\nagainst each line. The matchers recognize patterns you expect to find in a logfile, like dates, numbers, severity\nkeywords and more.\n\n`tailspin` does not make any assumptions on the format or position of the items it wants to highlight. For this reason,\nit requires no configuration and the highlighting will work consistently across different logfiles.\n\n## Usage\n\nThe binary name for `tailspin` is `tspin`.\n\n```console\n# Read from file and view in `less`\ntspin application.log\n\n# Pipe something into `tspin` and print to stdout\necho \"hello null\" | tspin\n\n# Read from stdin and print to stdout\nkubectl logs [pod_name] --follow | tspin\n\n# Run the provided command and view the output in `less`\ntspin --exec='kubectl logs -f pod_name'\n``` \n\n## Installing\n\n\u003Cdetails>\n\u003Csummary>Expand to view\u003C\u002Fsummary>\n\n### Package Managers\n\n```console\n# Homebrew\nbrew install tailspin\n\n# Cargo\ncargo install tailspin\n\n# Archlinux\npacman -S tailspin\n\n# Nix\nnix-shell -p tailspin\n\n# NetBSD\npkgin install tailspin\n\n# FreeBSD\npkg install tailspin\n\n# Windows\nscoop install tailspin\n```\n\n### From Source\n\n```console\ncargo install --path .\n```\n\nBinary will be placed in `~\u002F.cargo\u002Fbin`, make sure you add the folder to your `PATH` environment variable.\n\n> [!IMPORTANT]\n> When building from source, make sure that you are using the latest version\n> of [`less`](http:\u002F\u002Fgreenwoodsoftware.com\u002Fless\u002F).\n\n\u003C\u002Fdetails>\n\n## Highlight Groups\n\n### Defaults\n\nThe following highlight groups are enabled by default and can be toggled with `--enable` and `--disable`:\n\n#### Dates\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fdates.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Keywords\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fkeywords.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### URLs\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Furls.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Numbers\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fnumbers.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### IPv4 Addresses\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fip.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Quotes\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fquotes.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Unix file paths\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fpaths.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### HTTP methods\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fhttp.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### UUIDs\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fuuids.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Key-value pairs\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fkv.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Pointer addresses\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fpointers.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n#### Unix processes\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fprocesses.png\" width=\"600\"\u002F>\n\u003C\u002Fp>\n\n### Extras\n\nExtras are highlight groups that are not enabled by default. They can be enabled with the `--extras` flag and are\nalways additive — they apply on top of whatever defaults or `--enable`\u002F`--disable` configuration is active.\n\n```console\n# Enable IPv6 highlighting in addition to the defaults\ntspin application.log --extras ipv6\n\n# Combine with --enable\ntspin application.log --enable urls,numbers --extras ipv6\n```\n\nAvailable extras:\n\n| Name                | Description                                            |\n|---------------------|--------------------------------------------------------|\n| `ipv6`              | Highlight IPv6 addresses                               |\n| `jvm-stack-trace`   | Highlight JVM stack traces (Java, Kotlin, Scala, etc.) |\n\nTo enable extras by default without passing the flag every time, set the `TAILSPIN_EXTRAS` environment variable\n(comma-separated):\n\n```console\nexport TAILSPIN_EXTRAS=jvm-stack-trace\n```\n\n## Customizing Highlight Groups\n\n### Overview\n\nCreate a `theme.toml` in `~\u002F.config\u002Ftailspin` to customize highlight groups.\n\nStyles have the following shape:\n\n```toml\nstyle = { fg = \"color\", bg = \"color\", italic = false, bold = false, underline = false }\n```\n\nTo edit the different highlight groups, include them in your `theme.toml` file. For example, to edit the `date`\nhighlight group, add the following to your `theme.toml`:\n\n```toml\n[dates]\ndate = { fg = \"green\" }\n```\n\nExpand the section below to see the default config for the highlight groups:\n\n\u003Cdetails>\n\u003Csummary>Default highlight groups settings\u003C\u002Fsummary>\n\n```toml\n[dates]\ndate = { fg = \"magenta\" }\ntime = { fg = \"blue\" }\nzone = { fg = \"red\" }\nseparator = { faint = true }\n\n[[keywords]]\nwords = ['null', 'true', 'false']\nstyle = { fg = \"red\", italic = true }\n\n[[keywords]]\nwords = ['GET']\nstyle = { fg = \"black\", bg = \"green\" }\n\n[urls]\nhttp = { fg = \"red\", faint = true }\nhttps = { fg = \"green\", faint = true }\nhost = { fg = \"blue\", faint = true }\npath = { fg = \"blue\" }\nquery_params_key = { fg = \"magenta\" }\nquery_params_value = { fg = \"cyan\" }\nsymbols = { fg = \"red\" }\n\n[numbers]\nnumber = { fg = \"cyan\" }\n\n[ip_addresses]\nnumber = { fg = \"blue\", italic = true }\nletter = { fg = \"magenta\", italic = true }\nseparator = { fg = \"red\" }\n\n[quotes]\nstyle = { fg = \"yellow\" }\nquote_token = '\"'\n\n[paths]\nsegment = { fg = \"green\", italic = true }\nseparator = { fg = \"yellow\" }\n\n[uuids]\nnumber = { fg = \"blue\", italic = true }\nletter = { fg = \"magenta\", italic = true }\nseparator = { fg = \"red\" }\n\n[pointers]\nnumber = { fg = \"blue\", italic = true }\nletter = { fg = \"magenta\", italic = true }\n\n[key_value_pairs]\nkey = { faint = true }\nseparator = { fg = \"white\" }\n\n[processes]\nname = { fg = \"green\" }\nbracket = { fg = \"red\" }\nid = { fg = \"yellow\" }\n\n[json]\nkey = { fg = \"yellow\" }\nquote_token = { fg = \"yellow\", faint = true }\ncurly_bracket = { faint = true }\nsquare_bracket = { faint = true }\ncomma = { faint = true }\ncolon = { faint = true }\n```\n\n\u003C\u002Fdetails>\n\n### Disabling Highlight Groups\n\nTo individually disable or enable default highlight groups, use the `--enable` and `--disable` flags:\n\n```console\n# Enable only the url highlight group, disable the rest\ntspin application.log --enable urls\n\n# Disable the numbers highlight group, keep the rest\ntspin application.log --disable numbers\n```\n\n### Adding Keywords via theme.toml\n\nTo add custom keywords, either include them in the list of keywords or add new entries:\n\n```toml\n[[keywords]]\nwords = ['MyCustomKeyword']\nstyle = { fg = \"green\" }\n\n[[keywords]]\nwords = ['null', 'true', 'false']\nstyle = { fg = \"red\", italic = true }\n```\n\n### Adding Keywords from the command line\n\nSometimes it is more convenient to add highlight groups on the fly without having to edit a TOML. To add highlights from\nthe command line, use the `--highlight` flag followed by a comma separated list of words to be highlighted.\n\nFor example:\n\n```console\ntspin --highlight=red:error,fail --highlight=green:success,ok\n```\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fexamples\u002Fotf.png\" width=\"800\"\u002F>\n\u003C\u002Fp>\n\n### Custom regex highlighters\n\nWhen you need more control over the highlighting, you can use the regex highlighter. This highlighter allows you to\nspecify a regex and a style to be applied to the matched text.\n\nIt supports one capture group `()`. When found, it will apply the style to the captured text.\n\n```toml\n[[regexes]]\nregex = 'Started (.*)\\.'\nstyle = { fg = \"red\" }\n```\n\n## Working with `stdin` and `stdout`\n\n### Default behavior with pipes\n\nBy default, `tailspin` will open a file in the pager `less`. However, if you pipe something into `tailspin`, it will\nprint the highlighted output directly to `stdout`. This is similar to running `tspin [file] --print`.\n\nTo let `tailspin` highlight the logs of different commands, you can pipe the output of those commands into `tailspin`\nlike so:\n\n```console\njournalctl -f | tspin\ncat \u002Fvar\u002Flog\u002Fsyslog | tspin\nkubectl logs -f pod_name | tspin\n```\n\n### Capturing the output of a command and viewing it in `less`\n\nTo capture the output of a command and view it in `less`, use the `--exec` flag:\n\n```console\ntspin --exec 'kubectl logs -f pod_name'\n```\n\nThis will run the command `kubectl logs -f pod_name` in the background and pipe the output to `tailspin`. The output\nwill be displayed in `less`, allowing you to navigate and search through the logs.\n\n## Using the pager `less`\n\n### Overview\n\n`tailspin` uses `less` as its pager to view the highlighted log files. You can get more info on `less` via the **man**\ncommand (`man less`) or by hitting the \u003Ckbd>h\u003C\u002Fkbd> button to access the help screen.\n\n### Navigating\n\nNavigating within `less` uses a set of keybindings that may be familiar to users of `vim` or other `vi`-like\neditors. Here's a brief overview of the most useful navigation commands:\n\n- \u003Ckbd>j\u003C\u002Fkbd>\u002F\u003Ckbd>k\u003C\u002Fkbd>: Scroll one line up \u002F down\n- \u003Ckbd>d\u003C\u002Fkbd>\u002F\u003Ckbd>u\u003C\u002Fkbd>: Scroll one half-page up \u002F down\n- \u003Ckbd>g\u003C\u002Fkbd>\u002F\u003Ckbd>G\u003C\u002Fkbd>: Go to the top \u002F bottom of the file\n\n### Follow mode\n\nWhen you run `tailspin` with the `-f` or `--follow` flag, it will scroll to the bottom and print new lines to the screen\nas they're added to the file.\n\nTo stop following the file, interrupt with \u003Ckbd>Ctrl + C\u003C\u002Fkbd>. This will stop the tailing, but keep the\nfile open, allowing you to review the existing content.\n\nTo resume following the file from within `less`, press \u003Ckbd>Shift + F\u003C\u002Fkbd>.\n\n### Search\n\nUse \u003Ckbd>\u002F\u003C\u002Fkbd> followed by your search query. For example, `\u002FERROR` finds the first occurrence of\n**ERROR**.\n\nAfter the search, \u003Ckbd>n\u003C\u002Fkbd> finds the next instance, and \u003Ckbd>N\u003C\u002Fkbd> finds the previous instance.\n\n### Filtering\n\n`less` allows filtering lines by a keyword, using \u003Ckbd>&\u003C\u002Fkbd> followed by the pattern. For instance, `&ERROR` shows\nonly lines with **ERROR**.\n\nTo only show lines containing either `ERROR` or `WARN`, use a regular expression: `&\\(ERROR\\|WARN\\)`.\n\nTo clear the filter, use \u003Ckbd>&\u003C\u002Fkbd> with no pattern.\n\n### Custom pagers\n\nSet the `TAILSPIN_PAGER` environment variable to override the default pager.\nThe command must include the string **[FILE]** which will be replaced with the file path internally.\n\nFor example:\n\n```console\nTAILSPIN_PAGER=\"ov -f [FILE]\" tspin example-logs\u002Fexample1\n```\n\n## Settings\n\n```console\n-f, --follow                     Follow the contents of the file\n-p, --print                      Print the output to stdout\n-e, --exec='[CMD]'               Run command and view the output in a pager\n                                 (e.g. `tspin --exec 'kubectl logs -f pod_name'`)\n    --config-path=[PATH]         Use the configuration file from the provided path\n    --pager=[CUSTOM_PAGER]       Set a custom pager\n                                 (e.g. `--pager=\"ov -f [FILE]\"`)\n    --highlight=[COLOR]:[WORDS]  Highlight the provided comma-separated words in the specified color\n                                 (e.g. `--highlight red:ERROR,WARNING`)\n    --enable [HIGHLIGHT_GROUP]   Enable one or more default highlight groups, disabling the rest\n                                 (e.g. `--enable keywords,urls`)\n    --disable [HIGHLIGHT_GROUP]  Disable one or more default highlight groups, enabling the rest\n                                 (e.g. `--disable keywords,urls`)\n    --extras [EXTRA]             Enable extra highlight groups on top of the current configuration\n                                 (e.g. `--extras ipv6`)\n    --disable-builtin-keywords   Disable the highlighting of booleans, nulls, log severities and common REST verbs\n```\n\n\n","tailspin 是一个用于高亮显示日志文件的工具。它使用 Rust 语言编写，能够自动识别并高亮日志中的数字、日期、IP 地址、UUID 和 URL 等常见模式，无需任何配置即可工作，并且支持自定义高亮规则。此外，tailspin 易于与其他命令集成，支持从标准输入读取数据或直接处理文件内容。适用于需要快速查看和分析各种格式日志文件的场景，如开发调试、系统监控等。",2,"2026-06-11 03:03:56","top_language"]