clc — Clear the visible command window or console display.
clc emits a portable clear-screen control event for the active host without changing workspace or figure state.
Syntax
clcReturns
ans- Type
NumericArray- Description
- Empty matrix placeholder used by the runtime sink boundary.
Errors
RunMat:clc:ArgumentCount- When
- One or more input arguments are passed to clc.
- Message
clc: expected no input arguments
Console control
clc requests that the active host clear its visible command output. It emits a control event instead of writing terminal escape bytes, so terminal, desktop, and browser hosts can apply the request through their own display layer.
The operation does not alter workspace variables, figures, the working directory, or execution state. It accepts no input arguments and suppresses automatic display of its internal empty return value.
Host behavior
Terminal hosts translate the control event into their clear-screen behavior. WebAssembly hosts expose a clear stream entry to the embedding UI. A host may retain output in an external log even after removing it from the visible command window.
clc does not inspect array data and never invokes an accelerator provider. Its contract is portable across native and browser runtimes, but its visible effect is implemented by the host.
Examples
Clear between command-window messages
disp('Step 1 complete');
clc;
disp('Ready for the next command')Expected output:
Ready for the next commandLeave workspace values unchanged
sample_count = 42;
clc;
assert(sample_count == 42);Reject input arguments
clc(1)Expected output:
clc: expected no input argumentsUsing clc with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how clc changes the result.
Run a small clc example, explain the result, then change one input and compare the output.
FAQ
Does clc delete previous output permanently?⌄
It asks the active host to clear visible output. A host may retain the same entries in logs or execution history.
What does a browser host receive?⌄
The WebAssembly execution stream contains an entry whose stream is clear; the embedding UI decides how to update its console.
Does clc change variables or figures?⌄
No. Use clear for workspace bindings and close for figures.
Can clc accept arguments?⌄
No. Passing an argument returns clc: expected no input arguments.
Related Io functions
Repl Fs
addpath · cd · copyfile · delete · dir · exist · fileattrib · fileparts · filesep · fullfile · genpath · getenv · getpref · isenv · isfile · isfolder · ispref · ls · matlabroot · memmapfile · memmapfile.subsasgn · memmapfile.subsref · mkdir · movefile · open · opentoline · path · pathsep · pcode · pwd · readstruct · rehash · restoredefaultpath · rmdir · rmpath · run · savepath · setenv · setpref · system · tempdir · tempname · uigetdir · uigetfile · uiputfile · unsetenv · userpath · what · winqueryreg · xmlread · xmlwrite
Tabular
arrayDatastore · csvread · csvwrite · detectImportOptions · dlmread · dlmwrite · fileDatastore · getvaropts · parquetDatastore · parquetinfo · parquetread · readcell · readmatrix · readtable · readtimetable · setvaropts · setvartype · spreadsheetImportOptions · writecell · writematrix · writetable · writetimetable · xlsread · xlswrite
Data
commit · data.copy · data.create · data.delete · data.exists · data.export · data.import · data.inspect · data.list · data.move · data.open · DataArray.chunk_shape · DataArray.codec · DataArray.dtype · DataArray.fill · DataArray.name · DataArray.rank · DataArray.read · DataArray.resize · DataArray.shape · DataArray.write · Dataset.array · Dataset.arrays · Dataset.attrs · Dataset.begin · Dataset.get_attr · Dataset.has_array · Dataset.id · Dataset.path · Dataset.refresh · Dataset.set_attr · Dataset.set_attrs · Dataset.snapshot · Dataset.version · DataTransaction.abort · DataTransaction.commit · DataTransaction.create_array · DataTransaction.delete_array · DataTransaction.fill · DataTransaction.id · DataTransaction.resize · DataTransaction.set_attr · DataTransaction.set_attrs · DataTransaction.status · DataTransaction.write
Filetext
fclose · feof · fgetl · fgets · fileread · filewrite · fopen · fprintf · fread · frewind · fwrite · readlines · writelines
Import
Json
Source you can read
Every RunMat function's source is public. Read exactly how clc is executed, line by line, in Rust.
- View the source for clc in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.