There are two lists in LaTeX for stuff like verbatim:
\verb and environment verbatim are using a general list \dospecials. Each element is a pair, \do followed by a one-character command.
\index and \glossary are using \@sanitize. Each element is a pair,
\@makeother followed by the one-character command.
The following adds support for a new active / to both commands:
\makeatletter
\g@addto@macro\dospecials{\do\/}
\g@addto@macro\@sanitize{\@makeother\/}
\makeatother
BTW: \verb§/§
§ is a little dangerous beast regarding the input encoding. The character needs two bytes in encoding UTF-8. Then it will only work in LuaTeX/XeTeX,
whereas TeX/pdfTeX will see two bytes and the first byte is used as delimiter.
The problem is not visible with output font encoding OT1 and without inputenc, because the
8-bit bytes are not set because of the 7-bit fonts. With \tracinglostchars=2 this can be seen as warnings:
Missing character: There is no � in font cmtt10!
Missing character: There is no � in font cmr10!
The first is the second byte of the first § inside the verbatim text, the second is the second byte of the closing § outside, because the first byte was used as delimiter.
If \usepackage[utf8]{inputenc} is in use, then the disrupted second byte will cause errors:
! Package inputenc Error: Keyboard character used is undefined
(inputenc) in inputencoding `utf8'.
§is that it means different things at different times, by default it's an unsupported punctuation character, if you use inputenc it will (like all 8bit characters) be made active, if you use latin1 encoding it is a single token, if you use utf8 encoding with inputenc it is two tokens, if you use utf8 with xetex it is one token, so for example your\def§would fail if you defined it before loadinginputenc– David Carlisle Sep 02 '14 at 13:06|and+being used often. Are these the recommended delimiters? – FK82 Sep 02 '14 at 14:24