A terminal interface for StackOverflow written in Rust

栏目: IT技术 · 发布时间: 4年前

内容简介:While I like the acronymYou can install the AUR package

A terminal interface for StackOverflow written in Rust

A terminal interface for StackOverflow written in Rust

A terminal interface for StackOverflow written in Rust

example usage

While I like the acronym so , this tool would actually be better described as se : an interface to the StackExchange network. In particular one thing that differentiates it from similar tools is that you can simultaneously search any number of sites in the StackExchange network:

# search using your default configuration
$ so how do i reverse a list in python

# search for a latex solution
$ so --site tex how to put tilde over character

# use google to search stackoverflow.com, askubuntu.com, and unix.stackexchange.com
$ so -e google -s askubuntu -s stackoverflow -s unix how do i install linux

installation

Arch Linux

You can install the AUR package so (tracks latest release) or so-git (tracks master), e.g.

yay -S so-git

MacOS

You can install via homebrew

brew install samtay/tui/so

cargo

cargo install so

release binaries

Static binaries are available on the releases page for common Linux, MacOS, and Windows targets. You can quickly install the one you need to directory DEST with:

curl --proto '=https' --tlsv1.2 -sSf https://samtay.github.io/so/install.sh \
  | bash -s -- --to DEST

Right now I'm only building the most common targets, but in theory it should be easy to add more, so if you don't see what you are looking for just open an issue and I can add it. Here's a list of the supported targets . If you don't know what you need, you can install rustc and open an issue with the output of rustc -Vv | grep host | cut -d' ' -f2 .

documentation

configuration

The configuration files for e.g. a user Alice can be found in the following directories:

/home/alice/.config/so
C:\Users\Alice\AppData\Roaming\Sam Tay\so
/Users/Alice/Library/Preferences/io.Sam-Tay.so

defaults

The config.yml file let's you specify your CLI defaults. So if you dislike the lucky prompt, always search serverfault.com and unix.stackexchange.com, and want thefastest search engine, you can set your config file like this:

# config.yml
---
api_key: ~
limit: 10
lucky: false
sites:
  - serverfault
  - unix
search_engine: stackexchange

Run so --help to see your current defaults.

themes

In the same directory you'll find colors.toml which is self-documented. The default theme attempts to blend in with your default terminal theme, but you can change it as necessary. In particular, you may want to change the highlight_text if the current selection is difficult to read. There are some themes in the themes directory as well.

api keys

If you want to use your own StackExchange API Key you can set it via

so --set-api-key <KEY>

You can also choose to use no key by editing your configuration to api_key: ~ . If for some reason my API key is globally throttled, you can hit the StackExchange API with no key up to 300 times per day per IP, which I imagine is fine for most users.

search engines

The available search engines are StackExchange, DuckDuckGo, and Google. StackExchange will always be the fastest to search because it doesn't require an additional request or any HTML parsing; however, it is also very primitive. DuckDuckGo is in second place for speed, as its response HTML is much smaller than Google's. I've found that it performs well for my queries, so it is the default search engine.

multi-site searching

As stated in the docs ,

If a single IP is making more than 30 requests a second, new requests will be dropped.

So, don't go crazy with the multi-site search, since it is all done in parallel. In particular, if you specify more than 30 sites, SE will likely ban you for a short time.

selecting a backend

If you're installing from source, you can choose from a number of available backend rendering engines. Note that the package default and windows feature flags do not have an ncurses dependency, for the sake of portability. The default backend is termion , a bindless library in pure Rust which seems to work quite well on Linux, MacOS, BSD, and Redox. The windows backend is by default crossterm , and while its level of support is awesome, it does comes at a price in performance. On my machine, the app kind of flashes between draws. So if you are on Mac, Linux, or Redox, your best bet is to compile with default features which uses the termion backend. If you are on windows, use crossterm, but know it will be slightly jumpy.

If the crossterm folks figure out a fix for allowing ncurses to receive resize events , and you have ncurses installed on your system, then the ncurses and pancurses backends are likely the most performant. Just know that currently if you choose this option, and you run the --lucky prompt, you won't be able to resize the terminal window while the TUI is open.

Available backends:

termion-backend
ncurses-backend
pancurses-backend
crossterm-backend

E.g. to use ncurses-backend :

cargo install so --no-default-features --features ncurses-backend

See more information about this choice here .

contributing

Warning: this was my first time writing Rust and there is very likely some non-idiomatic and straight up ugly code throughout this project, so don't come looking here for a good Rust example! That being said, I would love to improve the codebase. Feel free to check out the contributing guidelines and submit any refactoring issues or pull requests.

credits

Credit to my good friend Charles for logo design.


以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网

查看所有标签

猜你喜欢:

本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们

格蠹汇编

格蠹汇编

张银奎 / 电子工业出版社 / 2013-3-1 / 66.00元

《格蠹汇编——软件调试案例集锦》以案例形式讨论了使用调试技术解决复杂软件问题的工具和方法。全书共36章,分为四篇。前两篇每章讲述一个有代表性的真实案例,包括从堆里抢救丢失的博客,修复因误杀而瘫痪的系统,徒手战木马,拯救“发疯”的windows7,经典阅读器的经典死锁,拯救挂死的powerpoint,转储分析之双误谜团,是谁动了我的句柄,寻找系统中的“耗电大王”,解救即将被断网的系统,转储分析之系统......一起来看看 《格蠹汇编》 这本书的介绍吧!

URL 编码/解码
URL 编码/解码

URL 编码/解码

XML 在线格式化
XML 在线格式化

在线 XML 格式化压缩工具

UNIX 时间戳转换
UNIX 时间戳转换

UNIX 时间戳转换