238 karma · joined September 23, 2010
Link to their GitHub repo: https://github.com/samnazarko/osmc
This has been an issue with the PowerBook G4 models in the past as well. The iBook G4 models also had this problem but only on the lid button.
He's an artist and his medium is ASCII, ANSI or Teletext. I think that's fascinating.
The Wikipedia article on IPC https://en.wikipedia.org/wiki/Inter-process_communication is really incomplete.
Users can use a different compiler by specifying it on the command line via e.g.
make CC=clang
Some people set CC=gcc
in their Makefile to force the usage of gcc. Never do this. Do this instead: CC?=gcc
That way users can still override the value of ${CC} on the command line if they want to.Edit: It seems to be set dynamically depending on available memory at boot. See http://fxr.watson.org/fxr/source/kern/subr_param.c#L266
user> (let [e nil] (e :key))
NullPointerExceptionThinking about it, I guess triple-quoted strings also facilitate doctests involving strings that would otherwise be really awkward to read/write.
Currently I am using a notebook in front of an external display and I added a function to dwm with which I can essentially "push" all clients (windows) to the external display, which in turn sends all its clients to my notebook's display (or in other words it swaps all clients of one display with all clients of the other).
When I am coding I am always using bstack mode with vim on top and one or two terminals at the bottom. The external monitor is displaying documentation. If I have to look something up I just have to push vim + terminals away. If I am finished I pull them back. So my notebook display becomes my working display.
short s[70];*l=s;t;main(){read(0,s,140);s[4]>>8==1&s[10]==8?s[10]=0,s[11]+=8,t=l[4],l[4]=l[3],l[3]=t,write(1,s,140):0;main();}
8 less now, thanks to viraptor: short s[70];*l=s+6;main(t){read(0,s,140);s[4]>>8==1&s[10]==8?s[10]=0,s[11]+=8,t=*l,*l=l[1],l[1]=t,write(1,s,140):0;main();}