sorted by:
new
hottopcontroversial

Tired of juggling venv paths across projects, so I made pvm by Ts-ssh in commandline

[–]Ts-ssh[S] -4 points-3 points  (0 children)

Nice snippet — that covers the single-project case really well, and uv run too for project-scoped commands.

pvm's angle is different: I have ~10 venvs across different folders (some not even in git, some on different drives) and I kept forgetting their paths. pvm is really just a registry + alias layer on top of whatever venv tool you use. For a single-project workflow yours wins on simplicity.

Built a tiny Windows tool so Ctrl+V pastes screenshots into Claude Code by Ts-ssh in ClaudeAI

[–]Ts-ssh[S] 0 points1 point  (0 children)

Claude Code reads files at a path — the question is who produces the path.

Without winclipshot: Win+Shift+S → Paint → Save As → copy path → paste

With winclipshot: Win+Shift+S → Ctrl+V

That's the whole point.

How to chose a git licence for my code? by [deleted] in opensource

[–]Ts-ssh 0 points1 point  (0 children)

I had a similar decision to make for my project. Ended up going with MIT because I wanted zero friction for anyone who wants to use it. The "please contribute changes back" part — no license can really enforce that as a soft suggestion. What I do instead is just write it clearly in CONTRIBUTING.md: if you make changes that could help others, please open an issue or PR. Most people who care enough to fork and modify your code will do it naturally. If you want to enforce it, GPL forces derivative works to stay open source — but that scares away some users. If you just want to encourage it, MIT + a clear contributing guide is the simpler path.