Support non-newline glossary term separator(s)

Petri Savolainen avatarPetri Savolainen created an issue

The current way of expressing multiple term variations is:

   .. glossary::

      term 1
      term 2
         Definition of both terms.

This can be suboptimal when there are several terms; in such a case there will be several lines (all terms) highlighted. A nicer, more readable alternative way to express could be:

   .. glossary::

      term 1 | term 2
         Definition of both terms.

A different term separator could be chosen of course; for example a comma or (forward) slash would be fine as well. Or allow all three, as they are all commonly used in computing to list alternative tokens.

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.