| Age | Commit message (Collapse) | Author |
|---|
|
|
|
It seems like --ignore isn't as 1:1 with the local ignore file.
Which is very frustrating TBH!
The good news is it looks like it takes precident over the default
settings which ignored the .gitignore - so we can throw that into the
mix!
Overall, this tool is very nice because it makes traversing these files
much much simpler. But I feel like for something that SHOULD be
relatively simple is actually not so? Which is a shame.
|
|
.stowrc file is a local configuration specific to this repository. It
should not get copied over to home directory
|
|
Some stupid reason I was thinking "oh $HOME is more universal" ... IDK
why I thought that would make sense versuses using ~/ which is like...
ugh... don't program while sleepy kids.
|
|
I think it may be built into the software, or just a sideeffect of
ignoring .git - there doesn't SEEM to be anything I can do bypass this -
so the EASIEST thing to do is simply revert back to using dot-gitignore
which I had before. But since there is the .config folder issue - I am
going to make this the only file using dot- . Which is fine, sine
.gitignore in a repo TYPICALLY is specific to that repository anyway
|
|
I've copied the preliminary list of configurations over from the old
repo as well as some probably unnecessary globablly, local files
(oversteer) - but I mean it REALLY cannot hurt to have a simple .ini
file on a computer.
But I may look into having PC branches that are rebased off of master,
but it may make merging harder? so IDK. Risky.
Anyway. The README.org committed has all you need to know. But for
posterity the reason I am using org-mode files for the README is I am
seeing how test driving emacs goes. Very easily can swap this over to a
markdown file. Just figure - why not.
|