Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible issue with use of --wrap #144

Open
JasonCust opened this issue Dec 1, 2020 · 0 comments
Open

Possible issue with use of --wrap #144

JasonCust opened this issue Dec 1, 2020 · 0 comments

Comments

@JasonCust
Copy link

JasonCust commented Dec 1, 2020

This is either a lack of documentation (leading to a lack of understanding) or a bug. I have been trying to use the --wrap option for argbash-init but it doesn't seem to have any effect.

$ argbash-init --opt environment --opt name -m full foo.m4
$ argbash-init --pos foobar --wrap foo.m4 -m full bar.m4
$ cat bar.m4
#!/bin/bash

# m4_ignore(
echo "This is just a script template, not the script (yet) - pass it to 'argbash' to fix this." >&2
exit 11  #)Created by argbash-init v2.10.0
# ARG_POSITIONAL_SINGLE([foobar])
# ARGBASH_SET_DELIM([ =])
# ARG_OPTION_STACKING([getopt])
# ARG_RESTRICT_VALUES([no-local-options])
# ARG_DEFAULTS_POS
# ARG_HELP([<The general help message of my script>])
# ARGBASH_GO

# [ <-- needed because of Argbash

# vvv  PLACE YOUR CODE HERE  vvv
# For example:
printf "Value of '%s': %s\\n" 'foobar' "$_arg_foobar"

# ^^^  TERMINATE YOUR CODE BEFORE THE BOTTOM ARGBASH MARKER  ^^^

# ] <-- needed because of Argbash

Expected outcome is the bar.m4 file would include a # ARGBASH_WRAP(...) line but it doesn't. Am I misunderstanding how to use --wrap?

EDIT: I've tried using both --wrap foo.m4 and --wrap foo as the underlying ARGBASH_WRAP says to use the filename stem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant