after(n)

✨ after(n) — the "bestie, just wait a sec" command ✨

okay so real talk, this is the Tcl Built-In Commands page for after(n) and it's genuinely one of my faves because it's literally just "do this thing later, mkay?" energy. no cap. 💅

---

💖 NAME 💖

after — execute a command after a time delay 🕐✨

---

🎀 SYNOPSIS 🎀

after ms
after ms ?script script script ...?
after cancel id
after cancel script script script ...
after idle ?script script script ...?
after info ?id?

---

🌸 DESCRIPTION 🌸

okay so this command is the delay girlie. it's used to delay execution of the program, or to execute a command in the background sometime in the future. it's got several forms, and which one you get depends on the first argument you hand it. vibe check time 👑

🦋 after ms

ms must be an integer giving a time in milliseconds. a negative number is treated as 0. the command sleeps for ms milliseconds and then returns. and bestie, heads up: while the command is sleeping, the application does not respond to events. it's giving "do not disturb" but like, aggressively. 😴

🦋 after ms ?script script script ...?

in this form the command returns immediately, but it arranges for a Tcl command to be executed ms milliseconds later as an event handler. the command will be executed exactly once, at the given time. ✨

the delayed command is formed by concatenating all the script arguments in the same fashion as the concat command. the command will be executed at global level (outside the context of any Tcl procedure). if an error occurs while executing the delayed command then the background error will be reported by the command registered with interp bgerror. 💀

the after command returns an identifier that can be used to cancel the delayed command using after cancel. 🎯

a ms value of 0 (or negative) queues the event immediately with priority over other event types (if not installed with an event proc, which will wait for next round of events). main character energy fr fr.

🦋 after cancel id

cancels the execution of a delayed command that was previously scheduled. id indicates which command should be canceled; it must have been the return value from a previous after command. if the command given by id has already been executed then the after cancel command has no effect. it's not mad, it's just too late 🙈

🦋 after cancel script script ...

this command also cancels the execution of a delayed command. the script arguments are concatenated together with space separators (just as in the concat command). if there is a pending command that matches the string, it is canceled and will never be executed; if no such command is currently pending then the after cancel command has no effect. 🫶

🦋 after idle script ?script script ...?

concatenates the script arguments together with space separators (just as in the concat command), and arranges for the resulting script to be evaluated later as an idle callback. the script will be run exactly once, the next time the event loop is entered and there are no events to process. 🌈

the command returns an identifier that can be used to cancel the delayed command using after cancel. if an error occurs while executing the script then the background error will be reported by the command registered with interp bgerror. 😭

🦋 after info ?id?

this command returns information about existing event handlers. if no id argument is supplied, the command returns a list of the identifiers for all existing event handlers created by the after command for this interpreter. 📋

if id is supplied, it specifies an existing handler; id must have been the return value from some previous call to after and it must not have triggered yet or been canceled. in this case the command returns a list with two elements. the first element of the list is the script associated with id, and the second element is either idle or timer to indicate what kind of event handler it is. two items, iconic. 💅

🫧 the after ms and after idle forms of the command assume that the application is event driven: the delayed commands will not be executed unless the application enters the event loop. in applications that are not normally event-driven, such as tclsh, the event loop can be entered with the vwait and update commands. iykyk 💖

---

🔥 EXAMPLES 🔥

this defines a command to make Tcl do nothing at all for N seconds:

proc sleep {N} {
    after [expr {int($N * 1000)}]
}

this arranges for the command wake_up to be run in eight hours (providing the event loop is active at that time):

after [expr {1000 * 60 * 60 * 8}] wake_up

the following command can be used to do long-running calculations (as represented here by ::my_calc::one_step, which is assumed to return a boolean indicating whether another step should be performed) in a step-by-step fashion, though the calculation itself needs to be arranged so it can work step-wise. this technique is extra careful to ensure that the event loop is not starved by the rescheduling of processing steps (arranging for the next step to be done using an already-triggered timer event only when the event queue has been drained) and is useful when you want to ensure that a Tk GUI remains responsive during a slow task. 🧚✨

proc doOneStep {} {
    if {[::my_calc::one_step]} {
        after idle [list after 0 doOneStep]
    }
}
doOneStep

---

👀 SEE ALSO 👀

• concat(n)
• interp(n)
• update(n)
• vwait(n)

---

⭐ KEYWORDS ⭐

cancel, delay, idle callback, sleep, time

---

okay that's the whole page bestie, no skips, no skims 🫶 this was the after(n) page from Tcl 7.5, and yes the page itself is literally named after(n) like it's too cool for a long title. mwah, go schedule something. 💜🎀