summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* stat: Keep statx()-specific flags separateTavian Barnes2022-05-121-8/+9
| | | | | Previously, if statx() was unsupported at runtime, we could end up passing AT_STATX_DONT_SYNC to fstatat() which doesn't expect it.
* stat: Factor the BFS_STAT_TRYFOLLOW retry logic outTavian Barnes2022-05-121-30/+25
|
* stat: Rename some feature detection macrosTavian Barnes2022-05-121-8/+8
|
* color: Don't colorize capable files by defaultTavian Barnes2022-05-111-1/+1
| | | | | | | GNU ls changed this default in coreutils 9.1, since checking capabilities has a severe performance penalty. Link: https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=6b5134770d35b045e5a9219bf4a216324e0113d3
* color: Only check ln=target onceTavian Barnes2022-05-111-7/+7
| | | | Fixes: 7241d6cc35134fcb5ec6dfa81bbd01e430b2415f
* Makefile: Look for .d files in the right placesTavian Barnes2022-05-111-1/+1
| | | | Fixes: f2cb2215213c0d831a697b0b440f78d9ad5c2b83
* main: Avoid a gotoTavian Barnes2022-05-111-6/+5
|
* README: Add links to upstream packagesTavian Barnes2022-05-111-9/+9
|
* Makefile: New check-install targetTavian Barnes2022-05-091-0/+8
|
* README: Use a table for side-by-side examplesTavian Barnes2022-05-091-10/+35
|
* docs: New USAGE.md documentTavian Barnes2022-05-092-40/+175
|
* docs: Move dependency flag info from the README to docs/BUILDING.mdTavian Barnes2022-05-072-11/+22
|
* docs: Split CONTRIBUTING into BUILDING and HACKINGTavian Barnes2022-05-073-48/+57
|
* README: Add a link to the AUR packageTavian Barnes2022-05-071-0/+3
|
* README: Open the "already packaged" section by defaultTavian Barnes2022-05-071-2/+10
|
* README: Reformat to save some vertical spaceTavian Barnes2022-05-071-16/+50
|
* docs: Move some documentation into a subfolderTavian Barnes2022-04-214-2/+2
|
* Add basic zsh completionArvid Norlander2022-04-212-0/+175
| | | | Fixes #32.
* Makefile: Put the main .o files under build/srcTavian Barnes2022-04-212-36/+32
|
* Makefile: Generate build/FLAGS.new with its own targetTavian Barnes2022-04-211-4/+7
|
* Makefile: Replace flags.sh with a two-line recipeTavian Barnes2022-04-192-15/+2
|
* Makefile: Move .flags to build/FLAGSTavian Barnes2022-04-193-12/+14
|
* Makefile: Quiet errors from git describeTavian Barnes2022-04-191-3/+5
| | | | | | | | | | | | | | | | With new git versions, it is an error to invoke git inside a repository owned by someone else. This manifested as $ sudo make install fatal: unsafe repository ('/home/tavianator/code/bfs' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /home/tavianator/code/bfs Work around it with `2>/dev/null`. This should also help if git is not installed, but .git/ still exists. Link: https://github.blog/2022-04-12-git-security-vulnerability-announced/
* RELEASES.md: 20222 is too far awayTavian Barnes2022-04-191-1/+1
|
* ci/codecov: Look for gcov files under buildTavian Barnes2022-04-181-1/+1
|
* Makefile: Spread out the .PHONY targetsTavian Barnes2022-04-181-2/+9
|
* Makefile: Use a recipe to update .flags rather than $(shell)Tavian Barnes2022-04-181-8/+4
| | | | | | | | | This means we don't need to generate .flags unless we're actually building a target that needs it, which is important for thing like $ sudo make install that used to inconveniently create a root-owned .flags file.
* tests: Also put build outputs under build/Tavian Barnes2022-04-163-19/+14
|
* Keep Build Files In `build` (#89)トトも2022-04-161-29/+32
|
* Source / Include Folder (#88)トトも2022-04-1654-5/+8
| | | Moved Source Files Into `src` Folder
* style: Use &array[i] rather than array + iTavian Barnes2022-04-163-8/+8
|
* color: Support a separate $BFS_COLORS environment variableTavian Barnes2022-04-155-70/+84
|
* color: Use three-letter codes for warnings and errorsTavian Barnes2022-04-153-11/+11
| | | | No reason to potentially conflict with the two-letter codes GNU ls uses.
* tests: Quiet errors from chflagsTavian Barnes2022-04-151-1/+1
|
* eval: Use BFTW_BUFFER when deleting files on FreeBSDTavian Barnes2022-04-151-0/+35
| | | | Works around #67.
* bftw: New BFTW_BUFFER flagTavian Barnes2022-04-152-2/+4
|
* bfs.1: Fix a confusing comma in the -size docsTavian Barnes2022-04-011-2/+2
|
* opt: Use floats consistently for probabilities and costsTavian Barnes2022-03-272-5/+5
|
* Release 2.52.5Tavian Barnes2022-03-273-2/+29
|
* README: Add a blurb about fancy errors/warningsTavian Barnes2022-03-271-0/+22
|
* parse.c: Use state->last_arg as the location for the expected )Tavian Barnes2022-03-271-16/+4
| | | | This lets us remove the special case for *argv == NULL.
* diag: Avoid printing trailing spacesTavian Barnes2022-03-271-3/+5
|
* opt: Add some more warningsTavian Barnes2022-03-271-0/+6
|
* parse: Highlight command line errorsTavian Barnes2022-03-274-191/+380
|
* diag: New functions for highlighting command line argumentsTavian Barnes2022-03-275-75/+185
|
* util: New xstrwidth() functionTavian Barnes2022-03-262-0/+46
|
* opt: Warn about expressions we remove while optimizingTavian Barnes2022-03-263-28/+115
|
* parse: Stop warning for options after tests/actionsTavian Barnes2022-03-261-44/+7
| | | | | | | | | | | Part of the bfs design philosophy is to care less about the order of arguments. As such, there's no good reason to be warning-compatible with GNU find in this case. I don't even think things like this are confusing: bfs -print -color so why warn about it?
* expr: Store auxilliary data in a unionTavian Barnes2022-03-259-777/+815
| | | | And rename struct expr to bfs_expr.
* Update from C99 to C11Tavian Barnes2022-03-252-2/+2
| | | | This is necessary for standard anonymous structs/unions.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 04:28:56 +0000