From 44c2395143406108356f1ed1657ed16354a9951a Mon Sep 17 00:00:00 2001 From: Stephane Zermatten Date: Wed, 11 Sep 2024 16:13:52 +0300 Subject: [PATCH] Mention the backward search/forbid edit mode in the doc. --- docs/source/usage.rst | 38 +++++++++- mistty.texi | 163 ++++++++++++++++++++++++++---------------- 2 files changed, 136 insertions(+), 65 deletions(-) diff --git a/docs/source/usage.rst b/docs/source/usage.rst index 0f7497d..8179086 100644 --- a/docs/source/usage.rst +++ b/docs/source/usage.rst @@ -137,8 +137,7 @@ directly to the terminal, bypassing Emacs: :kbd:`C-p` to the terminal. - :kbd:`M-n` to ask it to go down, or down the command history, sending :kbd:`C-n` to the terminal. -- :kbd:`M-r` to ask it to do backward history search, sending - :kbd:`C-r` to the terminal. +- :kbd:`M-r` to ask it to do :ref:`bs`, sending :kbd:`C-r` to the terminal. - :kbd:`M-.` to ask the shell to insert the last history argument. In addition, :kbd:`C-c C-c` sends the TERM signal to the terminal. @@ -311,7 +310,7 @@ available in MisTTY using the following shortcuts: - :kbd:`M-p` moves up command history - :kbd:`M-n` moves down command history -- :kbd:`M-r` triggers a backward search in command history +- :kbd:`M-r` triggers a :ref:`bs` in command history - :kbd:`M-.` insert the last argument from command history To get the same key bindings you'd get in a normal terminal, you can @@ -324,6 +323,39 @@ in the terminal zone of the MisTTY buffer. For example: (keymap-set mistty-prompt-map "C-n" #'mistty-send-key) (keymap-set mistty-prompt-map "C-r" #'mistty-send-key) +.. _bs: + +Backward Search +--------------- + +.. index:: + pair: map; mistty-forbid-edit-map + pair: variable; mistty-forbid-edit-regexps + pair: variable; mistty-forbid-edit-map + +Within the different shells :kbd:`C-r` or :kbd:`M-r` triggers a +special backward search mode, during which edition is very limited. +MisTTY detects this mode based on the regular expressions configured +in :kbd:`M-x customize-option mistty-forbid-edit-regexps`. + +While this mode is active: + +- text can be appended or deleted, but not modified. While it is still + possible to yank text or delete a word in this mode, most Emacs + edition command will not work. + +- the status modeline shows "FE:run", for Forbid Edit mode + +- arrow keys are sent directly to the terminal. This is useful when + the shell offers multiple choices that can be selected, as the Fish + shell does. To customize this behavior, add or remove key bindings + from :code:`mistty-forbid-edit-map`, which extends + :code:`mistty-prompt-map` while this mode is active. + +- C-g is forwarded to the terminal. It normally exits the backward + search mode without selecting anything. + + .. _dirtrack: Directory tracking and TRAMP diff --git a/mistty.texi b/mistty.texi index cda9fa9..3555b5b 100644 --- a/mistty.texi +++ b/mistty.texi @@ -151,6 +151,7 @@ command-line. * Navigating the scrollback zone:: * Fullscreen Mode:: * Command History:: +* Backward Search:: * Directory tracking and TRAMP:: * Completion-at-point:: * Template Expansion:: @@ -352,8 +353,7 @@ program. sending @code{C-n} to the terminal. @item -@code{M-r} to ask it to do backward history search, sending -@code{C-r} to the terminal. +@code{M-r} to ask it to do @ref{e,,Backward Search}, sending @code{C-r} to the terminal. @item @code{M-.} to ask the shell to insert the last history argument. @@ -372,7 +372,7 @@ MisTTY will not work if you’ve configured your shell to turn on `VI mode' by default. Please `turn it off' before trying out MisTTY, for details on how to turn off VI mode only of MisTTY buffers and leave it on otherwise, check out the instructions in -@ref{e,,Shells} for details. VI mode must be turned off even if you +@ref{f,,Shells} for details. VI mode must be turned off even if you just end up controlling it with VI commands using Evil. @end quotation @end cartouche @@ -463,7 +463,7 @@ you press to the terminal until you press @code{C-g}. @end quotation @node Navigating the scrollback zone,Fullscreen Mode,Terminal vs Scrollback,Usage -@anchor{usage navigating-the-scrollback-zone}@anchor{f}@anchor{usage navigation}@anchor{10} +@anchor{usage navigating-the-scrollback-zone}@anchor{10}@anchor{usage navigation}@anchor{11} @subsection Navigating the scrollback zone @@ -546,7 +546,7 @@ previous command output. previous command input, that is, the previous prompt. While this is a way of going back the command you’ve previously input, it’s best to use the shell native command history, as discussed in -@ref{11,,Command History}. +@ref{12,,Command History}. @end itemize @geindex command; mistty-goto-next-input @@ -560,7 +560,7 @@ best to use the shell native command history, as discussed in @end quotation @node Fullscreen Mode,Command History,Navigating the scrollback zone,Usage -@anchor{usage fullscreen}@anchor{2}@anchor{usage fullscreen-mode}@anchor{12} +@anchor{usage fullscreen}@anchor{2}@anchor{usage fullscreen-mode}@anchor{13} @subsection Fullscreen Mode @@ -587,8 +587,8 @@ these two. When the program exits, the two buffers are again merged. Note that the output of the full screen app isn’t available in the scrollback. -@node Command History,Directory tracking and TRAMP,Fullscreen Mode,Usage -@anchor{usage command-history}@anchor{13}@anchor{usage history}@anchor{11} +@node Command History,Backward Search,Fullscreen Mode,Usage +@anchor{usage command-history}@anchor{14}@anchor{usage history}@anchor{12} @subsection Command History @@ -608,7 +608,7 @@ available in MisTTY using the following shortcuts: @code{M-n} moves down command history @item -@code{M-r} triggers a backward search in command history +@code{M-r} triggers a @ref{e,,Backward Search} in command history @item @code{M-.} insert the last argument from command history @@ -624,8 +624,47 @@ in the terminal zone of the MisTTY buffer. For example: (keymap-set mistty-prompt-map "C-r" #'mistty-send-key) @end example -@node Directory tracking and TRAMP,Completion-at-point,Command History,Usage -@anchor{usage directory-tracking-and-tramp}@anchor{14}@anchor{usage dirtrack}@anchor{15} +@node Backward Search,Directory tracking and TRAMP,Command History,Usage +@anchor{usage backward-search}@anchor{15}@anchor{usage bs}@anchor{e} +@subsection Backward Search + + +@geindex map; mistty-forbid-edit-map +@geindex variable; mistty-forbid-edit-regexps +@geindex variable; mistty-forbid-edit-map + +Within the different shells @code{C-r} or @code{M-r} triggers a +special backward search mode, during which edition is very limited. +MisTTY detects this mode based on the regular expressions configured +in @code{M-x customize-option mistty-forbid-edit-regexps}. + +While this mode is active: + + +@itemize - + +@item +text can be appended or deleted, but not modified. While it is still +possible to yank text or delete a word in this mode, most Emacs +edition command will not work. + +@item +the status modeline shows “FE:run”, for Forbid Edit mode + +@item +arrow keys are sent directly to the terminal. This is useful when +the shell offers multiple choices that can be selected, as the Fish +shell does. To customize this behavior, add or remove key bindings +from @code{mistty-forbid-edit-map}, which extends +@code{mistty-prompt-map} while this mode is active. + +@item +C-g is forwarded to the terminal. It normally exits the backward +search mode without selecting anything. +@end itemize + +@node Directory tracking and TRAMP,Completion-at-point,Backward Search,Usage +@anchor{usage directory-tracking-and-tramp}@anchor{16}@anchor{usage dirtrack}@anchor{17} @subsection Directory tracking and TRAMP @@ -636,7 +675,7 @@ has to tell MisTTY about it. This is usually done from the prompt. a terminal of type @code{TERM=eterm-color} run from inside Emacs. Other shells need to be configured to do the same. For more details, -see @ref{e,,Shells}. +see @ref{f,,Shells}. @geindex variable; mistty-allow-tramp-path @@ -646,7 +685,7 @@ MisTTY to report remote paths on @code{M-x configure-option mistty-allow-tramp-paths}. @node Completion-at-point,Template Expansion,Directory tracking and TRAMP,Usage -@anchor{usage completion-at-point}@anchor{16} +@anchor{usage completion-at-point}@anchor{18} @subsection Completion-at-point @@ -679,7 +718,7 @@ Emacs @cite{hippie-expand} also works. That’s not completion, but it’s close. Other packages might work or might be made to work with some efforts. -Auto-completion is usually the main challenge. See @ref{17,,Auto-complete} +Auto-completion is usually the main challenge. See @ref{19,,Auto-complete} for some pointers. Please @ref{3,,file a bug} if you encounter issues with other completion packages. @@ -689,7 +728,7 @@ encounter issues with other completion packages. @end menu @node Autosuggestions,,,Completion-at-point -@anchor{usage autosuggestions}@anchor{18} +@anchor{usage autosuggestions}@anchor{1a} @subsubsection Autosuggestions @@ -717,13 +756,13 @@ autosuggestions, you can turn this off with @code{M-x customize-option mistty-wrap-capf-functions} @node Template Expansion,Fancy prompts,Completion-at-point,Usage -@anchor{usage template-expansion}@anchor{19} +@anchor{usage template-expansion}@anchor{1b} @subsection Template Expansion Template expansion and other form of long-running editing command might be confused by the way MisTTY work in the terminal region. See -@ref{1a,,Long-running commands} for details. +@ref{1c,,Long-running commands} for details. The following template expansion packages are known to work with MisTTY out of the box, if enabled: @@ -746,7 +785,7 @@ Please @ref{3,,file a bug} if you encounter issues with other packages. @node Fancy prompts,,Template Expansion,Usage -@anchor{usage fancy-prompts}@anchor{1b} +@anchor{usage fancy-prompts}@anchor{1d} @subsection Fancy prompts @@ -758,7 +797,7 @@ If you suspect your shell prompt is causing issues, please first try setting a traditional prompt to confirm, then @ref{3,,file a bug}, whatever the outcome. @node Shells,Extending MisTTY,Usage,Contents -@anchor{shells doc}@anchor{1c}@anchor{shells id1}@anchor{1d}@anchor{shells shells}@anchor{e} +@anchor{shells doc}@anchor{1e}@anchor{shells id1}@anchor{1f}@anchor{shells shells}@anchor{f} @section Shells @@ -770,7 +809,7 @@ setting a traditional prompt to confirm, then @ref{3,,file a bug}, whatever the @end menu @node Bash,Fish,,Shells -@anchor{shells bash}@anchor{1e}@anchor{shells id2}@anchor{1f} +@anchor{shells bash}@anchor{20}@anchor{shells id2}@anchor{21} @subsection Bash @@ -795,7 +834,7 @@ set enable-bracketed-paste on @end menu @node Multi-line prompts,Directory tracking,,Bash -@anchor{shells multi-line-prompts}@anchor{20} +@anchor{shells multi-line-prompts}@anchor{22} @subsubsection Multi-line prompts @@ -813,7 +852,7 @@ You’ll get the same effect if you yank a multi-line command while in a prompt or go up the command history to a previous multi-line command. @node Directory tracking,VI mode,Multi-line prompts,Bash -@anchor{shells directory-tracking}@anchor{21} +@anchor{shells directory-tracking}@anchor{23} @subsubsection Directory tracking @@ -838,7 +877,7 @@ Such sequence are either ignored or understood by most terminals, so you don’t absolutely need to check TERM. @node VI mode,,Directory tracking,Bash -@anchor{shells vi-mode}@anchor{22} +@anchor{shells vi-mode}@anchor{24} @subsubsection VI mode @@ -867,7 +906,7 @@ fi @end example @node Fish,Zsh,Bash,Shells -@anchor{shells fish}@anchor{23}@anchor{shells id3}@anchor{24} +@anchor{shells fish}@anchor{25}@anchor{shells id3}@anchor{26} @subsection Fish @@ -884,7 +923,7 @@ paste mode, on by default, so it should not be turned off. @end menu @node Autosuggestions<2>,Command History<2>,,Fish -@anchor{shells autosuggestions}@anchor{25} +@anchor{shells autosuggestions}@anchor{27} @subsubsection Autosuggestions @@ -896,7 +935,7 @@ The recommended way of accepting an autosuggestion in MisTTY is to type @code{C-e}. This works in normal terminals as well. @node Command History<2>,Directory tracking<2>,Autosuggestions<2>,Fish -@anchor{shells command-history}@anchor{26} +@anchor{shells command-history}@anchor{28} @subsubsection Command History @@ -931,7 +970,7 @@ use @code{C-q } @code{C-q } @code{C-q } @code{C-q }, or e @end itemize @node Directory tracking<2>,Multi-line prompts<2>,Command History<2>,Fish -@anchor{shells id4}@anchor{27} +@anchor{shells id4}@anchor{29} @subsubsection Directory tracking @@ -952,7 +991,7 @@ such sequence are either ignored or understood by most terminals. You might already have it set up. @node Multi-line prompts<2>,VI mode<2>,Directory tracking<2>,Fish -@anchor{shells id5}@anchor{28} +@anchor{shells id5}@anchor{2a} @subsubsection Multi-line prompts @@ -968,7 +1007,7 @@ mistty-skip-empty-spaces} allows you to turn that on or off in a MisTTY buffer. @node VI mode<2>,,Multi-line prompts<2>,Fish -@anchor{shells id6}@anchor{29} +@anchor{shells id6}@anchor{2b} @subsubsection VI mode @@ -987,7 +1026,7 @@ end @end example @node Zsh,,Fish,Shells -@anchor{shells id7}@anchor{2a}@anchor{shells zsh}@anchor{2b} +@anchor{shells id7}@anchor{2c}@anchor{shells zsh}@anchor{2d} @subsection Zsh @@ -1006,7 +1045,7 @@ unexpected results if you yank text containing special characters. @end menu @node Autosuggestions<3>,Directory tracking<3>,,Zsh -@anchor{shells id8}@anchor{2c} +@anchor{shells id8}@anchor{2e} @subsubsection Autosuggestions @@ -1019,7 +1058,7 @@ The recommended way of accepting an autosuggestion in MisTTY is to type @code{C-e}. This works in normal terminals as well. @node Directory tracking<3>,Multi-line prompts<3>,Autosuggestions<3>,Zsh -@anchor{shells id9}@anchor{2d} +@anchor{shells id9}@anchor{2f} @subsubsection Directory tracking @@ -1036,7 +1075,7 @@ fi such sequence are either ignored or understood by most terminals. @node Multi-line prompts<3>,VI mode<3>,Directory tracking<3>,Zsh -@anchor{shells id10}@anchor{2e} +@anchor{shells id10}@anchor{30} @subsubsection Multi-line prompts @@ -1054,7 +1093,7 @@ You’ll get the same effect if you yank a multi-line command while in a prompt or go up the command history to a previous multi-line command. @node VI mode<3>,,Multi-line prompts<3>,Zsh -@anchor{shells id11}@anchor{2f} +@anchor{shells id11}@anchor{31} @subsubsection VI mode @@ -1073,7 +1112,7 @@ fi @end example @node Extending MisTTY,FAQ,Shells,Contents -@anchor{extensions doc}@anchor{30}@anchor{extensions extending-mistty}@anchor{31} +@anchor{extensions doc}@anchor{32}@anchor{extensions extending-mistty}@anchor{33} @section Extending MisTTY @@ -1088,7 +1127,7 @@ fi @end menu @node Hooks,OSC Sequences,,Extending MisTTY -@anchor{extensions hooks}@anchor{32}@anchor{extensions id1}@anchor{33} +@anchor{extensions hooks}@anchor{34}@anchor{extensions id1}@anchor{35} @subsection Hooks @@ -1103,7 +1142,7 @@ fi @end menu @node mistty-mode-hook,mistty-interactive-insert-hook,,Hooks -@anchor{extensions mistty-mode-hook}@anchor{34} +@anchor{extensions mistty-mode-hook}@anchor{36} @subsubsection mistty-mode-hook @@ -1135,7 +1174,7 @@ you could do: @geindex hook; mistty-interactive-interactive @node mistty-interactive-insert-hook,mistty-after-process-start-hook,mistty-mode-hook,Hooks -@anchor{extensions mistty-interactive-insert-hook}@anchor{35} +@anchor{extensions mistty-interactive-insert-hook}@anchor{37} @subsubsection mistty-interactive-insert-hook @@ -1145,7 +1184,7 @@ for text that is inserted or displayed by the shell. This hook provides an appropriate time to trigger auto-completion UI, which, by default, doesn’t work in the terminal region, as discussed -in @ref{17,,Auto-complete}. +in @ref{19,,Auto-complete}. Auto-completion doesn’t work in the terminal region because it often requires calling a post-command function. To work around that, in most @@ -1159,7 +1198,7 @@ prefer to trigger the auto-completion UI yourself by adding your own function to this hook and turning the above option off. @node mistty-after-process-start-hook,mistty-after-process-end-hook,mistty-interactive-insert-hook,Hooks -@anchor{extensions mistty-after-process-start-hook}@anchor{36} +@anchor{extensions mistty-after-process-start-hook}@anchor{38} @subsubsection mistty-after-process-start-hook @@ -1170,7 +1209,7 @@ usually a shell. The process itself is available as typically empty, as no output from the process has been processed. @node mistty-after-process-end-hook,mistty-entered-fullscreen-hook,mistty-after-process-start-hook,Hooks -@anchor{extensions mistty-after-process-end-hook}@anchor{37} +@anchor{extensions mistty-after-process-end-hook}@anchor{39} @subsubsection mistty-after-process-end-hook @@ -1189,7 +1228,7 @@ the shell exits successfully, with @code{mistty-kill-buffer} or @end example @node mistty-entered-fullscreen-hook,mistty-left-fullscreen-hook,mistty-after-process-end-hook,Hooks -@anchor{extensions mistty-entered-fullscreen-hook}@anchor{38} +@anchor{extensions mistty-entered-fullscreen-hook}@anchor{3a} @subsubsection mistty-entered-fullscreen-hook @@ -1202,7 +1241,7 @@ run within the terminal buffer, available as buried until @code{mistty-toggle-buffers} is called. @node mistty-left-fullscreen-hook,,mistty-entered-fullscreen-hook,Hooks -@anchor{extensions mistty-left-fullscreen-hook}@anchor{39} +@anchor{extensions mistty-left-fullscreen-hook}@anchor{3b} @subsubsection mistty-left-fullscreen-hook @@ -1213,7 +1252,7 @@ In this mode, @code{mistty-fullscreen} is nil and user commands run in the work buffer. @node OSC Sequences,Writing Your Own Commands,Hooks,Extending MisTTY -@anchor{extensions osc}@anchor{3a}@anchor{extensions osc-sequences}@anchor{3b} +@anchor{extensions osc}@anchor{3c}@anchor{extensions osc-sequences}@anchor{3d} @subsection OSC Sequences @@ -1221,7 +1260,7 @@ OSC are “operating system command” control sequences. MisTTY supports some of these sequences and ignores the others. By default, the supported sequences are OSC 2 (set window title), 7 -(directory tracking, already mentioned in @ref{15,,Directory tracking and TRAMP}) and 8 +(directory tracking, already mentioned in @ref{17,,Directory tracking and TRAMP}) and 8 (hyperlinks), thanks to @code{ansi-osc.el}. @geindex variable; mistty-osc-handlers @@ -1258,7 +1297,7 @@ same argument. @end itemize @node Writing Your Own Commands,Terminal Keymap,OSC Sequences,Extending MisTTY -@anchor{extensions custom-commands}@anchor{3c}@anchor{extensions writing-your-own-commands}@anchor{3d} +@anchor{extensions custom-commands}@anchor{3e}@anchor{extensions writing-your-own-commands}@anchor{3f} @subsection Writing Your Own Commands @@ -1314,7 +1353,7 @@ to that position. @end itemize @node Terminal Keymap,Auto-complete,Writing Your Own Commands,Extending MisTTY -@anchor{extensions term-keymap}@anchor{3e}@anchor{extensions terminal-keymap}@anchor{3f} +@anchor{extensions term-keymap}@anchor{40}@anchor{extensions terminal-keymap}@anchor{41} @subsection Terminal Keymap @@ -1364,7 +1403,7 @@ keymap that simulates rxvt, you might do: distribution; it’s only available on github@footnote{https://github.com/szermatt/mistty/tree/master/extras}. @node Auto-complete,Long-running commands,Terminal Keymap,Extending MisTTY -@anchor{extensions auto-complete}@anchor{40}@anchor{extensions autocomplete}@anchor{17} +@anchor{extensions auto-complete}@anchor{42}@anchor{extensions autocomplete}@anchor{19} @subsection Auto-complete @@ -1374,7 +1413,7 @@ Auto-complete is a completion UI that shows up automatically after some delay, without having to call @cite{completion-at-point}. This used not to work in MisTTY terminal region. The hook @code{mistty-simulates-self-insert-command} was introduced to fix -that. See @code{mistty-interactive-insert-hook} in @ref{32,,Hooks}. +that. See @code{mistty-interactive-insert-hook} in @ref{34,,Hooks}. By default this hook calls the buffer @code{pre-command-hook} and @code{post-command-hook} with @code{this-command} set to @@ -1388,7 +1427,7 @@ should be possible to build a custom bridge between this hook and the auto-completion package. @node Long-running commands,,Auto-complete,Extending MisTTY -@anchor{extensions long-running-commands}@anchor{41}@anchor{extensions lrc}@anchor{1a} +@anchor{extensions long-running-commands}@anchor{43}@anchor{extensions lrc}@anchor{1c} @subsection Long-running commands @@ -1470,7 +1509,7 @@ Here’s an example of code that would detect @end example @node FAQ,Contributing,Extending MisTTY,Contents -@anchor{faq doc}@anchor{42}@anchor{faq faq}@anchor{43} +@anchor{faq doc}@anchor{44}@anchor{faq faq}@anchor{45} @section FAQ @@ -1524,7 +1563,7 @@ mistty-detect-foreign-overlays} or, if you know which package is causing trouble, remove the corresponding property in in @code{M-x customize-option mistty-foreign-overlay-properties}. -For details, see @ref{1a,,Long-running commands} +For details, see @ref{1c,,Long-running commands} If this keeps happening and the modeline does not contain CMD, this is likely a bug. Please see @ref{3,,Reporting issues} for details on @@ -1570,10 +1609,10 @@ than just editing text. One such issue is with interactivly editing the buffer over multiple Emacs command, which MisTTY calls a long-running command. There are ways of making such commands work if they don’t already, -described in @ref{1a,,Long-running commands}. +described in @ref{1c,,Long-running commands}. Another such issue is with autocomplete, with can also be made to -work as described in @ref{17,,Auto-complete}. +work as described in @ref{19,,Auto-complete}. While this works with some packages, it might not necessarily work with the package you want - it might even not be possible to make @@ -1586,18 +1625,18 @@ such a package you’d like to work with MisTTY. @quotation Older versions used to detect any unknown overlay as a -long-running command, described in @ref{1a,,Long-running commands}. Unfortunately, this +long-running command, described in @ref{1c,,Long-running commands}. Unfortunately, this caused problems with many packages which, leaving overlays around for a long time, prevented MisTTY from working at all. The good news is that it’s likely easy to make it work again by detecting the specific kind of overlays the package is using. -Please see @ref{1a,,Long-running commands} or file a bug@footnote{https://github.com/szermatt/mistty/issues} mentioning the +Please see @ref{1c,,Long-running commands} or file a bug@footnote{https://github.com/szermatt/mistty/issues} mentioning the package you’re using, its version and how you installed it. @end quotation @node Contributing,,FAQ,Contents -@anchor{contrib doc}@anchor{44}@anchor{contrib contributing}@anchor{45} +@anchor{contrib doc}@anchor{46}@anchor{contrib contributing}@anchor{47} @section Contributing @@ -1611,7 +1650,7 @@ package you’re using, its version and how you installed it. @end menu @node Reporting issues,Suggesting features,,Contributing -@anchor{contrib reporting}@anchor{3}@anchor{contrib reporting-issues}@anchor{46} +@anchor{contrib reporting}@anchor{3}@anchor{contrib reporting-issues}@anchor{48} @subsection Reporting issues @@ -1695,21 +1734,21 @@ anything private, and include it into the issue. @end itemize @node Suggesting features,Asking questions,Reporting issues,Contributing -@anchor{contrib issue-tracker}@anchor{47}@anchor{contrib suggesting-features}@anchor{48} +@anchor{contrib issue-tracker}@anchor{49}@anchor{contrib suggesting-features}@anchor{4a} @subsection Suggesting features Please add feature suggestions to the Issue Tracker@footnote{https://github.com/szermatt/mistty/issues}. @node Asking questions,Code contributions,Suggesting features,Contributing -@anchor{contrib asking-questions}@anchor{49} +@anchor{contrib asking-questions}@anchor{4b} @subsection Asking questions Open an issue on the Issue Tracker@footnote{https://github.com/szermatt/mistty/issues} with your question. @node Code contributions,Documentation contributions,Asking questions,Contributing -@anchor{contrib code-contributions}@anchor{4a} +@anchor{contrib code-contributions}@anchor{4c} @subsection Code contributions @@ -1727,7 +1766,7 @@ tests passing reliably when run using @code{eldev test} is what matters. @node Documentation contributions,,Code contributions,Contributing -@anchor{contrib documentation-contributions}@anchor{4b}@anchor{contrib eldev}@anchor{4c} +@anchor{contrib documentation-contributions}@anchor{4d}@anchor{contrib eldev}@anchor{4e} @subsection Documentation contributions