firefox/tridactyl.tridactyl
1
0
Fork 0
mirror of https://github.com/tridactyl/tridactyl.git synced 2026-09-10 07:16:33 -04:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #5193 from tridactyl/cmc-fix-typo
Some checks failed
e2e / test (firefox, ubuntu) (push) Has been cancelled
Details
e2e / test (firefox, windows) (push) Has been cancelled
Details
e2e / test (firefoxesr, ubuntu) (push) Has been cancelled
Details
lint / lint (lint) (push) Has been cancelled
Details
lint / lint (mozilla) (push) Has been cancelled
Details
lint / lint (unit) (push) Has been cancelled
Details
Website / build (push) Has been cancelled
Details
Website / deploy (push) Has been cancelled
Details

Browse source 
fix typo
This commit is contained in:
Oliver Blanthorn 2025-03-11 13:45:49 +00:00 committed by GitHub
parent 60118c49ec 01f18bf213
commit 02a5731d88
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/excmds.ts
View file

@ -3820,7 +3820,7 @@ async function getnexttabs(tabid: number, n?: number) {
This re-executes the last *exstr*, not the last *excmd*. Some excmds operate internally by constructing and evaluating exstrs, others by directly invoking excmds without going through the exstr parser. For example, aucmds and keybindings evaluate exstrs and are repeatable, while commands like `:bmarks` directly invoke `:tabopen` and you'll repeat the `:bmarks` rather than the internal `:tabopen`.
It's difficult to execute this in the background script (`:jsb`, `:run_excmd`, `:autocmd TriStart`, `:source`), but if you you do, it will re-execute the last exstr that was executed in the background script. What this may have been is unpredictable and not precisely encouraged.
It's difficult to execute this in the background script (`:jsb`, `:run_excmd`, `:autocmd TriStart`, `:source`), but if you do, it will re-execute the last exstr that was executed in the background script. What this may have been is unpredictable and not precisely encouraged.
*/
//#background