Re: [e-users] xscreensaver messages
Christoph Gysin wrote: > [EMAIL PROTECTED] wrote: > >> 'man patch' has some good info, but I guess what I'm really wanting to >> know is where to get information on the format of patch files so that i >> can understand better how to read them. I don't like the idea of just >> 'patch myfile' without knowing exactly whats getting changed, and the >> whole "+ lines add stuff and -lines remove stuff" is not explanitory >> enough, as there seems to be more information in those files than just >> that. I could be wrong, thats why I'm asking for clarification. > > > Actually, it's not much more than that. > > A patch is generated by diff, a tool to show only the differences of > two files. The most common diff format is the unified diff, generated > with: > > $ diff -u file1 file2 > > The output is then quite simple: > > --- driver/xscreensaver.c.orig2005-08-07 17:36:17.815261536 +0200 > +++ driver/xscreensaver.c2005-08-07 17:37:08.644534312 +0200 > > This shows which files got diff'ed: In our case, I copied the original > one to xscreensaver.c.orig and modified xscreensaver.c. But thats not > interesting. All the patch command needs to know is that this patch > applies to the file xscreensaver.c in the directory driver. > You could also diff whole directories. In the output of the diff > command, theres one such header for each file that has changed. > > @@ -1641,10 +1641,12 @@ > > This marks the part, where the two files differ: in file1, the part > starts at line 1641 and is 10 lines long. in file 2 the part starts at > the same offset (1641) but is 12 lines long. You can see that I've > added two lines in the second file. > >if (hint.res_class) XFree (hint.res_class); > } > > +/* >fprintf (stderr, "%s: %d: unrecognised ClientMessage \"%s\" > received\n", > blurb(), screen, (str ? str : "(null)")); >fprintf (stderr, "%s: %d: for window 0x%lx (%s)\n", > blurb(), screen, (unsigned long) w, wdesc); > +*/ >if (str) XFree (str); > } > > The rest of the patch shows the actual difference, where added lines > are marked with a '+', and removed lines are marked with a '-'. > > In the above example, I simply commented out the part that spits out > the useless error message. > > Christoph Thank you very much. I think that fills in all the blanks for me. Much appreciated! -Sid -- First things first, but not necessarily in that order. - Doctor Who --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
Re: [e-users] xscreensaver messages
[EMAIL PROTECTED] wrote: 'man patch' has some good info, but I guess what I'm really wanting to know is where to get information on the format of patch files so that i can understand better how to read them. I don't like the idea of just 'patch myfile' without knowing exactly whats getting changed, and the whole "+ lines add stuff and -lines remove stuff" is not explanitory enough, as there seems to be more information in those files than just that. I could be wrong, thats why I'm asking for clarification. Actually, it's not much more than that. A patch is generated by diff, a tool to show only the differences of two files. The most common diff format is the unified diff, generated with: $ diff -u file1 file2 The output is then quite simple: --- driver/xscreensaver.c.orig2005-08-07 17:36:17.815261536 +0200 +++ driver/xscreensaver.c2005-08-07 17:37:08.644534312 +0200 This shows which files got diff'ed: In our case, I copied the original one to xscreensaver.c.orig and modified xscreensaver.c. But thats not interesting. All the patch command needs to know is that this patch applies to the file xscreensaver.c in the directory driver. You could also diff whole directories. In the output of the diff command, theres one such header for each file that has changed. @@ -1641,10 +1641,12 @@ This marks the part, where the two files differ: in file1, the part starts at line 1641 and is 10 lines long. in file 2 the part starts at the same offset (1641) but is 12 lines long. You can see that I've added two lines in the second file. if (hint.res_class) XFree (hint.res_class); } +/* fprintf (stderr, "%s: %d: unrecognised ClientMessage \"%s\" received\n", blurb(), screen, (str ? str : "(null)")); fprintf (stderr, "%s: %d: for window 0x%lx (%s)\n", blurb(), screen, (unsigned long) w, wdesc); +*/ if (str) XFree (str); } The rest of the patch shows the actual difference, where added lines are marked with a '+', and removed lines are marked with a '-'. In the above example, I simply commented out the part that spits out the useless error message. Christoph -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" [EMAIL PROTECTED] --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
Re: [e-users] Hello!
Do your backgrounds appear in Emblem? If so, to select one you first choose in the small thumbnail and then click on the bigger. That should change your desktop background.On 8/8/05, Gabriel <[EMAIL PROTECTED]> wrote: Another thing now, can't change background... how come ? :/ I have a tonof backgrounds (edj) and they're in ~/.e/e/backgrounds but I can't change them with emblem...
Re: [e-users] xscreensaver messages
Mathieu wrote: >"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> disait dernièrement que : > > > >>Christoph Gysin wrote: >> >> >> >>>Robert May wrote: >>> >>> >>> Whenever I run xscreensaver I receive the following messages: xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS" received xscreensaver: 12:39:30: 0: for window 0x22e (root) >>>I will explain the problem to the xscreensaver maintainer, and submit >>>a patch. Until the next release, here's a quick fix: >>> >>>--- driver/xscreensaver.c.orig2005-08-07 17:36:17.815261536 +0200 >>>+++ driver/xscreensaver.c2005-08-07 17:37:08.644534312 +0200 >>>@@ -1641,10 +1641,12 @@ >>> if (hint.res_class) XFree (hint.res_class); >>> } >>> >>>+/* >>> fprintf (stderr, "%s: %d: unrecognised ClientMessage \"%s\" >>>received\n", >>>blurb(), screen, (str ? str : "(null)")); >>> fprintf (stderr, "%s: %d: for window 0x%lx (%s)\n", >>>blurb(), screen, (unsigned long) w, wdesc); >>>+*/ >>> if (str) XFree (str); >>> } >>> >>> >>>Christoph >>> >>> >>I have been using linux for close to 10 years now, and enlightenment for >>many of them, so I hate to think of myself as a 'newbie', but I am >>completely self taught, so there are definately some things I don't >>know. This snippet of code for example, I have seen many like this, but >>have absolutely no idea what to do with it. I would love to know how to >>apply this fix, and others like it...could somebody point me to some >>docs that explain this? >> >> > >herm this is a patch or I do not understand this question. >+ lines are lines which are added to the file >- lines are lines which are removed from the file >docs: man patch > >cd ; patch -p < patchfile > >this is a common way to share fixes to be applied to source files, >before recompiling the application. > >but how comes you don't know what a patch is, if you've been using >Linux for 10 years, I just cannot believe it :) >you are a newbie ;) > > > >>As a workaround for this particular problem, I run gnome-settings-daemon >>from the e-exec line or from the 'run' command in e17, this seems to >>handle the xscreensaver without throwing the extra garbage lines in my >>eterm. >> >>Thanks in advance, >>-Sid >> >> > >you are welcome, glad to help a >3-times-longer-I-have-been-using-linux-guy :) > > > Thanks for the info. You really know how to make a guy feel like an idiot. I know its a patch, I've just never cared enough to find out how to use them, as E17s the first thing I have done from cvs, and I've never been in such a situation that I couldn't fix the code I was compiling myself... 'man patch' has some good info, but I guess what I'm really wanting to know is where to get information on the format of patch files so that i can understand better how to read them. I don't like the idea of just 'patch myfile' without knowing exactly whats getting changed, and the whole "+ lines add stuff and -lines remove stuff" is not explanitory enough, as there seems to be more information in those files than just that. I could be wrong, thats why I'm asking for clarification. Thanks again, I think, -Sid --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
Re: [e-users] Hello!
Oppss... I'm sorry.. I was just answering a few emails from gentoo mailing list before this one.. so I messed up a little bit. You're right. Gentoo is not in any way a pre-requisite. FernandoOn 8/8/05, Paulo Jorge de Oliveira Cantante de Matos <[EMAIL PROTECTED]> wrote: Fernando Meira said:> # whereis enlightenment> enlightenment: /usr/bin/enlightenment /usr/lib/enlightenment> /usr/X11R6/bin/enlightenment /usr/bin/X11/enlightenment> /usr/include/enlightenment /usr/share/enlightenment > /usr/man/man1/enlightenment.1.gz> /usr/share/man/man1/enlightenment.1.gz>> but what about: emerge unmerge ??>Am I missing something or emerge/unemerge is all about GentooLinux Distro? I've seen suggestions like this elsewhere but why should "using Gentoo Distro" be a pre-requisite. (OK, I useGentoo but I'm sure many don't use it)Cheers,Paulo Matos> Cheers,> Fernando>> On 8/7/05, Gabriel < [EMAIL PROTECTED]> wrote: Hi AGAIN. ;) I'm gonna redo my enlightenment desktop again, recompile it>> all. This>> time I want to remove EVERYTHING that has to do with >> enlightenment>> before I do anything. So, first off, everything in>> /usr/local/lib/enlightenment, everything in ~/.e/, all syms>> in>> /usr/local/bin ... and then what more? >> --->> SF.Net email is Sponsored by the Better Software Conference &>> EXPO>> September 19-22, 2005 * San Francisco, CA * Development >> Lifecycle>> Practices>> Agile & Plan-Driven Development * Managing Projects & Teams *>> Testing & QA>> Security * Process Improvement & Measurement * >> http://www.sqe.com/bsce5sf>> ___>> enlightenment-users mailing list>> enlightenment-users@lists.sourceforge.net>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users>>> --Paulo Jorge Matos - pocm at sat inesc-id ptWeb: http://sat.inesc-id.pt/~pocmComputer and Software EngineeringINESC-ID - SAT Group
[e-users] Bug in "move_absolute"
Thanx for attention. I found a bug with the binding "move_absolute". Maybe it is reproductible with move_relative but few tries are not enough. Well, take a look: Pre-requesites: got at least one key binding for move_absolute (sry for >80col) enlightenment-remote -binding-key-add ANY Left 'CTRL|ALT' 0 'move_absolute' '+0 *' enlightenment-remote -binding-key-add ANY Right 'CTRL|ALT' 0 'move_absolute' '-0 *' enlightenment-remote -binding-key-add ANY Up'CTRL|ALT' 0 'move_absolute' '* +0' enlightenment-remote -binding-key-add ANY Down 'CTRL|ALT' 0 'move_absolute' '* -0' Open two terminals in a empty virtual desktop. Move second terminal upon the first (with a little down offset). So, let's start the show: Get the focus from the foreground one. Move the window with CTRL|ALT + Right binding. Ok, all could be done. Now, move window in origin position, and repeat exactly same action, with taking attention on the focus of the second one. If you are attentive, you can see the background window steal focus during one millisecond. It's a bit annoying if we repeat quickly many key binding like that, all window are moved instead just one (the focused..). Thanx to developer for fix this little bug :-) -- .around here, everyday is doomsday.. Doomsday - Jonathan Huot Epitech 3 [EMAIL PROTECTED] --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
