spw.quest

Pivot a line

Change one slot, keep the rest, and see the line before you go. Forms, side by side shows what each slot does.

The line

practice[profile]{fail.constrain}

a line you wrote

  • new
subject
practice
mode
profile
body
fail.constrain

An operator in front

  1. ~
  2. ?
  3. !
  4. *
  5. .
  6. ^
  7. #
  8. @
  9. &
  10. =
  11. %
  12. $
Add to what it holds

Back to builder[profile]{fail.constrain}

Families it belongs to

Other lines about practice

31 lines one change away

Drop a slot to read what the line says without it.

near: a line sharing a slot uses it · common: common on the shelf

charge the charge in front

  1. boon practice[profile]{fail.constrain}

    add boon

    • add
    lands
    Not on the shelf yet.
    why
    a valence word rides the word

subject the word

  1. builder[profile]{fail.constrain}

    swap to builder

    • swap
    • near
    lands
    Not on the shelf yet.
  2. folio[profile]{fail.constrain}

    swap to folio

    • swap
    • common
    lands
    Not on the shelf yet.
  3. theory[profile]{fail.constrain}

    swap to theory

    • swap
    • common
    lands
    Not on the shelf yet.
  4. principle[profile]{fail.constrain}

    swap to principle

    • swap
    • common
    lands
    Not on the shelf yet.
  5. ?practice[profile]{fail.constrain}

    ? wonder in front

    • mark
    lands
    Not on the shelf yet.
  6. ~practice[profile]{fail.constrain}

    ~ potential in front

    • mark
    lands
    Not on the shelf yet.
  7. ^practice[profile]{fail.constrain}

    ^ ascension in front

    • mark
    lands
    Not on the shelf yet.
  8. &practice[profile]{fail.constrain}

    & subject in front

    • mark
    lands
    Not on the shelf yet.
  9. $practice[profile]{fail.constrain}

    $ substrate in front

    • mark
    lands
    Not on the shelf yet.

mode the lens

  1. practice[software]{fail.constrain}

    swap to software

    • swap
    • near
    lands
    Not on the shelf yet.
  2. practice[learning]{fail.constrain}

    swap to learning

    • swap
    • near
    lands
    Not on the shelf yet.
  3. practice[design]{fail.constrain}

    swap to design

    • swap
    • near
    lands
    Not on the shelf yet.
  4. practice[film]{fail.constrain}

    swap to film

    • swap
    • near
    lands
    Not on the shelf yet.
  5. practice{fail.constrain}

    drop the lens

    • drop
    lands
    Not on the shelf yet.
  6. practice{fail.constrain}(profile)

    turn its walls to ( )

    • walls
    lands
    Not on the shelf yet.
    why
    the lens becomes the scene
  7. practice{fail.constrain}<profile>

    turn its walls to < >

    • walls
    lands
    Not on the shelf yet.
    why
    the lens becomes where it goes

body what it holds

  1. practice[profile]{founding}

    swap to founding

    • swap
    • near
    lands
    Not on the shelf yet.
  2. practice[profile]{components}

    swap to components

    • swap
    • near
    lands
    Not on the shelf yet.
  3. practice[profile]{release}

    swap to release

    • swap
    • near
    lands
    Not on the shelf yet.
  4. practice[profile]{folios}

    swap to folios

    • swap
    • near
    lands
    Not on the shelf yet.
  5. practice[profile]

    drop what it holds

    • drop
    lands
    Not on the shelf yet.
  6. practice[profile](fail.constrain)

    turn its walls to ( )

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes the scene
  7. practice[profile]<fail.constrain>

    turn its walls to < >

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes where it goes
  8. practice[profile]{fail,constrain}

    hold the parts together

    • turn
    lands
    Not on the shelf yet.
    why
    commas keep parts apart and present at once
  9. practice[profile]{fail;constrain}

    hold the parts in order

    • turn
    lands
    Not on the shelf yet.
    why
    semicolons put the parts in a sequence
  10. practice[profile]{fail ~> constrain}

    make the parts a path

    • turn
    lands
    Not on the shelf yet.
    why
    ~> carries each part on to the next without collapsing them

projection where it goes

  1. practice[profile]{fail.constrain}<share>

    add share

    • add
    • near
    lands
    Not on the shelf yet.
  2. practice[profile]{fail.constrain}<trace>

    add trace

    • add
    • near
    lands
    Not on the shelf yet.
  3. practice[profile]{fail.constrain}<seed>

    add seed

    • add
    • near
    lands
    Not on the shelf yet.
  4. practice[profile]{fail.constrain}<receipt>

    add receipt

    • add
    • common
    lands
    Not on the shelf yet.

Constructs · Specimens · Take one line apart · Learn it a mark at a time