markdown: Add settings_text command

GitHub Issue dovecot#1008

README.md

@@ -240,14 +240,24 @@ Links to the RFC page (external).
 #### Settings
 
 ***Syntax: `[[setting,setting_name(,args)]]`***
+***Syntax: `[[setting_text,setting_name(,text)]]`***
 
-If args is set, it is appended to the display as a setting value. Example:
+For the `setting` variant, if args is set, it is appended to the display as a
+setting value. Example:
 
 ```
 # [[setting,foo,5]] results in:
 <a href="PATH_TO_FOO_SETTING">foo = 5</a>
 ```
 
+For the `setting_text` variant, if text is set, it is used as the link text.
+Example:
+
+```
+# [[setting_text,foo,bar]] results in:
+<a href="PATH_TO_FOO_SETTING">bar</a>
+```
+
 #### Variable
 
 ***Syntax: `[[variable(,section)]]`***

lib/markdown.js

@@ -156,6 +156,7 @@ function dovecot_markdown(md, opts) {
 		case 'doveadm':
 		case 'event':
 		case 'setting':
+		case 'setting_text':
 			env.inner = parts[1]
 			env.args = parts[2] ? parts[2] : undefined;
 
@@ -179,6 +180,7 @@ function dovecot_markdown(md, opts) {
 				break
 
 			case 'setting':
+			case 'setting_text':
 				/* Settings names can have brackets, so we need to unescape
 				 * input for purposes of searching settings keys. */
 				const search_str = env.inner.replaceAll('&gt;', '<')
@@ -188,7 +190,7 @@ function dovecot_markdown(md, opts) {
 					handle_error('setting link missing: ' + env.inner)
 					return '<code><a>'
 				}
-				page += 's'
+				page = 'settings'
 				break
 			}
 
@@ -333,6 +335,9 @@ function dovecot_markdown(md, opts) {
 		case 'setting':
 			return env.inner + (env.args ? ' = ' + env.args : '')
 
+		case 'setting_text':
+			return env.args ?? env.inner
+
 		case 'variable':
 			return env.inner
 
@@ -356,6 +361,7 @@ function dovecot_markdown(md, opts) {
 		case 'event':
 		case 'man':
 		case 'setting':
+		case 'setting_text':
 		case 'variable':
 			return '</a></code>'