docs + images + fix nojs README + fixed open image autodetection

app/app.go

@@ -15,7 +15,7 @@ const (
  version = "%d.%d.%d"
  Major = 6
  Minor = 1
- Revision = 8210
+ Revision = 8220
 )
 
 // Copyright is the copyright owner string

config/defaults/profile_any.mx

@@ -688,21 +688,21 @@ openagent set image {
 
  if { $mode == "auto" } {
  switch {
- case { $TMUX } { mode = compatible }
- case { $MXTTY } { mode = mxtty } 
- case { $ITERM_PROFILE } { mode = iterm }
- case { $TERM_PROGRAM == "iTerm.app" } { mode = iterm }
- case { $KITTY_WINDOW_ID } { mode = kitty }
- case { $TERM == "xterm-kitty" } { mode = kitty }
- case { $TERMINOLOGY } { mode = terminology }
- catch { mode = compatible }
+ case { $TMUX } { $mode = "compatible" }
+ case { $MXTTY } { $mode = "mxtty" } 
+ case { $ITERM_PROFILE } { $mode = "iterm" }
+ case { $TERM_PROGRAM == "iTerm.app" } { $mode = "iterm" }
+ case { $KITTY_WINDOW_ID } { $mode = "kitty" }
+ case { $TERM == "xterm-kitty" } { $mode = "kitty" }
+ case { $TERMINOLOGY } { $mode = "terminology" }
+ catch { $mode = "compatible" }
  }
  }
 
  # If Kitty but running inside a screen / tmux session, fallback to compatible.
  # We do this because tmux doesn't support reporting screen sizes via the TIOCGWINSZ ioctl.
  if { $mode == "kitty" && $TERM == "screen" } {
- set mode=compatible
+ $mode = "compatible"
  }
 
  switch $mode {

docs/changelog/v6.1.md

@@ -91,6 +91,8 @@ Features marked as **EXPERIMENTAL** are provided without assurances of future br
 * readline: include errors in preview
 
 * profile: `openagent` for `image` data type wasn't passing path to image correctly
+
+* profile: `openagent` for `image` data type wasn't autodetecting shell correctly
 
 * profile: `openagent` default profile included references to deprecated maths lib
 

docs/integrations/iterm2.md

@@ -18,6 +18,12 @@ terminal. Normally that would be a blocky "pixellated" representation using
 block characters. But if you're running iTerm2, Murex will automatically switch
 to iTerm2's ANSI escape sequences to render those images beautifully.
 
+For example:
+
+```
+open https://murex.rocks/git-autocomplete.png
+```
+
 ## See Also
 
 * [Kitty Integrations](../integrations/kitty.md):

docs/integrations/kitty.md

@@ -18,6 +18,8 @@ terminal. Normally that would be a blocky "pixellated" representation using
 block characters. But if you're running Kitty, Murex will automatically switch
 to Kitty's ANSI escape sequences to render those images beautifully.
 
+![opening an image in Kitty](https://nojs.murex/rocks/images/screenshot-kitty-open.png)
+
 ## See Also
 
 * [Terminology Integrations](../integrations/terminology.md):

docs/integrations/terminology.md

@@ -19,6 +19,8 @@ block characters. But if you're running Terminology, Murex will automatically
 switch to Terminology's ANSI escape sequences to render those images
 beautifully.
 
+![opening an image in Kitty](https://nojs.murex/rocks/images/screenshot-terminology-open.png)
+
 ## See Also
 
 * [Kitty Integrations](../integrations/kitty.md):

gen/changelog/v6.1.inc.md

@@ -87,6 +87,8 @@ Features marked as **EXPERIMENTAL** are provided without assurances of future br
 * readline: include errors in preview
 
 * profile: `openagent` for `image` data type wasn't passing path to image correctly
+
+* profile: `openagent` for `image` data type wasn't autodetecting shell correctly
 
 * profile: `openagent` default profile included references to deprecated maths lib
 

gen/integrations/iterm2_doc.yaml

@@ -20,6 +20,12 @@
  terminal. Normally that would be a blocky "pixellated" representation using
  block characters. But if you're running iTerm2, Murex will automatically switch
  to iTerm2's ANSI escape sequences to render those images beautifully.
+
+ For example:
+
+ ```
+ open https://murex.rocks/git-autocomplete.png
+ ```
  Synonyms:
  Related:
  - open

gen/integrations/kitty_doc.yaml

@@ -20,6 +20,8 @@
  terminal. Normally that would be a blocky "pixellated" representation using
  block characters. But if you're running Kitty, Murex will automatically switch
  to Kitty's ANSI escape sequences to render those images beautifully.
+
+ ![opening an image in Kitty](https://nojs.murex/rocks/images/screenshot-kitty-open.png)
  Synonyms:
  Related:
  - open

gen/integrations/terminology_doc.yaml

@@ -21,6 +21,8 @@
  block characters. But if you're running Terminology, Murex will automatically
  switch to Terminology's ANSI escape sequences to render those images
  beautifully.
+
+ ![opening an image in Kitty](https://nojs.murex/rocks/images/screenshot-terminology-open.png)
  Synonyms:
  Related:
  - open

gen/user-guide/hint-text-overview.inc.md

@@ -5,7 +5,13 @@ to be used if you want it while keeping out of the way when you don't want it.
 
 {{ if env "DOCGEN_TARGET=vuepress" }}
 <!-- markdownlint-disable -->
-<img src="/screenshot-hint-text-rsync.png?v={{ env "COMMITHASHSHORT" }}" class="centre-image"/>
-<img src="/screenshot-hint-text-egrep.png?v={{ env "COMMITHASHSHORT" }}" class="centre-image"/>
+<figure>
+ <img src="/screenshot-hint-text-rsync.png?v={{ env "COMMITHASHSHORT" }}" class="centre-image"/>
+ <figcaption>`rsync` flag, with example, pulled from `man` pages ({{link "read more" "man-pages"}})</figcaption>
+</figure>
+<figure>
+ <img src="/screenshot-hint-text-egrep.png?v={{ env "COMMITHASHSHORT" }}" class="centre-image"/>
+ <figcaption>`egrep` is an {{link "alias" "alias"}} so also show the destination command</figcaption>
+</figure> 
 <!-- markdownlint-restore -->
 {{ end }}

gen/website/find-exec.mx

@@ -34,4 +34,4 @@
 #catch {
 # err "Could not write $filename ($title)"
 # exit 1
-#}
+#}

test/ci-website.sh

@@ -51,6 +51,7 @@ done
 find docs -name "*.md" -exec murex gen/website/find-exec.mx {} \;
 
 sed -i '0,/<img src/s//<img class="no-border" src/;
+ 0,/<img src/s//<img class="no-border" src/;
  0,/<img src/s//<img class="no-border" src/;
  0,/<img src/s//<img class="no-border" src/;' \
  README.html