How do I check if Vim is currently recording a macro?

Clash Royale CLAN TAG#URR8PPP

up vote
5
down vote

favorite

Is there a way to programmatically check if Vim is currently in the recording mode triggered by q?

edited Aug 7 at 2:07

Peter Mortensen

1626

asked Aug 6 at 10:12

wengwengweng

508

add a commentÂ |Â

up vote
5
down vote

favorite

Is there a way to programmatically check if Vim is currently in the recording mode triggered by q?

edited Aug 7 at 2:07

Peter Mortensen

1626

asked Aug 6 at 10:12

wengwengweng

508

add a commentÂ |Â

up vote
5
down vote

favorite

Is there a way to programmatically check if Vim is currently in the recording mode triggered by q?

edited Aug 7 at 2:07

Peter Mortensen

1626

asked Aug 6 at 10:12

wengwengweng

508

Is there a way to programmatically check if Vim is currently in the recording mode triggered by q?

edited Aug 7 at 2:07

Peter Mortensen

1626

asked Aug 6 at 10:12

wengwengweng

508

edited Aug 7 at 2:07

Peter Mortensen

1626

edited Aug 7 at 2:07

Peter Mortensen

1626

edited Aug 7 at 2:07

Peter Mortensen

1626

asked Aug 6 at 10:12

wengwengweng

508

asked Aug 6 at 10:12

wengwengweng

508

asked Aug 6 at 10:12

wengwengweng

508

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
13
down vote

accepted

Since Vim 8.1-0020, there is a reg_recording() function that'll return the name of the current register being recorded. An empty string is returned if we are not recording.

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

2

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

add a commentÂ |Â

up vote
3
down vote

Edit I wasn't aware of reg_recording() but if you have a newer version of Vim Luc's answer is clearly the best answer.

I'm not aware of a built-in way to check if Vim is recording but you could use the following workaround in your .vimrc:

let g:isRecording = get(g:, 'isRecording', 0)
nnoremap q :let g:isRecording = !g:isRecording<CR>q

The first line will create a global variable g:isRecording which is falsy by default or takes its existing value if you re-source your .vimrc.

Then you remap q to toggle the value of g:isRecording when it toggles the recording mode and you can then test g:isRecording.

That's not the most elegant solution but as :h recording doesn't seem to mention a variable which would change with q and :h autocmd-events doesn't mention an event related to recording, I guess that the easiest way to do.

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

1

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

1

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "599"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f17011%2fhow-do-i-check-if-vim-is-currently-recording-a-macro%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
13
down vote

accepted

Since Vim 8.1-0020, there is a reg_recording() function that'll return the name of the current register being recorded. An empty string is returned if we are not recording.

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

2

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

add a commentÂ |Â

up vote
13
down vote

accepted

Since Vim 8.1-0020, there is a reg_recording() function that'll return the name of the current register being recorded. An empty string is returned if we are not recording.

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

2

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

add a commentÂ |Â

up vote
13
down vote

accepted

Since Vim 8.1-0020, there is a reg_recording() function that'll return the name of the current register being recorded. An empty string is returned if we are not recording.

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

Since Vim 8.1-0020, there is a reg_recording() function that'll return the name of the current register being recorded. An empty string is returned if we are not recording.

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

answered Aug 6 at 12:06

Luc Hermitte

8,68111124

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

2

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

add a commentÂ |Â

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

2

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

That is the correct answer.
â€“Â Christian Brabandt
Aug 6 at 12:32

@ChristianBrabandt. Well, it depends if the script needs to target older versions of Vim. In that case, statox' solution may be the only workaround available.
â€“Â Luc Hermitte
Aug 6 at 12:35

add a commentÂ |Â

up vote
3
down vote

Edit I wasn't aware of reg_recording() but if you have a newer version of Vim Luc's answer is clearly the best answer.

I'm not aware of a built-in way to check if Vim is recording but you could use the following workaround in your .vimrc:

let g:isRecording = get(g:, 'isRecording', 0)
nnoremap q :let g:isRecording = !g:isRecording<CR>q

The first line will create a global variable g:isRecording which is falsy by default or takes its existing value if you re-source your .vimrc.

Then you remap q to toggle the value of g:isRecording when it toggles the recording mode and you can then test g:isRecording.

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

1

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

1

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

add a commentÂ |Â

up vote
3
down vote

Edit I wasn't aware of reg_recording() but if you have a newer version of Vim Luc's answer is clearly the best answer.

I'm not aware of a built-in way to check if Vim is recording but you could use the following workaround in your .vimrc:

let g:isRecording = get(g:, 'isRecording', 0)
nnoremap q :let g:isRecording = !g:isRecording<CR>q

The first line will create a global variable g:isRecording which is falsy by default or takes its existing value if you re-source your .vimrc.

Then you remap q to toggle the value of g:isRecording when it toggles the recording mode and you can then test g:isRecording.

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

1

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

1

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

add a commentÂ |Â

up vote
3
down vote

Edit I wasn't aware of reg_recording() but if you have a newer version of Vim Luc's answer is clearly the best answer.

I'm not aware of a built-in way to check if Vim is recording but you could use the following workaround in your .vimrc:

let g:isRecording = get(g:, 'isRecording', 0)
nnoremap q :let g:isRecording = !g:isRecording<CR>q

The first line will create a global variable g:isRecording which is falsy by default or takes its existing value if you re-source your .vimrc.

Then you remap q to toggle the value of g:isRecording when it toggles the recording mode and you can then test g:isRecording.

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

Edit I wasn't aware of reg_recording() but if you have a newer version of Vim Luc's answer is clearly the best answer.

I'm not aware of a built-in way to check if Vim is recording but you could use the following workaround in your .vimrc:

let g:isRecording = get(g:, 'isRecording', 0)
nnoremap q :let g:isRecording = !g:isRecording<CR>q

The first line will create a global variable g:isRecording which is falsy by default or takes its existing value if you re-source your .vimrc.

Then you remap q to toggle the value of g:isRecording when it toggles the recording mode and you can then test g:isRecording.

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

edited Aug 6 at 13:32

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

answered Aug 6 at 11:33

statoxâ™¦

23.9k556121

1

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

1

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

add a commentÂ |Â

1

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

1

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

I'm curious. Why have you preferred to define an autocommand to initialize the global variable instead of setting it in the vimrc? (with let g:isRecording = get(g:, 'isRecording', 0) to permit to source the vimrc as many times as we wish)
â€“Â Luc Hermitte
Aug 6 at 12:01

@LucHermitte It was because I didn't think of resourcing the vimrc :)
â€“Â statoxâ™¦
Aug 6 at 13:33

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu