Code Teachers?

[Thenomain]

@Ashen-Shugar and @WTFE: I would prefer Sublime/Atom as it has better project control and the plug-in support is more modern.

[WTFE]

@Thenomain Personally I couldn't stand Sublime. The editor core was nice. Very nice. But it was 99.44% undocumented, had a clear hierarchy of supported platforms (with my most common one at the bottom of the stack), and a vendor who was fucking close to extreme autism in his utter disinterest in actually communicating with his paying customers.

Atom is too hipster for my tastes (and I object to having to fire up a 1GB browser to edit 24KB of text), but it can probably be easily modified to support the functionality you'd like.

[Thenomain]

@WTFE

Possibly-probably, but I consider Atom to be in heavy development, the same way that it took some browsers forever and a day to become realistically fast or light. Atom doesn't hide much (any?) of its core functionality, but I'd have to get some deeper coding to make it work the way I want and there is a limit to my frustration-to-laziness ratio.

I'm not an Emacs/VIM person, mostly because I don't want to learn an entirely new UI. Yes, I can happily keep my current editor, but I like being able to share my style to those who are looking for help into how to code better, faster, cleaner.

(Did I mention? Spaces after commas! Spaces after semi-colons! If you do nothing else, do this, aaaaagh!)

[Chime]

@Thenomain: emacs has two cursors; the mark (generally invisible) and the point (aka the cursor you can see). Most cut and region-change operations are defined over the mark..point or point..mark span.

It's an utterly alien UI compared to anything you've used-- but it's also very old and long-lived and pervasive in places you already use. Things I've used that followed the same UI

• TECO Emacs 162 on PDP-10 ITS circa 1970s
• Zmacs on Symbolics Genera (lispmachines ARE the OS that emacs pretends to be) circa 1980s
• Emacs itself, of course, on all vaguely posix-ish systems and many that aren't.
• Most GNU command-oriented tools; bash, libreadline, etc.
• Most Apple core UI stuff, including all the apps in their office clone. (Because Steve Jobs was an emacs user, oddly enough; they are almost never documented, but all of the emacs control codes work transparently all over the place in MacOS X. ...except for iTunes. Fuck those guys.)

Come to the dark side...

...we have parentheses.

[Cobalt]

http://fallcoast.net/wiki/Code_Teaching_(%2BWho)

We didn't finish, I'll be scheduling another session for a day when I have alittle bit more time.

[Chime]

@Cobaltasaurus .... escaping mushcode so that it isn't parsed isn't that hard. Really!

Parsing context exists only at the beginning of an lbuf or after [ ... or as an argument to a function that is already being parsed.

You should be able to do:

say for example: iter( lnum(3), woot )
say iter( lnum(3), woot )

and then people see:

Chime says, "for example: iter( lnum(3), woot)"
Chime says, "woot woot woot"

see also the /noparse flag for @emit and friends.

Alternatively, there are a variety of mushify programs that can carefully escape arbitrarily complex punctuation, generally used for ascii art.

$ cat moon.txt
                     .--------------.
                .---'  o        .    `---.
             .-'    .    O  .         .   `-.
          .-'     @@@@@@       .             `-.
        .'@@   @@@@@@@@@@@       @@@@@@@   .    `.
      .'@@@  @@@@@@@@@@@@@@     @@@@@@@@@         `.
     /@@@  o @@@@@@@@@@@@@@     @@@@@@@@@     O     \
    /        @@@@@@@@@@@@@@  @   @@@@@@@@@ @@     .  \
   /@  o      @@@@@@@@@@@   .  @@  @@@@@@@@@@@     @@ \
  /@@@      .   @@@@@@ o       @  @@@@@@@@@@@@@ o @@@@ \
 /@@@@@                  @ .      @@@@@@@@@@@@@@  @@@@@ \
 |@@@@@    O    `.-./  .        .  @@@@@@@@@@@@@   @@@  |
/ @@@@@        --`-'       o        @@@@@@@@@@@ @@@    . \
|@ @@@@ .  @  @    `    @            @@      . @@@@@@    |
|   @@                         o    @@   .     @@@@@@    |
|  .     @   @ @       o              @@   o   @@@@@@.   |
\     @    @       @       .-.       @@@@       @@@      /
 |  @    @  @              `-'     . @@@@     .    .    |
 \ .  o       @  @@@@  .              @@  .           . /
  \      @@@    @@@@@@       .                   o     /
   \    @@@@@   @@\@@    /        O          .        /
    \ o  @@@       \ \  /  __        .   .     .--.  /
     \      .     . \.-.---                   `--'  /
      `.             `-'      .                   .'
        `.    o     / | `           O     .     .'
          `-.      /  |        o             .-'
             `-.          .         .     .-'
                `---.        .       .---'
                     `--------------'

$ cat moon.txt |mushify
[space(21)].--------------.%r[space(16)].---'%b%bo[space(8)].%b%b%b%b`---.%r[space(13)].-'%b%b%b%b.%b%b%b%bO%b%b.[space(9)].%b%b%b`-.%r[space(10)].-'%b%b%b%b%b@@@@@@[space(7)].[space(13)]`-.%r[space(8)].'@@%b%b%b@@@@@@@@@@@[space(7)]@@@@@@@%b%b%b.%b%b%b%b`.%r[space(6)].'@@@%b%b@@@@@@@@@@@@@@%b%b%b%b%b@@@@@@@@@[space(9)]`.%r%b%b%b%b%b/@@@%b%bo @@@@@@@@@@@@@@%b%b%b%b%b@@@@@@@@@%b%b%b%b%bO%b%b%b%b%b\\%r%b%b%b%b/[space(8)]@@@@@@@@@@@@@@%b%b@%b%b%b@@@@@@@@@ @@%b%b%b%b%b.%b%b\\%r%b%b%b/@%b%bo[space(6)]@@@@@@@@@@@%b%b%b.%b%b@@%b%b@@@@@@@@@@@%b%b%b%b%b@@ \\%r%b%b/@@@[space(6)].%b%b%b@@@@@@ o[space(7)]@%b%b@@@@@@@@@@@@@ o @@@@ \\%r /@@@@@[space(18)]@ .[space(6)]@@@@@@@@@@@@@@%b%b@@@@@ \\%r |@@@@@%b%b%b%bO%b%b%b%b`.-./%b%b.[space(8)].%b%b@@@@@@@@@@@@@%b%b%b@@@%b%b|%r/ @@@@@[space(8)]--`-'[space(7)]o[space(8)]@@@@@@@@@@@ @@@%b%b%b%b. \\%r|@ @@@@ .%b%b@%b%b@%b%b%b%b`%b%b%b%b@[space(12)]@@[space(6)]. @@@@@@%b%b%b%b|%r|%b%b%b@@[space(25)]o%b%b%b%b@@%b%b%b.%b%b%b%b%b@@@@@@%b%b%b%b|%r|%b%b.%b%b%b%b%b@%b%b%b@ @[space(7)]o[space(14)]@@%b%b%bo%b%b%b@@@@@@.%b%b%b|%r\\%b%b%b%b%b@%b%b%b%b@[space(7)]@[space(7)].-.[space(7)]@@@@[space(7)]@@@[space(6)]/%r |%b%b@%b%b%b%b@%b%b@[space(14)]`-'%b%b%b%b%b. @@@@%b%b%b%b%b.%b%b%b%b.%b%b%b%b|%r \\ .%b%bo[space(7)]@%b%b@@@@%b%b.[space(14)]@@%b%b.[space(11)]. /%r%b%b\[space(6)]@@@%b%b%b%b@@@@@@[space(7)].[space(19)]o%b%b%b%b%b/%r%b%b%b\\%b%b%b%b@@@@@%b%b%b@@\\@@%b%b%b%b/[space(8)]O[space(10)].[space(8)]/%r%b%b%b%b\\ o%b%b@@@[space(7)]\\ \\%b%b/%b%b__[space(8)].%b%b%b.%b%b%b%b%b.--.%b%b/%r%b%b%b%b%b\[space(6)].%b%b%b%b%b. \\.-.---[space(19)]`--'%b%b/%r[space(6)]`.[space(13)]`-'[space(6)].[space(19)].'%r[space(8)]`.%b%b%b%bo%b%b%b%b%b/ | `[space(11)]O%b%b%b%b%b.%b%b%b%b%b.'%r[space(10)]`-.[space(6)]/%b%b|[space(8)]o[space(13)].-'%r[space(13)]`-.[space(10)].[space(9)].%b%b%b%b%b.-'%r[space(16)]`---.[space(8)].[space(7)].---'%r[space(21)]`--------------'%r

...ugly, but effective

[Cobalt]

@Chime said in Code Teachers?:

@Cobaltasaurus .... escaping mushcode so that it isn't parsed isn't that hard. Really!

Parsing context exists only at the beginning of an lbuf or after [ ... or as an argument to a function that is already being parsed.

I know...? that wasn't really my problem? It was typos rather than not knowing how to escape mushcode.

Or see signature. XD I know what I'm doing, I swear!

[Chime]

@Cobaltasaurus said in Code Teachers?:

I know...? that wasn't really my problem? It was typos rather than not knowing how to escape mushcode.

Or see signature. XD I know what I'm doing, I swear!

Heh, I guess you do, at that. Sorry.

For typos, I can only offer reeeeally good coffee.

[Thenomain]

My favorite is the /noeval switch. E.g.: say/noeval, pose/noeval and of course for helping people from afar, page/noeval

(Not at all edited because @Cobaltasaurus was right and I was wrong or anything.)

[Cobalt]

I thought it was page/noeval? o.O

[Chime]

Ignore the bird, follow the river.