Start with an empty file, and type
:let@a='q:' @a
It should execute the command q:, opening the command-line window. However the q is ignored.
I believe this is because: "The 'q' command is disabled while executing a register, and it doesn't work inside a mapping and :normal." (from :h q)
However, q: does work from inside :normal, and it should work while executing a register. The behaviour for q? and q/ is the same
9.2.316
Arch Linux
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
It is clearly stated in the documentation.
:h q:
OPEN *c_CTRL-F* *q:* *q/* *q?*
(snip...)
Note that this is not possible while recording is in progress (the "q" stops recording then).
However, it is currently possible to do this via the command line, not directly through the command line window.
Use :<C-F> instead of q:.
Similarly,
q/ --> /<C-F>
q? --> ?<C-F>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I’m afraid you have misread something. I am trying to us q: while executing a register, not “while recording is in progress”. I currently do not see a reason why this should be disallowed
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Changing the behavior of q when executing a register is not backward compatible. Why doesn't you use :call feedkeys(@a, 'i') instead?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Thankyou. I was not aware that this would be backwards incompatible. Is there a reason that the expression register @= allows q:?
If it’s definitely backwards incompatible, I will close this issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I edited the comment to add an example.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()