to not expose the trapping BIF in the stacktrace
when it throws badarg.

Most notes.xml files will be updated in every release and cause
the kind of the problems described in the previous commit.

In Emacs it is possible to remotely edit a file, by opening for
example /ssh:somehost.com:/path/to/file.erl.  In Emacs, the feature
that makes this possible, is called TRAMP.  When compiling such a file,
by typing C-c C-k, an inferior Erlang shell is opened on the remote
host, but the compilation expression that was evaluated in the remote
Erlang shell was:

   c("/ssh:somehost.com:/path/to/file", [...]).

which resulted in a "no such file or directory" error.
This commit changes the compilation expression into:

   c("/path/to/file", [...]).

for files opened remotely via TRAMP.  The file name is adjusted
similarly when compiling .yrl and .xrl files.

In a buffer opened remotely, the Elisp function buffer-file-name
returns the full path with TRAMP syntax.  In this example it would
be "/ssh:somehost.com:/path/to/file.erl".  A new function,
erlang-local-buffer-file-name, has been introduced, which peels off
the TRAMP syntax on remotely opened files, while for locally opened
files, it just calls buffer-file-name.

* mh/line-initial-commas/OTP-11242:
  Inside parentheses, line-initial commas align with the open parenthesis

For example:

  [ one
  , two
  , three
  ]

This does not affect coding styles that don't put commas at the
beginning of lines.

* egil/increase-eprof-usability/OTP-11144:
  tools: Document new eprof options
  tools: Add options to eprof
  tools: Add testcase to eprof_SUITE
  tools: Refactor away ?line macro in eprof_SUITE