fish-shell/doc_src/realpath.txt

\section realpath realpath - Convert a path to an absolute path without symlinks

\subsection realpath-synopsis Synopsis
\fish{synopsis}
realpath path
\endfish

\subsection realpath-description Description

This is implemented as a function and a builtin. The function will attempt to use an external realpath command if one can be found. Otherwise it falls back to the builtin.  The builtin does not support any options. It's meant to be used only by scripts which need to be portable. The builtin implementation behaves like GNU realpath when invoked without any options (which is the most common use case). In general scripts should not invoke the builtin directly. They should just use `realpath`.

If the path is invalid no translated path will be written to stdout and an error will be reported.
make fish's realpath compatible with GNU realpath After implementing `builtin fish_realpath` it was noticed that it did not behave like GNU `realpath` without options. Which is super annoying since that was the whole point of implementing the command. Major failure on my part since I wrote the unit tests to match the behavior of the existing `wrealpath()` function that I simply exposed as a builtin command. Rather than actually verifying it behaved in a manner compatible with GNU realpath. Also, while the decision to call the builtin `fish_realpath` seemed to make sense at the time of the original commit further reflection has shown that to be a silly, idiosyncratic, thing to have done. So rename it to simply `realpath`. Fixes 3400 2016-10-04 00:51:27 +00:00			`\section realpath realpath - Convert a path to an absolute path without symlinks`

			`\subsection realpath-synopsis Synopsis`
			`\fish{synopsis}`
			`realpath path`
			`\endfish`

			`\subsection realpath-description Description`

			This is implemented as a function and a builtin. The function will attempt to use an external realpath command if one can be found. Otherwise it falls back to the builtin. The builtin does not support any options. It's meant to be used only by scripts which need to be portable. The builtin implementation behaves like GNU realpath when invoked without any options (which is the most common use case). In general scripts should not invoke the builtin directly. They should just use `realpath`.

			`If the path is invalid no translated path will be written to stdout and an error will be reported.`