feat: C template #27
22
c/.editorconfig
Normal file
|
|
@ -0,0 +1,22 @@
|
||||||
|
root = true
|
||||||
|
|
||||||
|
[*]
|
||||||
|
charset = utf-8
|
||||||
|
end_of_line = lf
|
||||||
|
indent_size = 4
|
||||||
|
indent_style = space
|
||||||
|
insert_final_newline = true
|
||||||
|
max_line_length = 80
|
||||||
|
tab_width = 4
|
||||||
|
|
||||||
|
[{Makefile,*.mk}]
|
||||||
|
indent_style = tab
|
||||||
|
|
||||||
|
[*.nix]
|
||||||
|
indent_style = space
|
||||||
|
tab_width = 2
|
||||||
|
indent_size = 2
|
||||||
|
|
||||||
|
[*.lock]
|
||||||
|
indent_style = unset
|
||||||
|
insert_final_newline = unset
|
||||||
2
c/.gitattributes
vendored
Normal file
|
|
@ -0,0 +1,2 @@
|
||||||
|
* text=lf
|
||||||
|
* eol=lf
|
||||||
15
c/.gitignore
vendored
Normal file
|
|
@ -0,0 +1,15 @@
|
||||||
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
# binaries
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
hello
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
# build
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
*.[aod]
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
# config
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
compile_commands.json
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
.pre-commit-config.yaml
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
.cache
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
# nix
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
.direnv
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
.envrc
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
|
result
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example ```suggestion
```
this can be commited, as long as it doesn't assume nix is installed. this can work for example
```
if has nix_direnv_version; then
use flake
fi
```
```suggestion
result*
repl-result-*
```
these are all unused ```suggestion
```
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched ```suggestion
```
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched
Only the I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like Only the `.pre-commit-config.yaml` is unused so I'll remove it.
I'm not sure why do you want to include entries unrelated to this template in the gitignore but also removing important ignore like `.cache` or `compile_commands.json` that are useful, it seems like a contradiction?
Committing a Committing a `.envrc` doesn't seems like a good practice to me.
I can remove that entry tho, so it's up to the user to decide was to do i they use direnv
I cant find any public gitignore using I cant find any public gitignore using `repl-result-*`, so it sound like something we may not need
yeah this would be better removed yeah this would be better removed
if you use > I cant find any public gitignore using repl-result-*, so it sound like something we may not need
if you use `:bl` in a repl, you do. this is a known nix artifact, same as `result*`
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either > important ignore like .cache or compile_commands.json
the only reason they are important is because of the specific way you have this set up. other projects are very unlikely to use these, and i would say they shouldn't be used here either
This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other This is the same scenario with the other GitHub ignore you wanted me to include, I think either both should be put or none, because it doesn't seem logic to add one and not the other
|
|||||||
29
c/Dockerfile
Normal file
|
|
@ -0,0 +1,29 @@
|
||||||
|
# Credit to Mitchell Hashimoto
|
||||||
|
# post: https://mitchellh.com/writing/nix-with-dockerfiles
|
||||||
|
|
||||||
|
# Nix builder
|
||||||
|
FROM nixos/nix:latest AS builder
|
||||||
|
|
||||||
|
# Copy our source and setup our working dir.
|
||||||
|
COPY . /tmp/build
|
||||||
|
WORKDIR /tmp/build
|
||||||
|
|
||||||
|
# Build our Nix environment
|
||||||
|
RUN nix \
|
||||||
|
--extra-experimental-features "nix-command flakes" \
|
||||||
|
--option filter-syscalls false \
|
||||||
|
build
|
||||||
|
|
||||||
|
# Copy the Nix store closure into a directory. The Nix store closure is the
|
||||||
|
# entire set of Nix store values that we need for our build.
|
||||||
|
RUN mkdir /tmp/nix-store-closure
|
||||||
|
RUN cp -R $(nix-store -qR result/) /tmp/nix-store-closure
|
||||||
|
|
||||||
|
# Final image is based on scratch. We copy a bunch of Nix dependencies
|
||||||
|
# but they're fully self-contained so we don't need Nix anymore.
|
||||||
|
FROM scratch
|
||||||
|
|
||||||
|
# Copy /nix/store
|
||||||
|
COPY --from=builder /tmp/nix-store-closure /nix/store
|
||||||
|
COPY --from=builder /tmp/build/result /app
|
||||||
|
CMD ["/app/bin/hello"]
|
||||||
4
c/tokei.toml
Normal file
|
|
@ -0,0 +1,4 @@
|
||||||
|
columns = 80
|
||||||
|
sort = "lines"
|
||||||
|
types = ["C", "C Header", "Makefile", "Markdown"]
|
||||||
|
treat_doc_strings_as_comments = true
|
||||||
this can be commited, as long as it doesn't assume nix is installed. this can work for example
these are all unused
when using cmake or meson with github's template, these are not necessary as we have a standard build directory and file extensions are already matched