Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Vomitorium – all of your project in 1 text file

npmjs.com

Post reply on HN
Print view View original

11–20 of 56 posts

Re: Show HN: Vomitorium – all of your project in 1 text file

#11

Post by sureglymop »

c-fe wrote: post #9

Love this. I created (half-jokingly, but only half) the concept of a monofile (inspired by our monorepo) in our team. I have not managed to convince my colleagues to switch yet, but maybe this package can help. Unironically, I find that in larger python projects, combining various related sub 100 loc files into one big sub 1000 loc file can do magic to circular import errors and remove 100s of lines of import stateme…

I usually do this with docker/podman compose files for dev environments.

I see people creating all kinds of mounts and volumes but I just embed files inline under the configs top level key. I even embed shell scripts that way to do one shot/initialization tasks.

The goal is to just have one compose.yml file that the developer can spin up for a local development reproduction of what they need. It's quite nice.

Re: Show HN: Vomitorium – all of your project in 1 text file

#12

Post by phito »

sureglymop wrote: post #11
c-fe wrote: post #9

Love this. I created (half-jokingly, but only half) the concept of a monofile (inspired by our monorepo) in our team. I have not managed to convince my colleagues to switch yet, but maybe this package can help. Unironically, I find that in larger python projects, combining various related sub 100 loc files into one big sub 1000 loc file can do magic to circular import errors and remove 100s of lines of import stateme…

I usually do this with docker/podman compose files for dev environments. I see people creating all kinds of mounts and volumes but I just embed files inline under the configs top level key. I even embed shell scripts that way to do one shot/initialization tasks. The goal is to just have one compose.yml file that the developer can spin up for a local development reproduction of what they need. It's quite nice.

I like splitting large compose file in smaller units and including them in the main compose file

Re: Show HN: Vomitorium – all of your project in 1 text file

#13

Post by langcss »

thih9 wrote: post #7
istvanmeszaros wrote: post #5

Love the name :D.

> A vomitorium is a passage situated below or behind a tier of seats in an amphitheatre or a stadium through which large crowds can exit rapidly at the end of an event. > A commonly held but erroneous notion is that Ancient Romans designated spaces called vomitoria for the purpose of literal vomiting, as part of a binge-and-purge cycle https://en.wikipedia.org/wiki/Vomitorium

Related-ish: https://en.wikipedia.org/wiki/Nosebleed_section

Re: Show HN: Vomitorium – all of your project in 1 text file

#16

Post by samrolken »

I have a bash script which is very similar to this, except instead of dumping it all into one file, it opens all the matched files as tabs in Zed. Since Zed's AI features let you dump all, or a subset, of open tabs into context, this works great. It gives me a chance to curate the context a little more. And what I'm working on is probably already in an open tab anyway.

Re: Show HN: Vomitorium – all of your project in 1 text file

#20

Post by Diti »

ghgr wrote: post #6

As an alternative to (npm -g)'ing here some potentially useful coreutils one-liners I've been using for a similar purpose: - Dump all .py files into out.txt (for copy/paste into a LLM) > find . -name "*.py" -exec cat {} + > out.txt - Sort all .py files by number of lines > find . -name '*.py' -exec wc -l {} + | sort -n

I was going to comment this. “What’s wrong with `cat`”, whose job is literally to concatenate files? Or even [uncompressed] `tar` archives, which are basically just a list of files with some headers?
Post reply on HN