Show HN: Zxc – Rust TLS proxy with tmux and Vim as UI, BurpSuite alternative
Link: https://github.com/hail-hydrant/zxc
Discussion: https://news.ycombinator.com/item?id=43568771
Who's using #vim with #autocomplete for #PowerShell ?
I know you're out there.
I see a bunch of add-ons that purport to do this but it's hard to know what to trust. What's good here?
BONUS: I do most of my PowerShell work in #Linux.
Please #boost!
GitHub - hail-hydrant/zxc:基於終端機的攔截代理,採用 Rust 編寫,並以 tmux 和 Vim 作為使用者介面
➤ 一款基於終端機的強大網路代理工具
✤ https://github.com/hail-hydrant/zxc
zxc 是一個基於 Rust 編寫的終端機攔截代理工具,它利用 tmux 和 Vim 作為使用者介面。它允許使用者攔截、檢查和修改 HTTP/1.1 和 WebSocket 流量,並提供了歷史記錄、重放和附加元件等功能。使用者可以自定義配置,並通過 Vim 插件來管理和操作請求與回應。
+ 這個工具看起來很專業,對於需要深入分析網路流量的開發者或安全研究人員來說非常有用。
+ 能夠使用 Vim 作為介面實在太酷了!我很喜歡這種獨特的設計理念,而且Rust的效能應該會很好。
#開源工具 #網路代理 #Rust #Vim #Tmux
Python developers might appreciate being able to look up stdlib documentation right inside of Vim: https://github.com/girishji/pythondoc.vim
Wednesday Progress Report April 2, 2025
#Beyond365DaysOfCode Day 94
#100DaysOfCode Day 94
#freeCodeCamp | #Python | #Vim | #SecondYearOfCode | #Code_Academy
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced Vim motions (30 minutes).
Trello: Updated the board.
freeCodeCamp: Continued Full Stack Developer Curriculum.
Consistent progress fuels success! Keep pushing forward! #DevLife #StayMotivated #KeepCoding
Monday Progress Report March 31, 2025
#Beyond365DaysOfCode Day 92
#100DaysOfCode Day 92
#freeCodeCamp | #Python | #Vim | #VS_Code
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced Vim motions (30 minutes).
Trello: Updated the board.
freeCodeCamp: Full Stack Developer Program.
Closing out March strong! Let’s keep leveling up! #KeepCoding #BuildAndLearn #CodeEveryDay
Wednesday Progress Report March 26, 2025
#Beyond365DaysOfCode Day 87
#100DaysOfCode Day 87
#freeCodeCamp | #Python | #Vim | #SecondYearOfCode | #Code_Academy
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced (30 minutes).
Trello: Updated the board.
freeCodeCamp: Continued Full Stack Developer Curriculum.
Every line of code is a step forward! Keep pushing! #CodeEveryDay #KeepBuilding #DevMindset
So I’ve been using vi for over three decades now, and vim was often the flavor of vi being used.
I just noticed that when editing a compressed file in vim (e.g. vim foo.gz), the implicit decompression step is entered into the undo log. You can hit u right after file load and get the compressed binary data.
Huh.
An asynchronous VsCode-like HTTP plugin for Neovim https://lobste.rs/s/ikc5av #api #programming #vim
https://github.com/blacklight/nvim-http
Tuesday Progress Report March 25, 2025
#Beyond365DaysOfCode Day 86
#100DaysOfCode Day 86
#freeCodeCamp | #Python | #Vim | #Code_Academy
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced (30 minutes).
Trello: Updated the board.
freeCodeCamp: Full Stack Developer Program.
Small steps lead to big progress! Keep going! #CodeDaily #StayMotivated #DevJourney
Monday Progress Report March 24, 2025
#Beyond365DaysOfCode Day 85
#100DaysOfCode Day 85
#freeCodeCamp | #Python | #Vim | #VS_Code
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced (30 minutes).
Trello: Updated the board.
freeCodeCamp: Full Stack Developer Program.
Another step forward! Keep building, keep learning! #CodeConsistency #DevJourney #LevelUp
Saturday Progress Report March 22, 2025
#Beyond365DaysOfCode Day 83
#100DaysOfCode Day 83
#freeCodeCamp | #Python | #Vim | #SecondYearOfCode | #NextLevelCoding
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced plugin configurations (30 minutes).
Trello: Updated the board.
freeCodeCamp: Continued Full Stack Developer Curriculum.
Every line of code brings progress! #KeepBuilding #DevJourney #CodeEveryDay
Friday Progress Report March 21, 2025
#Beyond365DaysOfCode Day 82
#100DaysOfCode Day 82
#freeCodeCamp | #Python | #Vim | #SecondYearOfCode
Daily Reading:
freeCodeCamp News – 1 article
Daily.dev – 1 article
Vim: Practiced motions for 30 minutes.
Trello: Updated the board.
freeCodeCamp: Continued Full Stack Developer Curriculum.
Staying consistent, one step at a time! #KeepCoding #TechJourney #DevLife
What a luck #dropbox destroyed its paper product, which was my favorite #quicknotes tool and last tie to dropbox.Now using #hedgedoc and never been that happy.Amazing tool. Once again #opensource rules.And that #vim support,what a touch of genius! :-)
More tech notes to myself
A very brief introduction to the #Readline library, customizing the #Bash shell prompt with mode indicators, and the vi editing mode.
Customizing the Bash command prompt for vi editing mode
https://suburbanalities.blogspot.com/2025/04/customizing-bash-command-prompt-for-vi.html
@ThierryStoehr
J'utilise #vi ou #neovim comme vi.
Il n'y a rien à ajouter.
Je n'utilise pas #vim.
J'utilise #Emacs pour toutes, même vi. Avec un grande tas des packages.
Et si on utilisait «#Emacs-only», ou «Vim-only» ?
Le « only » pouvant dire « je n'utilise que lui, car je fais tout avec ! » : c'est possible avec toutes les possibilités offertes par ces 2 logiciels ultra-puissants du #format texte.
Mais avec un autre sens : seulement #Emacs ou #Vim installés. Donc sans ajout d'un module, sans code (LISP) à créer, sans librairie à télécharger, sans dépendance à ajouter. Le logiciel tel quel dans sa version X.Y.Z.
Ce qui est en standard est ce qui est utilisé.
If you'd like to prank a fellow Vim user, send them a text file with `vim: revins` at the bottom and ask them to type some text in it... https://vimhelp.org/options.txt.html#%27revins%27
Unless they've turned off their `modeline` setting, something like this should happen: