Skip to content

Fails with command substitution #2

@SnoringFrog

Description

@SnoringFrog

If command substitution is used in the final directory/file, follow cannot follow it. If the command references a file, it can be ignored and the containing directory can be followed into. If the command references a directory, however, if can only be followed if the command is guaranteed to produce the same output.

Potential solutions:

  • Attempt to run the command again, just warn in docs that things may get weird if you're using things like project_name_generator or if the command has side effects (consider rm ./$(get-largest-dir-in-dir))
  • Ignore command substitution, try to follow any dirs leading up to the command substitution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions