Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/fix/Fix-User-Guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,4 +298,4 @@ You can use path wildcards to select fields matching a pattern. They only match

#### File paths

Some Fix functions can refer to files on your system. Paths are by default relative to the current working directory. Paths can always be stated in UNIX style - even when running Metafacture under Windows. If using Windows style you have to escape the backslashes (`C:\my\path` > `C:\\my\\path`). If you want to address files relative to the Fix file add `.` as directory (`./myFile`). To address files relative to the location of the executed Flux file, use the predefined `FLUX_DIR` variable, but you need to add the `*` to the `fix` command in the Flux (see above). You can also use `..` for the parent directory.
Some Fix functions can refer to files on your system. Paths are by default relative to the current working directory. Paths can always be stated in UNIX style - even when running Metafacture under Windows. If using Windows style you have to escape the backslashes (`C:\my\path` > `C:\\my\\path`). If you want to address files relative to the Fix file add `.` as directory (`./myFile`). To address files relative to the location of the executed Flux file, use the predefined `FLUX_DIR` variable, but you need to add the `*` to the `fix` command in the Flux (see above). You can also use `..` for the parent directory. At the beginning `..` is relative to the Fix file and can be used multiple times in order to relate to parent directories of parent directories (`../../myFile` relates to a file two parent directories up from the fix file.)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Some Fix functions can refer to files on your system. Paths are by default relative to the current working directory. Paths can always be stated in UNIX style - even when running Metafacture under Windows. If using Windows style you have to escape the backslashes (`C:\my\path` > `C:\\my\\path`). If you want to address files relative to the Fix file add `.` as directory (`./myFile`). To address files relative to the location of the executed Flux file, use the predefined `FLUX_DIR` variable, but you need to add the `*` to the `fix` command in the Flux (see above). You can also use `..` for the parent directory. At the beginning `..` is relative to the Fix file and can be used multiple times in order to relate to parent directories of parent directories (`../../myFile` relates to a file two parent directories up from the fix file.)
Some Fix functions can refer to files on your system. Paths are by default relative to the current working directory. Paths can always be stated in UNIX style - even when running Metafacture under Windows. If using Windows style, you have to escape the backslashes (`C:\my\path` > `C:\\my\\path`). If you want to address files relative to the Fix file, add `.` as directory (`./myFile`). To address files relative to the location of the executed Flux file, use the predefined `FLUX_DIR` variable, but you need to add the `*` to the `fix` command in the Flux (see above). You can also use `..` for the Fix file's parent directory (can be used multiple times in order to refer to parent directories of parent directories, e.g. `../../myFile` refers to a file two parent directories up from the Fix file).