This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
In Neovim, the . character repeats "the most recent action"; however, this is not always respected by plugin actions. Here we will explore how to build dot-repeat support directly into your plugin, bypassing the requirement of dependencies like repeat.vim.
When some buffer-modifying action is performed, Neovim implicitly remembers the operator (e.g. d), motion (e.g. iw), and some other miscellaneous information. When the dot-repeat command is called, Neovim repeats that operator-motion combination. For example, if we type ci"text<Esc>, then we replace the inner contents of some double quotes with text, i.e. "hello world" → "text". Dot-repeating from here will do the same, i.e. "more samples" → "text".
| #include <QtCore> | |
| static void dump(const char* name, const QStringList& variable) { | |
| QTextStream out(stdout); | |
| out << variable.count() << " " << name << endl; | |
| foreach (const QString& item, variable) { | |
| out << " " << item << endl; | |
| } | |
| } |
| del alias:cd -Force # Remove builtin cd alias to Set-Location | |
| function cd { | |
| $pwd = Get-Location | |
| if ($args.Count -eq 0) { | |
| Set-Location ~ | |
| } elseif ($args[0] -eq "-") { | |
| Set-Location @global:OLDPWD | |
| } else { | |
| Set-Location @args | |
| } |
For adding temporary logging to help understand behavior. For when it is impractical to use Frida to instrument Frida.
Choose one of these and copy-paste it into e.g. lib/interfaces/session.vala,
then use log_event ("name='%s'", name); to log.
When something appears to be hanging, try applying: x-async-debug.patch.
| #include <cstdio> | |
| #include <random> | |
| #include <algorithm> | |
| #include <chrono> | |
| int getRandNum_Old() { | |
| static bool init = false; | |
| if (!init) { | |
| std::srand(time(nullptr)); // Seed std::rand | |
| init = true; |
| #include "colattachedtype.h" | |
| #include <QQuickItem> | |
| #include <QQuickWindow> | |
| #include <QQmlInfo> | |
| ColAttachedType::ColAttachedType(QObject* parent) : | |
| QObject{parent}, | |
| m_item{qobject_cast<QQuickItem*>(parent)} | |
| { | |
| if (!m_item) { |
| Public URL: | Github Gist |
|---|---|
| Status: | Incomplete |
| Last Updated: | 2018-08-23 04:10 EDT |
| #!/usr/bin/env python | |
| """ | |
| Twitter's API doesn't allow you to get replies to a particular tweet. Strange | |
| but true. But you can use Twitter's Search API to search for tweets that are | |
| directed at a particular user, and then search through the results to see if | |
| any are replies to a given tweet. You probably are also interested in the | |
| replies to any replies as well, so the process is recursive. The big caveat | |
| here is that the search API only returns results for the last 7 days. So |
| for idx = 1, 5 do repeat | |
| print(1) | |
| print(2) | |
| print(3) | |
| do break end -- goes to next iteration of for | |
| print(4) | |
| print(5) | |
| until true end |
