Allow easy navigation to function definitions in emacs.
The rg (ripgrep) search is needed because as the dumb-jump README says:
[...] the default searcher (git-grep) won't be able to search
outside of the project root. This edge case will be fixed in a
future release.
See: https://github.com/jacktasia/dumb-jump
We no longer need to ensure that texi2any (a.k.a. makeinfo) is called
with -I $(srcdir) in order to make the
@verbatiminclude default-ignore-list
in the manual work, because texi2any includes the current working
directory by default anyway. Presumably this behaviour was introduced
after this AM_MAKEINFOFLAGS was previously added, because it was
needed at some point in the past.
This should have been part of 182acbbb64
when the option was first added.
This commit basically just copies the help text from stow.in into the
texinfo manual.
Problem was that when running stow_contents/unstow_contents recursively from
stow_node/unstow_node the information for the source path (without the dot- to
. transformation) was lost.
In the case of stow_contents the solution is just to remove the leading
dots (..) from the $source path (since the $source path is passed as an argument
to the function)
In the case of unstow_contents the solution is the same as for stow_contents but
the arguments was now passed so I added it to the function.
This avoids errors like
fatal: You are pushing to remote 'savannah', which is not the upstream of
your current branch 'master', without telling me what to push
to update which remote branch.
Under emacs, this was previously rendered as
'--no-folding'
This disables any further *note tree folding:: or *note tree
refolding::. If a new subdirectory is encountered whilst stowing a
which looks awkward. Similarly under info(1):
'--no-folding'
This disables any further *note tree folding:: or *note tree
refolding::. If a new subdirectory is encountered whilst stowing a
The new way is undesirably repetitive, but at least grammatically
correct. I don't think there's a better solution with texinfo :-/
It doesn't make sense to have docs online relating to a release which
isn't yet available; it's less confusing to have a small time window
in which the online docs are out of date.
