Menu
▾
▴
fvwm-themes-devel — Developing FVWM Themes
You can subscribe to this list here.
| 2000 |
Jan
(40) |
Feb
(57) |
Mar
(31) |
Apr
(62) |
May
(15) |
Jun
(38) |
Jul
(46) |
Aug
(50) |
Sep
(13) |
Oct
(41) |
Nov
(65) |
Dec
(36) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(15) |
Feb
(50) |
Mar
(57) |
Apr
(10) |
May
(24) |
Jun
(10) |
Jul
(14) |
Aug
(20) |
Sep
(9) |
Oct
(32) |
Nov
(4) |
Dec
(3) |
| 2002 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
(3) |
May
(15) |
Jun
(23) |
Jul
(11) |
Aug
|
Sep
(6) |
Oct
(7) |
Nov
|
Dec
(30) |
| 2003 |
Jan
(8) |
Feb
(5) |
Mar
(4) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(5) |
Aug
|
Sep
(22) |
Oct
(30) |
Nov
(13) |
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2008 |
Jan
(1) |
Feb
|
Mar
(12) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(10) |
Oct
|
Nov
|
Dec
(4) |
|
From: Olivier C. <oli...@fr...> - 2001-03-09 08:26:44
|
Le Vendredi 9 Mars 2001 04:07, vous avez écrit : > On 08 Mar 2001 17:51:27 -0500, Dan Espen wrote: > > > Anyway, my suggestion is when you try to exec fvwm2 near the > > end of the shell, why don't you use the full path to start it? > > There are pros and cons. I may rething this later. > The script gets --fvwm option to change the executable (default: fvwm2). > You may use it to force your script instead of the true fvwm2. > I am not sure to understand all this path discution. But, I know that at present time fvwm-themes install $bindir (and so fvwm one) should be in the path so that fvwm-themes be fully functional. Regards, Olivier |
|
From: Olivier C. <oli...@fr...> - 2001-03-09 06:37:37
|
Hello, If I well understand the kde2 icons set are "hight" colors KDE icons set. With KDE2 there are a lot of new hight colors icons, so for more themability I would like to change some (a lot) of the icons of the kde2 wm-icons sets and also for consistancy add a 16x16-kde2 icons set (and in the future a 48x48-kde set but not for 0.3.0). Any objection Mikhael? Regards, Olivier |
|
From: David K. <ko...@is...> - 2001-03-09 05:35:46
|
::: What does the uppercase X in the permissions do?
From "man chmod" ...
<snip>
The letters `rwxXstugo' select the new permissions for the
affected users: read (r), write (w), execute (or access for
directories) (x),
--> execute only if the file is a directory or already has execute
permission for some user (X)
</snip>
--
Koo
|
|
From: Dan E. <da...@mk...> - 2001-03-09 04:47:36
|
Mikhael Goikhman <mi...@ho...> writes:
> On 08 Mar 2001 17:00:58 -0500, Dan Espen wrote:
> >
> > make install gives me:
> >
> > /bin/sh ./mkinstalldirs /opt/public/share/fvwm/2.3.30/fvwm
> > for dir in themes images sounds; do \
> > chmod -R o-w,go+rX $dir 2>/dev/null; \
> > rm -rf "/opt/public/share/fvwm/2.3.30/fvwm/$dir"; \
> > (if test -f $dir.tar.gz; then gzip -dc $dir.tar.gz; else \
> > tar cpf - $dir; fi) | (cd "/opt/public/share/fvwm/2.3.30/fvwm" && tar x
> fBp -); \
> > find "/opt/public/share/fvwm/2.3.30/fvwm/$dir" -name CVS -exec rm -r {}
> \; 2>/dev/null ; \
> > done
> > *** Error code 1
> > make: Fatal error: Command failed for target `install-data-local'
> > Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
> > *** Error code 1
> > make: Fatal error: Command failed for target `install-am'
> > Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
> > *** Error code 1
> > make: Fatal error: Command failed for target `install-recursive'
> >
> > This is Solaris 8 with Suns make. Gnumake works fine.
>
> Can you please add some echo lines in this for loop, like:
Its not really a make vs. gnumake issue at all.
I don't know why it seemed that way.
When it does:
for dir in themes images sounds; do \
chmod -R o-w,go+rX $dir
it has no chance of succeeding it needs $(FT_DATADIR)/
before $$dir.
The Solaris shell requires that the "do" "done" block contain a list,
I needed to add an open paren after the do and a close paren before the
done.
What does the uppercase X in the permissions do?
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk...
Piscataway, NJ 08854 Phone: (732) 699-5570
|
|
From: Dan E. <da...@mk...> - 2001-03-09 03:57:41
|
Mikhael Goikhman <mi...@ho...> writes: > On 08 Mar 2001 17:51:27 -0500, Dan Espen wrote: > > > > Last time I ran fvwm themes I had some problems because I don't have > > fvwm2 in my path. What I do have in my path is a shell that starts fvwm2. > > > > I don't know if you were trying to fix that with the logic I see > > in fvwm-themes-start that tries to change the path, but it didn't > > work. Basically, the logic doesn't update my path since there is an > > fvwm2 shell in my path. Unfortunately, I tried to use this same shell > > to start fvwm-themes which got me nowhere. If I ever start using fvwm > > themes, I would still like to use the fvwm2 shell to start it. > > Yes, I tried to fix a case when there is a wrong/old fvwm2 in the path. > Ok, I think I have fixed several Solaris problems in cvs. > > Why exactly your fvwm2 script can't run "fvwm2 -f themes-rc"? :-) > Does it preserve arguments in "$@"? No, $*. It seemed to eat up arguments until it wouldn't execute. > > Anyway, my suggestion is when you try to exec fvwm2 near the > > end of the shell, why don't you use the full path to start it? > > There are pros and cons. I may rething this later. > The script gets --fvwm option to change the executable (default: fvwm2). > You may use it to force your script instead of the true fvwm2. I'm still not sure what would be good regarding the path but you could do: case `which fvwm2` in BUILTINPATH/fvwm2) UPDATE PATH;; esac case `which fvwm-themes-config` in BUILTINPATH/fvwm-themes-config) UPDATE PATH;; esac > > I don't know if thats a good idea or not, but thats what I had to do > > to get this started. > > > > I have display problems now, large parts of my screen appear > > transparent or are not updating when exposed. I guess thats an fvwm2 > > problem. I'm running on Solaris, displaying with Exceed. > > We may do a work around in fvwm-themes if we know what happens. I think just about anything you do in fvwm themes should not cause windows to display incorrectly. > You asked whether $prefix (/usr/local) is used. The answer: depends on the > instalation, by default - no, the original directories of fvwm are used. > Only when someone specifies --prefix, it is used (documented in INSTALL). Ok, it just looks strange in the shell when it doesn't even exist. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Mikhael G. <mi...@ho...> - 2001-03-09 03:10:30
|
On 08 Mar 2001 17:51:27 -0500, Dan Espen wrote: > > Last time I ran fvwm themes I had some problems because I don't have > fvwm2 in my path. What I do have in my path is a shell that starts fvwm2. > > I don't know if you were trying to fix that with the logic I see > in fvwm-themes-start that tries to change the path, but it didn't > work. Basically, the logic doesn't update my path since there is an > fvwm2 shell in my path. Unfortunately, I tried to use this same shell > to start fvwm-themes which got me nowhere. If I ever start using fvwm > themes, I would still like to use the fvwm2 shell to start it. Yes, I tried to fix a case when there is a wrong/old fvwm2 in the path. Ok, I think I have fixed several Solaris problems in cvs. Why exactly your fvwm2 script can't run "fvwm2 -f themes-rc"? :-) Does it preserve arguments in "$@"? > Anyway, my suggestion is when you try to exec fvwm2 near the > end of the shell, why don't you use the full path to start it? There are pros and cons. I may rething this later. The script gets --fvwm option to change the executable (default: fvwm2). You may use it to force your script instead of the true fvwm2. > I don't know if thats a good idea or not, but thats what I had to do > to get this started. > > I have display problems now, large parts of my screen appear > transparent or are not updating when exposed. I guess thats an fvwm2 > problem. I'm running on Solaris, displaying with Exceed. We may do a work around in fvwm-themes if we know what happens. You asked whether $prefix (/usr/local) is used. The answer: depends on the instalation, by default - no, the original directories of fvwm are used. Only when someone specifies --prefix, it is used (documented in INSTALL). Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-03-09 00:50:06
|
On 08 Mar 2001 17:00:58 -0500, Dan Espen wrote:
>
> make install gives me:
>
> /bin/sh ./mkinstalldirs /opt/public/share/fvwm/2.3.30/fvwm
> for dir in themes images sounds; do \
> chmod -R o-w,go+rX $dir 2>/dev/null; \
> rm -rf "/opt/public/share/fvwm/2.3.30/fvwm/$dir"; \
> (if test -f $dir.tar.gz; then gzip -dc $dir.tar.gz; else \
> tar cpf - $dir; fi) | (cd "/opt/public/share/fvwm/2.3.30/fvwm" && tar xfBp -); \
> find "/opt/public/share/fvwm/2.3.30/fvwm/$dir" -name CVS -exec rm -r {} \; 2>/dev/null ; \
> done
> *** Error code 1
> make: Fatal error: Command failed for target `install-data-local'
> Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
> *** Error code 1
> make: Fatal error: Command failed for target `install-am'
> Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
> *** Error code 1
> make: Fatal error: Command failed for target `install-recursive'
>
> This is Solaris 8 with Suns make. Gnumake works fine.
Can you please add some echo lines in this for loop, like:
chmod -R o-w,go+rX $$dir 2>/dev/null; \
echo $$dir 1; \
rm -rf "$(FT_DATADIR)/$$dir"; \
echo $$dir 2; \
...
to try to find a problematic command. I would think the for itself is ok.
Regards,
Mikhael.
|
|
From: Mikhael G. <mi...@ho...> - 2001-03-09 00:18:37
|
On 08 Mar 2001 18:10:46 -0500, Dan Espen wrote: > > When I bring up the color selector, the OK button has a label, but > the other 2 buttons are blank. > > The middle button must be Help since it brings up a window that says > it can't find the documenation. The button on that window is also > blank. These internationalization problems (empty translated labels) should be fixed in the current cvs. I suggest you to set up cvs, it is the same as with fvwm, and you can always update fvwm-themes by one shell command. > Clicking on the third button on the main window causes the crash. Yes, the crush is also caused by pressing the first button as well. > The color bars at the top of the selector are very pretty but I couldn't > figure out what they did. Clicking in various places didn't do anything. It will be easier once Help is readable for you. > If I haven't mentioned it, shame on me, this was all with 0.4.1. We will release 0.4.2 soon, it will include Solaris fixes, but it would be better to test them first. Regards, Mikhael. |
|
From: Dan E. <da...@mk...> - 2001-03-08 23:14:05
|
When I bring up the color selector, the OK button has a label, but the other 2 buttons are blank. The middle button must be Help since it brings up a window that says it can't find the documenation. The button on that window is also blank. Clicking on the third button on the main window causes the crash. The color bars at the top of the selector are very pretty but I couldn't figure out what they did. Clicking in various places didn't do anything. If I haven't mentioned it, shame on me, this was all with 0.4.1. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Dan E. <da...@mk...> - 2001-03-08 23:00:04
|
Last time I ran fvwm themes I had some problems because I don't have fvwm2 in my path. What I do have in my path is a shell that starts fvwm2. I don't know if you were trying to fix that with the logic I see in fvwm-themes-start that tries to change the path, but it didn't work. Basically, the logic doesn't update my path since there is an fvwm2 shell in my path. Unfortunately, I tried to use this same shell to start fvwm-themes which got me nowhere. If I ever start using fvwm themes, I would still like to use the fvwm2 shell to start it. Anyway, my suggestion is when you try to exec fvwm2 near the end of the shell, why don't you use the full path to start it? I don't know if thats a good idea or not, but thats what I had to do to get this started. I have display problems now, large parts of my screen appear transparent or are not updating when exposed. I guess thats an fvwm2 problem. I'm running on Solaris, displaying with Exceed. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Dan E. <da...@mk...> - 2001-03-08 22:25:42
|
Trying to start fvwm-themes I get: [FVWM-Themes]: Welcome to FVWM Themes 0.4.1! /opt/public/src/fvwm/2.3.30/fvwm-themes-start: !: not found /opt/public/src/fvwm/2.3.30/fvwm-themes-start: !: not found Looking at fvwm-themes-start I see: prefix=/usr/local I don't know if thats going to hurt, but I don't have a /usr/local. fvwm-config gave me this: fvwm-themes-0.4.1> fvwm-config --bindir --mandir --fvwm-datadir /opt/public/src/fvwm/2.3.30 /opt/public/man /opt/public/share/fvwm/2.3.30/fvwm I configured with --mandir=/tmp The errors above are from these: if ! which fvwm-themes-config >/dev/null; then which don't appear to be valid on Solaris. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Dan E. <da...@mk...> - 2001-03-08 22:05:40
|
make install gives me:
/bin/sh ./mkinstalldirs /opt/public/share/fvwm/2.3.30/fvwm
for dir in themes images sounds; do \
chmod -R o-w,go+rX $dir 2>/dev/null; \
rm -rf "/opt/public/share/fvwm/2.3.30/fvwm/$dir"; \
(if test -f $dir.tar.gz; then gzip -dc $dir.tar.gz; else \
tar cpf - $dir; fi) | (cd "/opt/public/share/fvwm/2.3.30/fvwm" && tar xfBp -); \
find "/opt/public/share/fvwm/2.3.30/fvwm/$dir" -name CVS -exec rm -r {} \; 2>/dev/null ; \
done
*** Error code 1
make: Fatal error: Command failed for target `install-data-local'
Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
*** Error code 1
make: Fatal error: Command failed for target `install-am'
Current working directory /u/tools/dane/fvwm/fvwm-themes-0.4.1
*** Error code 1
make: Fatal error: Command failed for target `install-recursive'
This is Solaris 8 with Suns make. Gnumake works fine.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk...
Piscataway, NJ 08854 Phone: (732) 699-5570
|
|
From: Dan E. <da...@mk...> - 2001-03-08 21:59:24
|
Olivier Chapuis <oli...@fr...> writes: > Le Mercredi 7 Mars 2001 23:53, vous avez =E9crit : > = > Any report on how fvwm-themes work on Solaris is welcome :o) During configure, I see this: checking for FvwmM4... /opt/public/src//fvwm/2.3.30/FvwmM4 awk: syntax error near line 1 awk: illegal statement near line 1 updating cache ./config.cache It continued, so I will proceed with installation. I'm not subscribed. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: da...@mk... Piscataway, NJ 08854 Phone: (732) 699-5570 |
|
From: Alex W. <aw...@do...> - 2001-03-07 06:33:59
|
I've been trying to alter some components, add button bars etc...(I have several more buttonbar variations to add). I also attempted to create a multi-option sounds component using the modules setup as a guide. Since sound and FvwmEvent is invoked elsewhere(i.e. settings/sound-player) I ran into problems with the Start/Stop AllHooks functions. I think some of these might need reworking in order to properly implement my future design ideas. As a means of keeping my changes separate from the cvs, I simply copied awol theme to testawol/ and edited the files therein. I've uploaded this theme directory as a tarball to http://dove/net/au/~awol/fvwm/testing. testawol.tar.gz = complete theme directory tree. test-sounds.tar.gz = just the sounds dir/'s with .wav files testawol-configs.tar.gz = just the config files (12k attached) I've also placed the source & binaries for kLo_mix and other apps in http://dove.net.au/~awol/fvwm/support. The vol_hori_QT.tgz package is what I used for the added buttonbar. I still have FvwmIconBox's to add yet. I'm hoping someone can find the time to have a look at it and educate me on my mistakes, and perhaps explain how the array/hash in this example actually works, as the creating themes documentation is a little vague. Although I seem to have managed a certain degree of success, I have no idea how I achieved even this much. Trial and error are my most useful guides, so I know there are syntax and other mistakes present. I really do need help integrating this. This soundscapes design BTW is merely a preliminary step towards my actual goal for this component. I'd imagine that FvwmM4 preprocessing like in colors component might be a better way to accomplish what I'm trying to do here, but I'm still figuring that out too. ;-P Finally, I also wondered if having an fvwm-themes soundpath might not be a good idea? ...as I'm having problems with $FVWM_USERDIR not being recognised. And/or a standardised Function for starting an FvwmEvent alias and included in all the hooks? Many thanks in advance! :-) Alex P.S. Style * TitleAtBottom is never reset? |
|
From: Mikhael G. <mi...@ho...> - 2001-03-06 22:24:03
|
Forgotten attachment. Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-03-06 22:17:33
|
Olivier, I want to do the attached changes to 16x16-general. If you like them, please apply, document in icons.lst and prepare 14x14-general versions (they should be manually edited in text editor). I may help if needed. You may also work on kde (low color) and kde2 (high color) icon sets. I will process martys2 and 3dpixmaps icon sets, and will try to do something about 48x48-general (it should really be low color, and otherwise improved, but probably not for 0.3.0). Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-03-01 00:07:26
|
On 27 Feb 2001 23:05:37 +0100, Olivier Chapuis wrote: > > So this set will be not very pretty as a set. I've fixed that (more or less) > for 16x16-gnome but do not have the time to do that with the 48x48 icons. Not critical for 0.3.0. > For laptop utilities as for battery monitor. I've no objection if you > want to replace/remove this name. It may look like this Ok, I am not sure we can find real icons (at least half) of batery for our icon sets, I also don't think batery is a good name (laptop is better), and not essentially needed. So I will remove batery. > > gimp - to have or not to have? I think leaving xv is good. > > No particular advices. I just think that an "application" name > as gimp or xv is not in the idea of wm-icons. However, if you > what to replace xv or battery by gimp I've no objection. I don't want gimp, it is you that wanted to have gimp some time ago. :) It is very popular (something that xv was before/now), so we may add it. Can you add gimp globally without breaking icon set features like the number of colors used? > Which real icons do you plan to add? If I know that I can add > and build some. If not there is a risk that we work on the same > icons and lost our time. I want to work on all icon sets, but you may always work in parallel. I will try not to have uncommited work so we don't duplicate efforts. Regards, Mikhael. |
|
From: Olivier C. <oli...@fr...> - 2001-02-27 22:14:55
|
Mikhael Goikhman wrote: > > On 27 Feb 2001 01:26:33 +0100, Andre Goeree wrote: > > > > On Mon, Feb 26, 2001 at 09:35:17PM +0100, Olivier Chapuis wrote: > > > Andre Goeree wrote: > > > > > > > > Everything works fine! :-) except for this: > > > > When i start Menu Editor: > > > > > > > > Unable to load pixmap None > > I let Olivier to fix this. > I can fix that but this error is not important. > > > > ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > I think I have fixed this. Try again. > I've added some fixes in particular in FvwmScript-Menu. Olivier |
|
From: Olivier C. <oli...@fr...> - 2001-02-27 22:14:52
|
Mikhael Goikhman wrote:
>
> Olivier, more questions to you.
>
> I want to release wm-icons-0.3.0 in two weeks. I think 84 names is good
> enough. I also think that 1.0.0 should not include more than 88/92 names.
>
> How many gnome icon sets do you want to include? You wrote 4 in configure,
> but maybe 16x16 and 48x48 are enough? What is the progress of these?
>
It is a mistake, I plan to add 48x48-gnome only (not very far from being
finish). Unfortunately, I've a problem here: the std gnome icons have 48x48
geometries but if you look only the non transparent part the size is really
variable ... So this set will be not very pretty as a set. I've fixed that
(more or less) for 16x16-gnome but do not have the time to do that with the
48x48 icons.
> Now, let finalize remaining name problems.
>
> battery - I am not sure where this should be used, please give examples,
> where do you want to use it and how it should look.
>
For laptop utilities as for battery monitor. I've no objection if you
want to replace/remove this name. It may look like this
AAAA
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
BBBBBBBBBB
> gimp - to have or not to have? I think leaving xv is good.
>
No particular advices. I just think that an "application" name
as gimp or xv is not in the idea of wm-icons. However, if you
what to replace xv or battery by gimp I've no objection.
> disk-floppy, disk-cd - do we need these names? I have no problems to
> remove them. I have no problems to leave them as well.
>
I think we can leave them.
> module - did you intend it to be used like item, or like a group,
> in the last case it may be named modules. Speaking more practically,
> should we use "modules" for submenus and "item" for module items?
>
Yes, I think like that.
Which real icons do you plan to add? If I know that I can add
and build some. If not there is a risk that we work on the same
icons and lost our time.
Regards, Olivier
|
|
From: Andre G. <abg...@uw...> - 2001-02-27 21:50:11
|
On Tue, Feb 27, 2001 at 09:40:06AM -0600, Mikhael Goikhman wrote: > On 27 Feb 2001 01:26:33 +0100, Andre Goeree wrote: > > > > On Mon, Feb 26, 2001 at 09:35:17PM +0100, Olivier Chapuis wrote: > > > Andre Goeree wrote: > > > > > > > > Everything works fine! :-) except for this: > > > > When i start Menu Editor: > > > > > > > > Unable to load pixmap None > > I let Olivier to fix this. > > > > > ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > I think I have fixed this. Try again. > Yes! it's gone :) > > The difference is that Linux executes the shell with the > > same pid as popen 8-) > > No, this is incorrect. Any unix popen forks a new process and the shell > always gets a new pid. > Correct, now i look at it again, it doesn't seem logical to begin with.... :-} > The difference is in the /bin/sh. GNU bash (/bin/sh on linux) seems to > optimize its command passed in "-c" by adding exec when decired, i.e. when > there are no pipes or similar, while other /bin/sh may fork first. > > Running "sh -c sh" from tcsh on linux gives: > > 1081 pts/1 00:00:00 tcsh > 7706 pts/1 00:00:00 sh > 7708 pts/1 00:00:00 ps > > on freebsd there is one more process: > > 40720 p0 Ss 0:01.90 -tcsh (tcsh) > 40757 p0 S 0:00.00 sh -c sh > 40758 p0 S 0:00.00 sh > 40759 p0 R+ 0:00.00 ps > > When the command has pipes, say (sh -c 'ps | grep " "') there are the same > number of processes on both systems. > > So by using "exec perl" on both systems the perl process has the same > pid that /bin/sh, and its parent pid is the popen pid. > > Now, please let leave all popen disscussions and focus on other problems. :) > Yes, you are right. When i link /bin/sh to /usr/local/bin/bash (stupid, why i didn't try that first :-}) the outcome of popen is the same on both boxes. Thanks for explaining. Regards, Andre. |
|
From: Mikhael G. <mi...@ho...> - 2001-02-27 19:11:06
|
Olivier, more questions to you. I want to release wm-icons-0.3.0 in two weeks. I think 84 names is good enough. I also think that 1.0.0 should not include more than 88/92 names. How many gnome icon sets do you want to include? You wrote 4 in configure, but maybe 16x16 and 48x48 are enough? What is the progress of these? Now, let finalize remaining name problems. battery - I am not sure where this should be used, please give examples, where do you want to use it and how it should look. gimp - to have or not to have? I think leaving xv is good. disk-floppy, disk-cd - do we need these names? I have no problems to remove them. I have no problems to leave them as well. module - did you intend it to be used like item, or like a group, in the last case it may be named modules. Speaking more practically, should we use "modules" for submenus and "item" for module items? Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2001-02-27 15:40:04
|
On 27 Feb 2001 01:26:33 +0100, Andre Goeree wrote: > > On Mon, Feb 26, 2001 at 09:35:17PM +0100, Olivier Chapuis wrote: > > Andre Goeree wrote: > > > > > > Everything works fine! :-) except for this: > > > When i start Menu Editor: > > > > > > Unable to load pixmap None I let Olivier to fix this. > > > ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. I think I have fixed this. Try again. > The difference is that Linux executes the shell with the > same pid as popen 8-) No, this is incorrect. Any unix popen forks a new process and the shell always gets a new pid. The difference is in the /bin/sh. GNU bash (/bin/sh on linux) seems to optimize its command passed in "-c" by adding exec when decired, i.e. when there are no pipes or similar, while other /bin/sh may fork first. Running "sh -c sh" from tcsh on linux gives: 1081 pts/1 00:00:00 tcsh 7706 pts/1 00:00:00 sh 7708 pts/1 00:00:00 ps on freebsd there is one more process: 40720 p0 Ss 0:01.90 -tcsh (tcsh) 40757 p0 S 0:00.00 sh -c sh 40758 p0 S 0:00.00 sh 40759 p0 R+ 0:00.00 ps When the command has pipes, say (sh -c 'ps | grep " "') there are the same number of processes on both systems. So by using "exec perl" on both systems the perl process has the same pid that /bin/sh, and its parent pid is the popen pid. Now, please let leave all popen disscussions and focus on other problems. :) Regards, Mikhael. |
|
From: Andre G. <abg...@uw...> - 2001-02-27 00:22:29
|
On Mon, Feb 26, 2001 at 09:35:17PM +0100, Olivier Chapuis wrote: > Andre Goeree wrote: > > > > On Mon, Feb 26, 2001 at 09:19:09AM +0100, Olivier Chapuis wrote: > > > Andre Goeree wrote: > > > > > > > > On Sun, Feb 25, 2001 at 08:56:48PM +0100, Olivier Chapuis wrote: > > > > 11197 > > > > 11196 > > > > 1 > > > > Not set > > > > Not set > > > > Not set > > > > > > > > There's always a difference of 1 between the two pids. > > > > > > > > > > > > > > Interseting, is the second pid is the pid of the Test > > > > > FvwmScript? > > > > > > > > Yes. > > > > > > > > > > So, we have found how to fix the problem :o) > > > > Great! :-) > > > > > I've just commited this fix. Can you try it (of > > > course you need to rereplace the 1 by the 0 in > > > the my $test = 0/1 line in the perl scripts). > > > > > > > Everything works fine! :-) except for this: > > When i start Menu Editor: > > > > Unable to load pixmap None > > ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > > > Then,if i don't do anything and press "Apply and Save": > > My X freezes :-( and several things appear in the log: > > > > Unable to load pixmap None > > This error is normal :o) The others are not ... I will take a > look. > > > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > mkfifo: .tmp-com-out-menuapp-17815: File exists > > menuapp-17815: cannot open .tmp-com-out-menuapp-17815 > > fvwm-themes-menuapp: internal error 1 > > OS error: No such file or directory > > killing FvwmScript-Menus > > Is FvwmScript-Menus die at this point? > If not can you check again if the pidnum in .tmp-com-lock-*-pidnum > is the same as the corresonding FvwmScript PID. > Yes, FvwmScript dies. The pid from .tmp-com-lock-menuapp is the same as the pid from FvwmScript (before it gets killed;). > > com: menuapp-17815 does not answer the message! > > Unable to load pixmap None > > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > Unable to load pixmap None > > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > menuapp-17970: com give an unvalide unlock! > > com: menuapp-17970 does not answer the message! > > No component 'menus-user' cfg in theme Personal > > > > But when i use Menu Editor as it should (add/modify) > > it works ok, except for a occasional: > > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > > > > The problem was that with BSD popen execute the > > > command as sh -c "command" and that with Linux > > > popen execute the command with sh -c "exec command" > > > (or someting like that). > > No in fact linux does not do that in general. So, in fact > I do not understand why the old command > perl -e 'print getppid . "\n"' > returned the good pid with Linux. In theory, as with BSD and > any UNIX this command return the pid of the shell that use > popen to run this command. I really want to understand this > but it seems that I will not be able to. Mikhael any idea???? The difference is that Linux executes the shell with the same pid as popen 8-) On the Linux box: [ago@igor src]$ ./popen My pid: 466 Calling popen() pids of executed shell are: My ppid: 466 My pid: 467 On the FreeBSD box: ago@mandark$ ./popen My pid: 55185 Calling popen() pids of executed shell are: My ppid: 55186 My pid: 55187 popen is a small C program that i cooked up, it popen()'s another program: pids, pids just returns its ppid and pid. > > > > > Interesting, maybe i want to investigate this a little. > > Has anybody tried this (your fix) on [Open/Net]BSD yet? > > I suspect they work similar as FreeBSD but you never know... > > > > As I just say all UNIX should work as FreeBSD but ... > I have another spare (test) box.. It already runs OpenBSD.. Regards, Andre. |
|
From: Olivier C. <oli...@fr...> - 2001-02-26 20:39:35
|
Andre Goeree wrote: > > On Mon, Feb 26, 2001 at 09:19:09AM +0100, Olivier Chapuis wrote: > > Andre Goeree wrote: > > > > > > On Sun, Feb 25, 2001 at 08:56:48PM +0100, Olivier Chapuis wrote: > > > 11197 > > > 11196 > > > 1 > > > Not set > > > Not set > > > Not set > > > > > > There's always a difference of 1 between the two pids. > > > > > > > > > > > Interseting, is the second pid is the pid of the Test > > > > FvwmScript? > > > > > > Yes. > > > > > > > So, we have found how to fix the problem :o) > > Great! :-) > > > I've just commited this fix. Can you try it (of > > course you need to rereplace the 1 by the 0 in > > the my $test = 0/1 line in the perl scripts). > > > > Everything works fine! :-) except for this: > When i start Menu Editor: > > Unable to load pixmap None > ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > Then,if i don't do anything and press "Apply and Save": > My X freezes :-( and several things appear in the log: > > Unable to load pixmap None This error is normal :o) The others are not ... I will take a look. > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > mkfifo: .tmp-com-out-menuapp-17815: File exists > menuapp-17815: cannot open .tmp-com-out-menuapp-17815 > fvwm-themes-menuapp: internal error 1 > OS error: No such file or directory > killing FvwmScript-Menus Is FvwmScript-Menus die at this point? If not can you check again if the pidnum in .tmp-com-lock-*-pidnum is the same as the corresonding FvwmScript PID. > com: menuapp-17815 does not answer the message! > Unable to load pixmap None > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > Unable to load pixmap None > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > menuapp-17970: com give an unvalide unlock! > com: menuapp-17970 does not answer the message! > No component 'menus-user' cfg in theme Personal > > But when i use Menu Editor as it should (add/modify) > it works ok, except for a occasional: > ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > > > The problem was that with BSD popen execute the > > command as sh -c "command" and that with Linux > > popen execute the command with sh -c "exec command" > > (or someting like that). No in fact linux does not do that in general. So, in fact I do not understand why the old command perl -e 'print getppid . "\n"' returned the good pid with Linux. In theory, as with BSD and any UNIX this command return the pid of the shell that use popen to run this command. I really want to understand this but it seems that I will not be able to. Mikhael any idea???? > > Interesting, maybe i want to investigate this a little. > Has anybody tried this (your fix) on [Open/Net]BSD yet? > I suspect they work similar as FreeBSD but you never know... > As I just say all UNIX should work as FreeBSD but ... Regards, Olivier |
|
From: Andre G. <abg...@uw...> - 2001-02-26 11:56:04
|
On Mon, Feb 26, 2001 at 09:19:09AM +0100, Olivier Chapuis wrote: > Andre Goeree wrote: > > > > On Sun, Feb 25, 2001 at 08:56:48PM +0100, Olivier Chapuis wrote: > > 11197 > > 11196 > > 1 > > Not set > > Not set > > Not set > > > > There's always a difference of 1 between the two pids. > > > > > > > > Interseting, is the second pid is the pid of the Test > > > FvwmScript? > > > > Yes. > > > > So, we have found how to fix the problem :o) Great! :-) > I've just commited this fix. Can you try it (of > course you need to rereplace the 1 by the 0 in > the my $test = 0/1 line in the perl scripts). > Everything works fine! :-) except for this: When i start Menu Editor: Unable to load pixmap None ^+ matches null string many times at [snip]/fvwm-themes-menuapp line 1706, <IN> chunk 26. Then,if i don't do anything and press "Apply and Save": My X freezes :-( and several things appear in the log: Unable to load pixmap None ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. mkfifo: .tmp-com-out-menuapp-17815: File exists menuapp-17815: cannot open .tmp-com-out-menuapp-17815 fvwm-themes-menuapp: internal error 1 OS error: No such file or directory killing FvwmScript-Menus com: menuapp-17815 does not answer the message! Unable to load pixmap None ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. Unable to load pixmap None ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. menuapp-17970: com give an unvalide unlock! com: menuapp-17970 does not answer the message! No component 'menus-user' cfg in theme Personal But when i use Menu Editor as it should (add/modify) it works ok, except for a occasional: ^+ matches null string many times at [snip]/bin/fvwm-themes-menuapp line 1706, <IN> chunk 26. > The problem was that with BSD popen execute the > command as sh -c "command" and that with Linux > popen execute the command with sh -c "exec command" > (or someting like that). As exec exec command is the > same thing that exec command we get a fix for all POSIX > os by replacing > perl -e 'print getppid . "\n"' > by > exec perl -e 'print getppid . "\n"' > Interesting, maybe i want to investigate this a little. Has anybody tried this (your fix) on [Open/Net]BSD yet? I suspect they work similar as FreeBSD but you never know... > Now we can try to work on the core dump ... > Yes! that's still there. Any suggestions about what to try? I think i'm going to try FvwmM4 without themes and see if the same happens. Perhaps we can isolate the problem.. > Thanks again, Olivier No thanks at all, with this fix i can *really* have a go at designing my FreeBSD theme :-) it works a lot easier with some help of the graphical tools. Andre. |
6 messages has been excluded from this view by a project administrator.
