There is a naive caching mechanism, where the tool deletes each repo if it is older than 3 minutes. The Linux file command will quickly tell you what type of file it is.

repo-peek downloads the tar:gz of the repo, extracts it and saves it to ~/.repk. A quick peek at the first eight bytes of the binary with hexdump will show the signature byte and ELF string in the first four bytes of the file. developer and went to verify that I could use fgets on commands that I used with popen.

The tool creates 2 files and a directory, a config file ~/.repk.ini, a log file ~/.repk.log and a directory ~/.repk. pants peek args Display BUILD target info Backend: section: peek Basic options outputfile -peek-output-file. fgetss() - Gets line from file pointer and strip HTML tags.

The configs after these have the format: remove_by – time till the cache would be kept Peek Definition (Ctrl+Shift+F10), is similar, but displays the definition directly in the editor (making space in the editor window to avoid obscuring any code). You can open directories to change working directories, edit text files, and even request your desktop environment to open a file.

It will list all the files in your working directory and allow you to interact with them. Proxy_settings – if you are inside a proxy set these Peek gives you interactive exploration of directories on the command line. Editor = 'vim ' cache_repos = 1Ĭache_loc = ' ' github_token = ' ' gitlab_token = ' ' https_proxy = ' ' http_proxy = ' ' remove_by = 20210213-185716Įditor – editor of choice (default=vim) cache_repos – should repos be cached (default=1, set 0 if caching is not required) cache_delta – mintues for which repos should be cached cache_loc – directory where cached repos should be stored (default=~/.repk) github_token – for handling throlling limits (not implemented) gitlab_token – for handling throlling limits (not implemented)

Command line file peek