Hi, Is there any way to find out when there's a conflict in a recurring meeting, that the organizer can see what the conflicts are? Intead of the resoruce calendar just rejecting the whole series, it should provide more information so the organizer can shift around other's schedule if necessary. Thanks for your assistance. P.S. Server is Exchange 2007 SP1, clients are mostly ...

...> way to do it. Of course I can write a small lisp function, but I think there are other cool ways. First, don't get hung up on killing the buffer. Buffers like *Help* don't use much resoruces and the buffer will be reused next time you use help. I've often got many buffers open in emacs at a time (normally around 30 or more). All you want is to have the buffer not use up valuable ...

.... Of course, this is a rather resource expensive way of serving a few pages - you would always have to have an emacs image loaded or accept fairly slow responses (depending on machine/resoruces etc). I think a better solution would be to add a hook to the org mode save function that does an automatic export as html whenever the org file is updated. The pages can ...

... page. Of course, this is a rather resource expensive way of serving a few pages - you would always have to have an emacs image loaded or accept fairly slow responses (depending on machine/resoruces etc). I think a better solution would be to add a hook to the org mode save function that does an automatic export as html whenever the org file is updated. The pages can then ...

... I'm aware of. Of course, this is a rather resource expensive way of serving a few pages - you would always have to have an emacs image loaded or accept fairly slow responses (depending on machine/resoruces etc). I think a better solution would be to add a hook to the org mode save function that does an automatic export as html whenever the org file is updated. The pages can then be ...

> that's a slightly different aspect. the note should not be "page fault" but "out of memory" (or some such thing). that's much better than a nil return. most errors on shared resoruces are better expressed as exceptions (notes), because that's what they are: they are a failure of the underlying physical or virtual machine to handle an exceptional case. the code shouldn't have to ...

.... that's a slightly different aspect. the note should not be "page fault" but "out of memory" (or some such thing). that's much better than a nil return. most errors on shared resoruces are better expressed as exceptions (notes), because that's what they are: they are a failure of the underlying physical or virtual machine to handle an exceptional case. the code shouldn't have to deal ...

... think it was more the part where you lie and attempt to mislead people into thinking there's some fee required. You say membership instead of registration and often have claimed outright that the resoruces on fastseduction.com are not free. You obviously feel some need to point out that you need to register to view pair, and yet fail to mention you need similar registration on...

...I think it was more the part where you lie and attempt to mislead people into thinking there's some fee required. You say membership instead of registration and often have claimed outright that the resoruces on fastseduction.com are not free. You obviously feel some need to point out that you need to register to view pair, and yet fail to mention you need similar registration on the ...

Can anyone suggest any good resources (books, websites etc) covering writing programmable shaders using HLSL? I am especially interested in resources that show how to do the various fixed function pipeline things (e.g. various SetRenderState calls) in shaders.