here's some desktop footage of the glitch-like qualities caused by
neglecting to redirect stderr to /dev/null or /dev/pts/1 (an open
terminal) when stderr is having debug messages output to it.

http://jwm-art.net/xorcurses_debug.mp4

i find there is some aesthetically pleasing qualities to it. but

it's expected for an ncurses app which outputs anything to stdout or
stderr. its not out of the ordinary for debug info to be sent to
stderr. a console/terminal application (non-ncurses) would normally
output to stdout, so outputting debug info to stderr allows the two
streams to be prized apart, one as normal, the other to a file or
elsewhere where ordinarily they'd intermingle and become confused like
they do in the file i show.

in the file i show, what you see, is by me thoroughly expected
behaviour. its not bugs in the code which produce this glitch-like
effect. it's not an accident.

debug messages are used by programmers to identify what and when is
happening. they're written by the programmer and the program. macros
insert src filename, function name, and lineno into the messages.

perhaps some kind of deprivation produces this. driven by some kind of
deprivation to send this out. 3 people look at the first fifteen
seconds. two don't even get as far as the link. the rest have me in
their ignore file.

pity this poor fake artist. he's not very good at art, even worse at
theory, has forgotten all history... he can write code but not
brilliantly. can write code. can't code art. can't art code. can create
code. code write create. poor fake artist. nose know theyorae. glitch
glitch. fear||y. kerchitch. gling. theory. per chin beer re: glitch
hero. heroe's of glitch volume II: the blessed yoghurt pock. grab-bag.

dev/pts/1 is my favourite thing right now. i love it, /dev/pts/1 it
rocks my socks yo. yo yo yo yore botox. /dev/pts/1/rox-shlocks/



-- 
http://jwm-art.net/
image/audio/text/code/

_______________________________________________
NetBehaviour mailing list
[email protected]
http://www.netbehaviour.org/mailman/listinfo/netbehaviour

Reply via email to