similar to: Patch for ini plugin

Hi David, When maximizing windows on a different resolution only 70% of the window is maximized. Ie: on my 1280x1024 screen a window maximized is correct (and does not clobber the desktop panel in KDE, kicker) On my 1600x1200 screen, with no kicker panel, the window is maximized about 70% of the screen only Is this known? Thanks, Shawn. ----- Original Message ---- From: David Reveman

Here are my patches to add edge + button functionality. I still feel that there is a problem with gconf, but I have just made it so that the edge button functionality works. I have included a patch for gconf to display AnyButton if it is set to 0. There is also a patch to make the edge size configurable because 1 pixel was too small and the mouse keeps slipping off when using it for the

The ini plugin segfaults on startup. The following patch fixes it. Not sure why this hasn't been caught before - i guess not many people use the ini plugin. Please apply. randolph diff --git a/plugins/ini.c b/plugins/ini.c index d58f671..2d3c2dd 100644 --- a/plugins/ini.c +++ b/plugins/ini.c @@ -377,7 +377,7 @@ iniParseLine (char *line, char **optionName, char **optionValue) if

Hi, I finally got it working and it was just as Gene said except that option 43 didn't have the right value. I downloaded a utility called PXEForcedMode that gave me the binary string I had to use as option 43. In my case the utility reported the following data: dhcp server set optionvalue 43 BINARY 06010B0807AAAA010AD7903C00 dhcp server set optionvalue 60 STRING PXEClient dhcp server set

Hi, some bugs i would see fixed is when using edgebutton in scale. The first is initiate_group_edgebutton don't seem to work at all. The second is when using it on initate and initate_all, it sometimes seem to stop working all together, though this is the case also without using edgebutton, maybe after doing some config changes in gconf.

Question 1: I am trying to get a function not to be inlined. What are llvm's rules pertaining to inlining? I have tried all of the standard gcc options for turning off inlining and they do not seem to work. Here is the sample code that I am working with: #include <stdio.h> void print_string(char* strval); int main() { char* strval = "Hello world\n"; while(1){

Hello. System info: OS: FC6 x86_64 video: Nvidia GF 7900 GT, driver version 97.55 compiz version: git config backend used: ccp I can reproduce this crash every time on my system. When blur plugin is active and I try to access any right-click menu, regular application menu or drop-down list, compiz crashes. Backtrace produced by crashhandler plugin shows crash in blur.c in function

I'm writing a C compiler in OCaml and I've run into a small problem. I wrote the following piece of code to generate a pointer to a string constant, so I could compile C expressions of the form "const char* p = "test\n";" : let strval = const_stringz codecontext v in dump_value strval; dump_value i32_zero; const_gep strval [| i32_zero; i32_zero |] The dump statements

There is a problem with some window specific actions like scale_group and rotate_with_window when they are activated by an edgebutton. The basic problem is that each of those actions use the window option provided to the action. When an edgebutton is used the window id sent is actually the id of the edge window, this means that actions which rely on this stop working. The obvious solution would

On Mar 4, 2010, at 4:50 PM, Nyx wrote: > > I'm writing a C compiler in OCaml and I've run into a small problem. I wrote > the following piece of code to generate a pointer to a string constant, so I > could compile C expressions of the form "const char* p = "test\n";" : > > let strval = const_stringz codecontext v in > dump_value strval; >

On Feb 14, 2012, at 10:47 PM, Talin wrote: > /// Add a pointer value > template<typename T> > void add(const T *PtrVal) { > addImpl( > reinterpret_cast<const uint32_t *>(&PtrVal), > reinterpret_cast<const uint32_t *>(&PtrVal + 1)); > } > > This violates TBAA rules and looks pretty dangerous to expose as public API.

On Tue, Feb 14, 2012 at 2:44 AM, Chris Lattner <clattner at apple.com> wrote: > On Feb 13, 2012, at 2:00 AM, Talin wrote: >> >> Just out of curiosity, why not MurmurHash3 ? This page seems to >> suggest that #2 has some flaw, and #3 is better all round: >> >> https://sites.google.com/site/murmurhash/ >> > The main reason is because there's no

Ok, here is the patch again... I also included fixes for the bits that originally gave my mailer fits... Two votes for orange, so I went with orange... Doing diffs in .: --- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800 +++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800 @@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char * Result +=

On Tue, Feb 14, 2012 at 2:44 AM, Chris Lattner <clattner at apple.com> wrote: > On Feb 13, 2012, at 2:00 AM, Talin wrote: > > Just out of curiosity, why not MurmurHash3 ? This page seems to >> suggest that #2 has some flaw, and #3 is better all round: >> >> https://sites.google.com/site/murmurhash/ >> >> The main reason is because there's no

On Feb 13, 2012, at 2:00 AM, Talin wrote: > Just out of curiosity, why not MurmurHash3 ? This page seems to > suggest that #2 has some flaw, and #3 is better all round: > > https://sites.google.com/site/murmurhash/ > > The main reason is because there's no incremental version of 3. I think that that is a great reason. > LLVM's needs, on the other hand, are fairly

Hi, I was trying to use the autorun feature of rspec but noticed that when I run the command to kick off the ruby scripts it picks up the options that I give to the command. ''myRubyBin -j optionValue'' This then fails with this error, /usr/lib/ruby/1.8/optparse.rb:1448:in `complete'' : invalid option: -j ( OptionParser::InvalidOption ) from

OK here's a patch with the latest, including unit tests. I've also tried to make the comments clear that this is intended for the case of "generic" key types, where you are either hashing multiple data types together, or you don't know in advance what the data type will be - for cases such as strings where a tailored algorithm is available, you should use that instead of

I tried to build LLVM with 'gcc-4.8.1 -flto', and when linking unittest programs, I got the following error: /tmp/cc8pMk84.ltrans30.ltrans.o:(.data.rel.ro._ZTIN4llvm2cl15OptionValueCopyISsEE[_ZTIN4llvm2cl15OptionValueCopyISsEE]+0x10): undefined reference to `typeinfo for llvm::cl::GenericOptionValue'

(+Chris, since I assume he wrote this policy - and, as I said in my previous email, I wouldn't mind seeing some justification or just seeing the rule go away & drop the anchors I added previously (or, if we're going to keep it, we could add more anchors & actually get to the point where we're -Wweak-vtable clean & enable that warning)) On Wed, Jun 12, 2013 at 1:44 PM,

Thanks that helped :). I am still trying to cover add_value some more though since I seem to not understand it totally. I guess it is because I am used to Lucene and Sphinx and Solr and it appears that Xapian seems to attach the type of value stored more on add_value. Like for example I am still a bit confused on how slotno actually works and what it actually is. I think the main thing is