-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Use sources as variable #948
Comments
Hi @NVolcz, This indeed makes sense, because we already have other special variables like Implementation note: this variable should probably be an array (slice) because them users will have more flexibility on what to do with it (join with space or |
I think this might help with a use-case I'm looking at now. edit: never mind, a colleague came up with a pattern for what I want to do that works quite well as-is:
|
Wonder if this is the only possible solution. May I suggest:
IMHO this would be more flexible since it would let any variable be usable based on filename expansion. |
For a task, is the list of files specified in sources available for commands so it can be used as a variable?
I have a script that that I would like to pass the list of sources available to:
Alternatively if it was possible to use vars for sources:
The text was updated successfully, but these errors were encountered: