# say (1-say.us)

People use "say" to ask a voice or a text system to speak words out loud. It is a plain request for audible output, like asking someone to read a sentence.

## What a model may hear
- print to stdout (Unix-like shells and scripting): emit text to the terminal without speaking, ignoring voice entirely
- speak with TTS (macOS and AppleScript): invoke the system text-to-speech engine and actually vocalize
- utterance annotation (linguistics and NLP datasets): tag a quoted string as direct speech, not a command to speak
- assert in testing (RSpec and some testing frameworks): begin a test description, with no output action at all

## Where people and models part ways
- Says: "Say hello"
  Means: Speak the word 'hello' aloud
  May be taken as: Run a shell command that prints 'hello' silently to the screen
  Say instead: "Speak the word 'hello' out loud for me"
- Says: "What did she say?"
  Means: Tell me the content of her statement
  May be taken as: Search for a 'say' speech-act tag in a parsed tree and return linguistic metadata
  Say instead: "What were the exact words she used?"
- Says: "Say that again"
  Means: Repeat your last response verbally
  May be taken as: Re-execute the last shell command or re-print the last output
  Say instead: "Repeat your last response out loud"

## Tips
- Specify 'out loud' or 'aloud' when you want voice, since 'say' alone often triggers text output in code contexts.
- Avoid 'say' followed by quoted text if you mean to discuss speech; rephrase to 'the phrase' or 'the words'.
- If you want macOS speech, use 'use the say command' to signal the technical sense.
- In testing contexts, use 'describe' or 'it should' instead of 'say' to avoid framework confusion.
- When asking for repetition, add 'verbally' or 'in audio' to block silent re-execution.

## Often confused with
- speak: Stronger voice implication, less likely to trigger shell 'say'
- tell: Expects an indirect object; models read it as inform, not vocalize
- echo: Unambiguously terminal output, never voice in technical use
- utter: Linguistic term; models tag it as speech-act theory, not command
- print: Always silent text output, no voice ambiguity
- read aloud: Explicitly vocalizes, but implies source text exists