similar to: New Compiz Maintainer

Hi Kristian, On Fri, Nov 21, 2014 at 1:37 AM, Kristian Lyngstøl <kristian at bohemians.org> wrote: > For the last few weeks I've been fiddling with the 0.8 code-base, mostly > because compiz got nuked in my distro and I had to do something, if for no > other reason than to have a running WM. You can find my work at: > > https://github.com/KristianLyng/compiz >

For the last few weeks I've been fiddling with the 0.8 code-base, mostly because compiz got nuked in my distro and I had to do something, if for no other reason than to have a running WM. You can find my work at: https://github.com/KristianLyng/compiz (I'm also tracking issues there) I've done what I felt like doing, some of which would've been controversial/problematic 5 years

I have made claims that I have not left the compiz project and that I have been maintaining it over the past 4 years, despite the lack of releases by not fault but my own. At the request of some of the original compiz developers, I am now posting a compilation of some of the contributions I've made over time, since the beginning. Since the most important contributions are code and easiest to

compiz.org hasn't been updated properly in almost half a decade, and there's a lot of misleading or downright wrong information out there right now. There's a launchpad ticket on it [1], but the subject isn't quite covered by a simple bug as it stands. First thing first: Compiz has been using version 0.9 for almost half a decade, and clearly deviated from past conventions of

Hi all, I finally got around to producing an 0.8.10 release. Here are the details, which are also posted on my blog <http://blog.northfield.ws>. It took a bit of setup and cook time but compiz 0.8.10 tarballs are ready now including addons-experimental plugin package. Anyone who has installed compiz before knows it can be confusing so here, I will focus on installing 0.8.10 using the

On 11/10/2014 12:45 PM, Kristian Lyngstøl wrote: > > First thing first: Compiz has been using version 0.9 for almost half a decade, and clearly deviated from past > conventions of using 0.<odd> for development and 0.<even> for stable. In addition, a fourth digit has been added. > > In the long run I'd like to see the project drop the fourth digit and instead go

https://bugs.freedesktop.org/show_bug.cgi?id=104672 Bug ID: 104672 Summary: [NVAC] Compiz segfaults on login on Ubuntu 17.10 with Unity 7 (kernel DRM bug?) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

I would like to use the output from the map function in the package maps for use in, say, the spatstat package. I don't quite understand the coordinates for the border of the state: Example: library(maps) iowa<-map("region","iowa) x<-iowa$x y<-iowa$y There are NA's and duplicated coordinates. What would I need to do to use this in the spatstat owin command?

This is a somewhat controversial subject which I only reluctantly bring up. I honestly believe that open discussion is the only way to run a project, and I apologize in advance if I offend anyone. I got what should have been an easy question on #compiz a few days ago. A user came in and asked "What version do you recommend I use?". I honestly didn't know what to say. >From a

Hi, On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl <kristian at bohemians.org> wrote: > > Feature-wise, Compiz 0.9.12.0 actually has fewer features as I understand it. With the move to OpenGL ES, several plugins got dropped. I understand some of that has been remedied, but 0.9 still does not come out ahead if my understanding is correct. I have asked around and this is what

On Mon, Nov 17, 2014 at 11:11 AM, Sam Spilsbury <smspillaz at gmail.com> wrote: > > On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl > <kristian at bohemians.org> wrote: > > So to sum up: Equal stability, fewer features, but actively maintained. > > > > In the end I told the user in question that 0.9.12.0 is the latest > stable version, but 0.8.9 has

https://bugs.freedesktop.org/show_bug.cgi?id=27501 Summary: nVidia 9600M GT (Macbook Pro current model) is unable to boot Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau

Mornin' all, I've got a trio of quick questions: 1.) Are there archives for the list, 2.) Any trick to installing Qt, 3.) Any tricks, once Qt is set, installing KGPG? Meanwhile, only sending signed web-mail from my knoppix box... -- Robert Thomas ("beau") Hayes Link Open your heart, pray for peace, preach healing (c)2004ISR http://www.semanticrestructuring.com/

For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particular (or all) uid ? WHy would the backend be aware of the transactions on the mailbox ??? There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend,

Duh... src/lib/restrict-process-size.h Should be in the installed include files as well, /usr/include/dovecot/restrict-process-size.h Aki > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I can't find "src/lib/restrict.h" . Is it in dovecot source ? > > > On 2020-11-06 13:20, Aki Tuomi wrote: > > Seems I had

On Sun, Sep 26, 2010 at 09:19:41AM +0800, Sam Spilsbury wrote: >> So I was looking forward to starting my day on a positive note until I >> scroll through the commit logs and see this: >> >> http://git.compiz.org/compiz /plugins/ezoom/commit/?id=aec55753c2b99764dbad6cd77832f0725b62ddcd >> >> Is this seriously how we can expect the project to function? > >

Well, "break-imap-search" option prevent dovecot from starting. I used solr on one server since yesterday. First feedback is that * BODY search is not working * FTS is not really working in headers : For instance, if you search "kliinik" but you type "kliini" (missing one k), the search does not return anything , whereas it shall return more results (as the

for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > Thank you > > I still don't get the "build_key" function. The email (body, hearders, .. and the uid) is the one (and only) to index . What "key" is that function referring to ? Or is the

and finally , for fts_backend_xxxx_lookup_multi, why is that backend dependent ? Would- nt the below function below be the same for any backend ? Waiting fro your feedback on all those questions Thank you JM ----------------- static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, struct mailbox *const boxes[], struct mail_search_arg *args, enum fts_lookup_flags flags,

I have tried to spend some time of understanding the logic (if any !) of the fts part Honestly, the one who created this mess shall be the one to fix it, or one shall refactor it totally. Basically, the fts "core" should be able to do - select the backend according to conf file - send new emails/maiblox to backend - send teh ID of the emails to be removed - resend an entire