Shouldn't this work?
find /path/to/directory -type f -exec cat {} + > output.txt
Show HN: Vomitorium – all of your project in 1 text file
51–56 of 56 posts
Re: Show HN: Vomitorium – all of your project in 1 text file
#52We use a C compiler for embedded systems that doesn't support link time optimizations (unless you pay for the pro version, that is). I have been thinking about some tool like this that merges all C source files for compilation.
That's called a "unity" build, isn't it? I was under the impression that it was a relatively well-known technique, such that there are existing tools to merge a set of source files into a single .c file.
Re: Show HN: Vomitorium – all of your project in 1 text file
#53I've been dreaming of a tool which resembles this, at least in spirit. I want to figure out how to structure a codebase such that a failing test can spit out a CID for that failure such that it can be remotely recreated (you'd have to be running ipfs so that the remote party can pull the content from you, or maybe you push it to some kind of hub before you share it). It would be the files relevant to that failure--bo…
Hmm, you could probably make a proof of concept on a weekend specifically in the typescript/JavaScript ecosystem, as it's already heavily reliant on bundlers. The process could be 1. defining a new/temporary bundler entry point 2. copying the failing code into the file 3. Bundle without minification It'd probably be best to reduce scope by limiting it to a specific testing framework and make it via an extension, i.e.…
You're talking sense, but I'm kinda wanting to do it at the subprocess level so that caller and callee need not use the same language (I was talking in terms of tests but tests are just a special kind of function).
Whether to use nodejs or python or rust (and which version thereof) will be as much a part of the bundled function as its code. I figure I'll wrap nix so it can replicate the environments, then I'll just have to do the runtime stuff.
Re: Show HN: Vomitorium – all of your project in 1 text file
#54Surely with storage being pretty slow and everything it would be better to compress it into an archive with really basic compression?
Re: Show HN: Vomitorium – all of your project in 1 text file
#55One feature you could add is allowing the user to map changes in the concatenated file back to the original files.
For example, if an LLM edits the concatenated file, I would want it to return the corresponding filenames and line numbers of the original files.
Re: Show HN: Vomitorium – all of your project in 1 text file
#56Cool! I'd like to see an indication of the total number of tokens in the output, so I know right away on which LLM I can use this prompt or, if it's too large, I can relaunch the script by excluding other files to reduce the number of tokens in the output