RSS/Atom feed Twitter
Site is read-only, email is disabled

Gimp server startup

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

34 of 37 messages available
Toggle history

Please log in to manage your subscriptions.

Gimp server startup Andrei Simion 26 May 23:57
  Gimp server startup Andrei Simion 27 May 16:07
   Gimp server startup Carol Spears 27 May 17:52
    Gimp server startup Andrei Simion 30 May 16:58
     Gimp server startup Carol Spears 30 May 17:21
     Gimp server startup Sven Neumann 30 May 17:24
      Gimp server startup Andrei Simion 05 Jun 04:44
       Gimp server startup Sven Neumann 06 Jun 00:37
   Gimp server startup Sven Neumann 28 May 02:38
Reply to Considered Harmful [Re: Gimp server startup [OT]] Michael Schumacher 01 Jun 16:54
  Reply to Considered Harmful, Part N Giles 01 Jun 17:05
   Reply to Considered Harmful, Part N Carol Spears 01 Jun 17:50
4243d4c60505270840465badcc@... 07 Oct 20:23
  Gimp server startup Andrei Simion 27 May 18:16
  Gimp server startup Andrei Simion 30 May 16:57
20050527161513.GK10792@gimp... 07 Oct 20:23
  Gimp server startup Andrei Simion 30 May 17:04
   Gimp server startup Sven Neumann 30 May 17:38
   Gimp server startup Carol Spears 30 May 18:08
87vf4zog3k.fsf@gimp.org 07 Oct 20:23
  Gimp server startup Andrei Simion 31 May 15:58
   Gimp server startup Sven Neumann 31 May 17:02
   Gimp server startup Michael Schumacher 31 May 17:24
    Gimp server startup [OT] jernej@ena.si 31 May 18:48
     Reply to Considered Harmful [Re: Gimp server startup [OT]] Alan Horkan 01 Jun 16:22
      Reply to Considered Harmful [Re: Gimp server startup [OT]] GSR - FR 01 Jun 20:47
       Reply to Considered Harmful [Re: Gimp server startup [OT]] Hal V Engel 01 Jun 21:33
  Gimp server startup Andrei Simion 31 May 19:42
   Gimp server startup Irek S?onina 01 Jun 10:09
    Gimp server startup Andrei Simion 01 Jun 17:18
     Gimp server startup Irek S?onina 02 Jun 10:37
      Gimp server startup Andrei Simion 07 Jun 04:07
   Gimp server startup Kevin Cozens 01 Jun 17:34
   Gimp server startup Sven Neumann 01 Jun 17:46
    Gimp server startup Andrei Simion 01 Jun 18:13
     Gimp server startup Sven Neumann 01 Jun 19:20
      Gimp server startup Andrei Simion 01 Jun 23:05
Andrei Simion
2005-05-26 23:57:34 UTC (over 19 years ago)

Gimp server startup

Hi all,

I have to run the Gimp server on a RH machine, but I don't have any clue how it can be started. Where can I find some documentation on that? I mention that the Gimp server will be accesed through a Perl interface.

Regards, Andrei Simion

Andrei Simion
2005-05-27 16:07:59 UTC (over 19 years ago)

Gimp server startup

I managed to start the Gimp server. I read that one of its new features is that you don't need the X to run it. But, when I run an old Perl script I got this warning:

1117202349: accepted unix connection Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264. 1117202349: closing connection 11 (0 requests in 0 seconds)

I think the Perl script needs a display, but this can be obtained only by running X, which I shouldn't run.

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

Thanks, Andrei

Andrei Simion wrote:

Hi all,

I have to run the Gimp server on a RH machine, but I don't have any clue how it can be started. Where can I find some documentation on that? I mention that the Gimp server will be accesed through a Perl interface.

Regards, Andrei Simion

Carol Spears
2005-05-27 17:52:18 UTC (over 19 years ago)

Gimp server startup

On Fri, May 27, 2005 at 10:07:59AM -0400, Andrei Simion wrote:

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

no they dont.

carol

Andrei Simion
2005-05-27 18:16:54 UTC (over 19 years ago)

Gimp server startup

Seth Burgess wrote:

How exactly are you running it? If you're not supplying the parameters to it, it will try to start the dialog, which will require Gtk which requires an X server.

I started the gimp server using this:

gimp --no-interface --batch '(extension-perl-server 0 0 0)' &

The script looks like this:

#!/usr/bin/perl

use Gimp ":auto"; use Gimp::Fu;

# create a footer image

sub newimage { my ($width, $height,
$backgroundcolor, $foregroundcolor, $borderSize, $borderColor,
$typeFace, $typeSize, $typeColor, $dividerAboveSize, $dividerAboveWidth, $dividerAboveColor, $text,
$dividerBelowSize, $dividerBelowWidth, $dividerBelowColor, $divider_offset
) = @_;

# Create a new image $img = gimp_image_new($width, $height, RGB);

# Create a new layer $layer = gimp_layer_new($img, $width, $height, RGB, "Layer 1", 0, NORMAL_MODE);

# define the background colors # $backgroundcolor = "#0000FF"; # blue # $foregroundcolor = "#FF0000"; # red # $backgroundcolor = $color1;
# $foregroundcolor = $color2;

gimp_palette_set_background($backgroundcolor); gimp_palette_set_foreground($foregroundcolor);

# add the layer to the image gimp_image_add_layer($img, $layer, -1);

# gimp_selection_all($img); gimp_layer_add_alpha($layer);
gimp_drawable_fill($layer,TRANS_IMAGE_FILL); # gimp_selection_border($img, 3); #script_fu_addborder($img, $layer, 3, 3, "#000000", "100");

# gimp_palette_set_background("#000000");

# change the foreground color gimp_palette_set_background($borderColor);

# draw the border # define first region
gimp_rect_select ($img, 0, 0, $width, $borderSize, 2, 0, 0); # (x1, y1, x2, y2)
# fill the region
gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# define the second region $height_sec_region = $height - $borderSize; gimp_rect_select ($img, 0, $height_sec_region, $width, $height, 2, 0, 0);
# fill the second region
gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# define the left lateral region gimp_rect_select($img, 0, 0, $borderSize, $height, 2, 0, 0); # fill the region
gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# define the right lateral region $width_lat_region = $width - $borderSize; gimp_rect_select($img, $width_lat_region, 0, $width, $height, 2, 0, 0); # fill the region
gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# create the dividers # upper divider
# calculate the width of divider $x_start_above_div = (($width - ($dividerAboveWidth/100) * $width)/2) + $borderSize;
$x_end_above_div = ($dividerAboveWidth/100) * $width - $borderSize * 2; gimp_rect_select($img, $x_start_above_div, $divider_offset, $x_end_above_div, $dividerAboveSize, 2, 0, 0); # fill the region
# change the background color
gimp_palette_set_background($dividerAboveColor); gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# lower divider # calculate the y coordinates for the divider $y_start_below_div = $height - ($divider_offset+$dividerBelowSize); $y_end_below_div = $dividerBelowSize; # calculate the width of divider $x_start_below_div = (($width - ($dividerBelowWidth/100) * $width)/2) + $borderSize;
$x_end_below_div = ($dividerBelowWidth/100) * $width - $borderSize * 2; gimp_rect_select($img, $x_start_below_div, $y_start_below_div, $x_end_below_div, $y_end_below_div, 2, 0, 0); # fill the region
# change the background color
gimp_palette_set_background($dividerBelowColor); gimp_bucket_fill($layer,BG_BUCKET_FILL,0,100,100,0,0,0);

# my $font = qq{-*-agenda-medium-r-normal-*-24-*-*-*-*-*-*-*};

# set the foreground with the font color gimp_palette_set_foreground($typeColor); my $text_layer = gimp_text_fontname($layer, 0, 0, $text, -1, #border 1, #antialias $typeSize, #size 0, #size type $typeFace );

# determine the position of the text my $texty = $height/2 - $text_layer->height/2; my $textx = $width/2 - $text_layer->width/2;

# pull out text layer we were checking size and fonts on. gimp_image_remove_layer($img,$text_layer);

# create again the layer $text_layer = gimp_text_fontname($layer, $textx, $texty, $text, -1, #border 1, #antialias $typeSize, #size 0, #size type $typeFace );

gimp_floating_sel_anchor($text_layer);

# draw the border (cannot define its width) # script_fu_addborder($img, $layer, 3, 3, "#000000", "1");

#$layer2 = gimp_layer_new($img, 725, 5, RGB, "Layer 2", 0, NORMAL_MODE);
#gimp_image_add_layer($img, $layer2, -1); #gimp_selection_all($img);
#gimp_layer_add_alpha($layer2); #gimp_drawable_fill($layer2,FG_IMAGE_FILL);

# Set the background to the required color # gimp_palette_set_foreground($color1); # gimp_palette_set_background($color2);

# Paint the layer #gimp_edit_fill($layer, BG_IMAGE_FILL); #gimp_edit_fill($layer2, FG_IMAGE_FILL);

# delete the image # gimp_image_delete($img);
# Return the image
return $img;
}

register
"newimage2", # fill in name "Create a footer", # a small description "gimp", # a help text
"Andrei Simion", # Your name "", # Your copyright
"2005-04-17", # Date "/Xtns/Perl-Fu/Tutorial/newimage", # menu path "*", # Image types [
[PF_INT, "width", "Img width", "725"], [PF_INT, "height", "Img height", "80"], [PF_COLOR, "bckg_color", "background color", [255,0,0]], [PF_COLOR, "fg_color", "foreground color", [0, 0, 255]], [PF_INT, "border_size", "Border size", "1"], [PF_COLOR, "border_color", "border color", [0, 0, 255]], [PF_FONT, "font", "font", "-*-utopia-bold-r-*-*-70-*-*-*-*-*-*-*"], [PF_INT, "font_size", "Font size", "32"], [PF_COLOR, "font_color", "Font color", [0, 0, 255]], [PF_INT, "divider_above_size", "Divider above size", "1"], [PF_INT, "divider_above_width", "Divider above width", "100"], [PF_COLOR, "divider_above_color", "Divider above color", [0, 0, 255]],
[PF_STRING,"text", "Text", "some text"], [PF_INT, "divider_below_size", "Divider below size", "1"], [PF_INT, "divider_below_width", "Divider below width", "100"], [PF_COLOR, "divider_below_color", "Divider below color", [0, 0, 255]],
[PF_INT, "divider_offset", "Divider offset", "10"] ],
\&newimage;

exit main();

Andrei

On 5/27/05, Andrei Simion wrote:

I managed to start the Gimp server. I read that one of its new features is that you don't need the X to run it. But, when I run an old Perl script I got this warning:

1117202349: accepted unix connection Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264. 1117202349: closing connection 11 (0 requests in 0 seconds)

I think the Perl script needs a display, but this can be obtained only by running X, which I shouldn't run.

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

Thanks, Andrei

Andrei Simion wrote:

Hi all,

I have to run the Gimp server on a RH machine, but I don't have any clue how it can be started. Where can I find some documentation on that? I mention that the Gimp server will be accesed through a Perl interface.

Regards, Andrei Simion

Sven Neumann
2005-05-28 02:38:31 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

I managed to start the Gimp server. I read that one of its new features is that you don't need the X to run it. But, when I run an old Perl script I got this warning:

1117202349: accepted unix connection Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264.
1117202349: closing connection 11 (0 requests in 0 seconds)

I think the Perl script needs a display, but this can be obtained only by running X, which I shouldn't run.

GIMP 2.x doesn't need a display if run with the --no-interface option. That doesn't hold true if you want to use any plug-ins that open an X11 conncetion on their own. I wouldn't have expected the perl server to do that though.

Can someone reproduce this problem?

Sven

Andrei Simion
2005-05-30 16:57:59 UTC (over 19 years ago)

Gimp server startup

Seth Burgess wrote:

How exactly are you running it? If you're not supplying the parameters to it, it will try to start the dialog, which will require Gtk which requires an X server.

I'm running it using the folowing:

gimp --no-interface --batch '(extension-perl-server 0 0 0)' &

Andrei

On 5/27/05, Andrei Simion wrote:

I managed to start the Gimp server. I read that one of its new features is that you don't need the X to run it. But, when I run an old Perl script I got this warning:

1117202349: accepted unix connection Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264. 1117202349: closing connection 11 (0 requests in 0 seconds)

I think the Perl script needs a display, but this can be obtained only by running X, which I shouldn't run.

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

Thanks, Andrei

Andrei Simion wrote:

Hi all,

I have to run the Gimp server on a RH machine, but I don't have any clue how it can be started. Where can I find some documentation on that? I mention that the Gimp server will be accesed through a Perl interface.

Regards, Andrei Simion

Andrei Simion
2005-05-30 16:58:06 UTC (over 19 years ago)

Gimp server startup

Carol Spears wrote:

On Fri, May 27, 2005 at 10:07:59AM -0400, Andrei Simion wrote:

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

no they dont.

So I have to use other APIs like the new Gimp module.

Could you explain me to what extent I have to rewrite the code?

Thanks, Andrei

carol

Andrei Simion
2005-05-30 17:04:27 UTC (over 19 years ago)

Gimp server startup

Carol Spears wrote:

On Fri, May 27, 2005 at 12:10:35PM -0400, Andrei Simion wrote:

Carol Spears wrote:

On Fri, May 27, 2005 at 10:07:59AM -0400, Andrei Simion wrote:

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

no they dont.

Thank you. I have the Gimp Perl module installed. I think this is the API I should use. But is there any documentation/tutorial on that excepting the man page?

the gimp-perl stuff is the least maintained of the scripting stuff (that is working).

the gimp parts are fairly easy to determine via the Procedure Browser.

i suggest getting the cvs source and reading the existing scripts. i was working on minor updating to some of those scripts (which is sad because there are so many who profited from this who are trained and capable of fixing it -- i am neither capable nor have i profited).

And where is the cvs source? Are you talking about the source code for the gimp server? Are there perl scripts that access the server there?

Thanks, Andrei

Carol Spears
2005-05-30 17:21:55 UTC (over 19 years ago)

Gimp server startup

On Mon, May 30, 2005 at 10:58:06AM -0400, Andrei Simion wrote:

Carol Spears wrote:

On Fri, May 27, 2005 at 10:07:59AM -0400, Andrei Simion wrote:

Another question would be whether the old Perl scripts (written for 1.x versions of Gimp) run on 2.2.

no they dont.

So I have to use other APIs like the new Gimp module.

Could you explain me to what extent I have to rewrite the code?

did you look at the scripts and read the error messages?

the scripts that i fixed, i read the error messages and fixed them. i have more knowledge of gimp than of its scripting languages.

one of the scripts was obviously broken within the perl module and i understand enough perl to know that i am the wrong person to be fixing these things.

all of this i learned by loading the scripts into gimp, running them and seeing the messages. while i do not suggest this is the correct approach to answering your questions, it answered that question for me.

plug-ins with the gui tell the deprecated code bits and the replacements in a select and paste-able dialog.

carol

Sven Neumann
2005-05-30 17:24:26 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

Could you explain me to what extent I have to rewrite the code?

Only very little has changed, there is a good chance that your script will work with no or only very little changes. You will switch from XLFD font names to the easier fontconfig names GIMP is using now. A couple of functions have been renamed. You can find a comprehensive list in the libgimp/gimpcompat.h header. If you have problems, feel free to ask.

Sven

Sven Neumann
2005-05-30 17:38:05 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

And where is the cvs source?

http://gimp.org/source/#gimp_from_cvs http://developer.gimp.org/cvs.html

Sven

Carol Spears
2005-05-30 18:08:04 UTC (over 19 years ago)

Gimp server startup

On Mon, May 30, 2005 at 11:04:27AM -0400, Andrei Simion wrote:

Carol Spears wrote:

i suggest getting the cvs source and reading the existing scripts. i was working on minor updating to some of those scripts (which is sad because there are so many who profited from this who are trained and capable of fixing it -- i am neither capable nor have i profited).

And where is the cvs source? Are you talking about the source code for the gimp server? Are there perl scripts that access the server there?

i made sure that information about how to get the gimp things from cvs is available on the gimp web site. while it does not directly explain how to get the perl module, it takes only a little jump in logic and perhaps some limited reading of gnomecvs documentation to get the all of the gimp source modules via cvs checkout.

it would be helpful to me if you can tell me how successful you can be at finding this information from http://www.gimp.org, understanding of course that it is set up for the non-programmer and needs people with programming background to understand more on their own.

i think it would be better to fix the information that has been online for years than it would be to explain this to you.

let me know how it goes, carol

Andrei Simion
2005-05-31 15:58:39 UTC (over 19 years ago)

Gimp server startup

Sven Neumann wrote:

Hi,

Andrei Simion writes:

When I start the Gimp server with this command:

gimp --no-interface --batch '(extension-perl-server 0 0 0)' &

I got these messages:

GIMP is not properly installed for the current user. User installation was skipped because the '--no-interface' flag was used. To perform user installation, run the GIMP without the --no-interface' flag.

GIMP: Could not open '/home/gimp/.gimp-2.2/pluginrc' for writing: No such file or directory

GIMP: Unable to open a test swap file. To avoid data loss please check the location and permissions of the swap directory defined in your Preferences (currently "${gimp_dir}").

You have obviously not done the user installation for gimp yet. You need to run gimp once with a user interface so that it creates the user ~/.gimp-2.2 folder.

The reason I haven't done that was because there was no X server instaled and I presume the user installation can be done only by starting Gimp in the graphical interface, am I wright?

But could you please stop sending me private email and use the mailing-list instead? Thank you.

Sorry about that. There is an explanation for this. This mailing list is set up that when someone sends an email on it, it has the "to" header field to the original sender and a cc to the list. Replying to this message would send one email to the email address in the "to" field. Sometimes I forget to replace the private address I'm replying to with the mailing list address. And this happened to me too as other members of the list replied only to me personally. Maybe something has to be done regarding the list configuration.

Andrei

Sven

Sven Neumann
2005-05-31 17:02:19 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

The reason I haven't done that was because there was no X server instaled and I presume the user installation can be done only by starting Gimp in the graphical interface, am I wright?

A patch to change that would be very much appreciated. But you can easily work around it by copying a ~/.gimp-2.2 folder from a different computer.

But could you please stop sending me private email and use the mailing-list instead? Thank you.

Sorry about that. There is an explanation for this. This mailing list is set up that when someone sends an email on it, it has the "to" header field to the original sender and a cc to the list. Replying to this message would send one email to the email address in the "to" field. Sometimes I forget to replace the private address I'm replying to with the mailing list address. And this happened to me too as other members of the list replied only to me personally. Maybe something has to be done regarding the list configuration.

The list configuration is fine. This is how a mailing-list is supposed to be set up. Munging the Reply-To: field is a bad thing to do (see http://www.unicom.com/pw/reply-to-harmful.html).

Sven

Michael Schumacher
2005-05-31 17:24:01 UTC (over 19 years ago)

Gimp server startup

Andrei Simion wrote:

Sorry about that. There is an explanation for this. This mailing list is set up that when someone sends an email on it, it has the "to" header field to the original sender and a cc to the list. Replying to this message would send one email to the email address in the "to" field. Sometimes I forget to replace the private address I'm replying to with the mailing list address. And this happened to me too as other members of the list replied only to me personally. Maybe something has to be done regarding the list configuration.

This is intentional - google for "reply to considered harmful".

HTH, Michael

jernej@ena.si
2005-05-31 18:48:58 UTC (over 19 years ago)

Gimp server startup [OT]

On Tuesday, May 31, 2005, 17:24:01, Michael Schumacher wrote:

This is intentional - google for "reply to considered harmful".

This might have been of concern years ago, before people were used to mailing lists which do set the Reply-to header. Nowadays, I'd say that the opposite is true, since setting the Reply-to header seems common practice (at least if I look at the mailing lists I'm following, there are only 2 that don't set the header).

Andrei Simion
2005-05-31 19:42:35 UTC (over 19 years ago)

Gimp server startup

Hi again,

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface --batch \('extension-perl-server 0 0 0'\)

and I get this error:

Invalid option "--display"

I tried different "--display" options: ":1", ":1.0", "1.0". The result was the same.

I mention that the 1.3 version of Gimp started with "--display :1.0".

I took the display option out of the startup command and the gimp server started. But, when I was running a script I got the same error as when I started the Gimp server without the X:

1117560504: accepted tcp connection from 127.0.0.1:32855 Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264. 1117560504: closing connection 11 (1 requests in 0 seconds)

Thanks, Andrei

Sven Neumann wrote:

Hi,

Andrei Simion writes:

When I start the Gimp server with this command:

gimp --no-interface --batch '(extension-perl-server 0 0 0)' &

I got these messages:

GIMP is not properly installed for the current user. User installation was skipped because the '--no-interface' flag was used. To perform user installation, run the GIMP without the --no-interface' flag.

GIMP: Could not open '/home/gimp/.gimp-2.2/pluginrc' for writing: No such file or directory

GIMP: Unable to open a test swap file. To avoid data loss please check the location and permissions of the swap directory defined in your Preferences (currently "${gimp_dir}").

You have obviously not done the user installation for gimp yet. You need to run gimp once with a user interface so that it creates the user ~/.gimp-2.2 folder.

But could you please stop sending me private email and use the mailing-list instead? Thank you.

Sven

Irek S?onina
2005-06-01 10:09:02 UTC (over 19 years ago)

Gimp server startup

Andrei Simion wrote:

Hi again,

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface --batch \('extension-perl-server 0 0 0'\)

and I get this error:

Invalid option "--display"

I tried different "--display" options: ":1", ":1.0", "1.0". The result was the same.

I would guess that if you are using --no-interface then you can't use at the same time --display... try to use --display to connect to Xvfb, but without --no-interface.
I do not know if it will help you but I am running script-fu-server with following command:

/usr/bin/gimp -c -i -s -b '(plug-in-script-fu-server 1 10008 \"/tmp/gimpserverlog\")' '(gimp-quit 1)' 1>/tmp/gimprunlog 2>/tmp/gimperrlog &

Maybe try --display :1.0 -c -s, without no-interface.

Regards, Irek Slonina

Alan Horkan
2005-06-01 16:22:03 UTC (over 19 years ago)

Reply to Considered Harmful [Re: Gimp server startup [OT]]

On Tue, 31 May 2005 jernej@ena.si wrote:

Date: Tue, 31 May 2005 18:48:58 +0200 From: jernej@ena.si
To: gimp-developer@lists.xcf.berkeley.edu Subject: Re: [Gimp-developer] Gimp server startup [OT]

On Tuesday, May 31, 2005, 17:24:01, Michael Schumacher wrote:

This is intentional - google for "reply to considered harmful".

This might have been of concern years ago, before people were used to mailing lists which do set the Reply-to header. Nowadays, I'd say that the opposite is true, since setting the Reply-to header seems common practice (at least if I look at the mailing lists I'm following, there are only 2 that don't set the header).

The problem is still the same.

It is better to accidentally mail only one person and need to resend to the list than it is to accidentally send mail to many people.

- Alan

Michael Schumacher
2005-06-01 16:54:31 UTC (over 19 years ago)

Reply to Considered Harmful [Re: Gimp server startup [OT]]

Von: Alan Horkan

On Tue, 31 May 2005 jernej@ena.si wrote:

On Tuesday, May 31, 2005, 17:24:01, Michael Schumacher wrote:

This is intentional - google for "reply to considered harmful".

This might have been of concern years ago, before people were used to mailing lists which do set the Reply-to header. Nowadays, I'd say that

the

opposite is true, since setting the Reply-to header seems common

practice

(at least if I look at the mailing lists I'm following, there are only 2 that don't set the header).

The problem is still the same.

It is better to accidentally mail only one person and need to resend to the list than it is to accidentally send mail to many people.

Well, let's just say that I tend to ignore private mail that is sent to me from a mailing list participant if it still has the subject used on the list, especially if it still contains the list markers ([gimp-user] etc). Sometimes, this is just accidently - I get the mail, rush through it, don't have an answer readily available and since it still has the marker, I assume it went to the list and someone else might answer it.

Sometimes, a question pops up what makes me think "why couldn't the sender have posted this to the list or have searched the archives?". Especially when I don't have much time, I knowingly ignore these messages.

Or, in just one sentence:

When posting to a mailing list, I expect replies (either to or from the list) to end up on the list.

The following is IMO:

Not munging the reply-to header should be considered harmful. Not doing it makes it harder than needed for many people - usually the people who would be able to help the person who posted the question - to reply to as many people as possible. And making this harder is is not the purpose of a mailing list, is it?

Michael

Giles
2005-06-01 17:05:12 UTC (over 19 years ago)

Reply to Considered Harmful, Part N

Here, in a nutshell, are the two sides of the argument:

On Wed, Jun 01, 2005 at 03:22:03PM +0100, Alan Horkan wrote:

It is better to accidentally mail only one person and need to resend to the list than it is to accidentally send mail to many people.

On Wed, Jun 01, 2005 at 04:54:31PM +0200, Michael Schumacher wrote:

Not munging the reply-to header should be considered harmful. Not doing it makes it harder than needed for many people - usually the people who would be able to help the person who posted the question - to reply to as many people as possible. And making this harder is is not the purpose of a mailing list, is it?

I tend to agree with Alan, and disagree with "making this harder is is not the purpose of a mailing list, is it?" It does make it more difficult, but less embarrassing. I think that's the crux of it. Having sent out mass mailings that embarrassed me considerably a couple times because of reply-to-all on a list, I'm all in favour of the single person reply.

P.S. "Who the hell is 'Giles?'" I'm lurking with the intention of asking for some weird help once I've made sure I'm not going to sound too stupid. Suspenseful, isn't it?

-------------------------------------------------------------- Giles giles@dreaming.org http://www.gilesorr.com/
--------------------------------------------------------------

Andrei Simion
2005-06-01 17:18:00 UTC (over 19 years ago)

Gimp server startup

Irek S?onina wrote:

Andrei Simion wrote:

Hi again,

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface --batch \('extension-perl-server 0 0 0'\)

and I get this error:

Invalid option "--display"

I tried different "--display" options: ":1", ":1.0", "1.0". The result was the same.

I would guess that if you are using --no-interface then you can't use at the same time --display... try to use --display to connect to Xvfb, but without --no-interface.
I do not know if it will help you but I am running script-fu-server with following command:

/usr/bin/gimp -c -i -s -b '(plug-in-script-fu-server 1 10008 \"/tmp/gimpserverlog\")' '(gimp-quit 1)' 1>/tmp/gimprunlog 2>/tmp/gimperrlog &

Maybe try --display :1.0 -c -s, without no-interface.

Thanks Irek, I'll try your command. The thing is that the 1.3 version of gimp worked just fine with my command. To clear the things out: are you connecting to the Gimp server through some kind of interface or you work with the Gimp in the graphic mode?

Thanks again, Andrei Simion

Kevin Cozens
2005-06-01 17:34:22 UTC (over 19 years ago)

Gimp server startup

Andrei Simion wrote:

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface --batch \('extension-perl-server 0 0 0'\)

If the above is all you have done, you have not done what Sven told you to do. After starting X you need to run gimp once without any arguments to let it run its installation steps. After it has completed its installation steps you may then try starting the server once more.

Sven Neumann
2005-06-01 17:46:11 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface

You cannot combine --display and --no-interface. If you don't want any user interface, then you don't need a display.

I took the display option out of the startup command and the gimp server started. But, when I was running a script I got the same error as when I started the Gimp server without the X:

1117560504: accepted tcp connection from 127.0.0.1:32855 Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264.
1117560504: closing connection 11 (1 requests in 0 seconds)

What about setting the DISPLAY environment variable for the perl server (if it really needs a display) ?

Sven

Carol Spears
2005-06-01 17:50:57 UTC (over 19 years ago)

Reply to Considered Harmful, Part N

On Wed, Jun 01, 2005 at 11:05:12AM -0400, Giles wrote:

P.S. "Who the hell is 'Giles?'" I'm lurking with the intention of asking for some weird help once I've made sure I'm not going to sound too stupid. Suspenseful, isn't it?

with me on this list, you will never look too stupid. ask away.

carol

Andrei Simion
2005-06-01 18:13:09 UTC (over 19 years ago)

Gimp server startup

Sven Neumann wrote:

Hi,

Andrei Simion writes:

I managed to start X:

Xvfb :1.0 -screen 0 10x10x16

So, the display is 1.

Now, I start the Gimp server:

gimp --display 1 --no-interface

You cannot combine --display and --no-interface. If you don't want any user interface, then you don't need a display.

I presume you need. Firstly, the 1.3 Gimp server worked fine with it. Secondly, if you start a the Xvfb (X virtual frame buffer) and assign a display for it, it means in my opinion that the Gimp has a display to output the images to. About the --no-interface, it means that you don't need the graphical interface of the Gimp, which is obvious as you run the Gimp in the server mode.

I took the display option out of the startup command and the gimp server started. But, when I was running a script I got the same error as when I started the Gimp server without the X:

1117560504: accepted tcp connection from 127.0.0.1:32855 Gtk-WARNING **: cannot open display: at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Gimp.pm line 264.
1117560504: closing connection 11 (1 requests in 0 seconds)

What about setting the DISPLAY environment variable for the perl server (if it really needs a display) ?

You mean a DISPLAY variable in each script?

What we have to keep in mind is that the 1.3 version of the Gimp server worked fine in this configuration (the Xvfb and Gimp startup). Now, with the 2.2 I have problems and there is no documentation at all, except for the man page that doesn't say anything for my problem).

Thanks, Andrei

Sven

Sven Neumann
2005-06-01 19:20:03 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

What about setting the DISPLAY environment variable for the perl server (if it really needs a display) ?

You mean a DISPLAY variable in each script?

No, I mean setting DISPLAY in the environment you start GIMP and the perl-server from.

What we have to keep in mind is that the 1.3 version of the Gimp server worked fine in this configuration (the Xvfb and Gimp startup). Now, with the 2.2 I have problems and there is no documentation at all, except for the man page that doesn't say anything for my problem).

GIMP 1.3 is an unsupported development release. Nothing that worked there has ever been guarenteed to work in any later releases. Your choice to continue using GIMP 1.3 but don't expect any support from anyone then.

Sven

GSR - FR
2005-06-01 20:47:35 UTC (over 19 years ago)

Reply to Considered Harmful [Re: Gimp server startup [OT]]

Hi,
horkana@maths.tcd.ie (2005-06-01 at 1522.03 +0100):

This is intentional - google for "reply to considered harmful".

This might have been of concern years ago, before people were used to mailing lists which do set the Reply-to header. Nowadays, I'd say that the opposite is true, since setting the Reply-to header seems common practice (at least if I look at the mailing lists I'm following, there are only 2 that don't set the header).

The problem is still the same.
It is better to accidentally mail only one person and need to resend to the list than it is to accidentally send mail to many people.

After seeing this talk many times in many lists I think the issue is "dumb mail apps considered harmful".

Instead of bringing up the thing about reply-to again and again, use mail apps that understand the concept of mailing list. Some apps had that feature for some time already so it must not be so hard to implement, and in some cases it could even be auto detected based in headers (wow, and solve the unsubscribe problem too when you are at it). If the app you like does not, fill a bug. I guess it will be easier than convicing every mailing list admin.

When there is a button or function that is reply list and other reply person, how the list is set does not matter.

GSR

Hal V Engel
2005-06-01 21:33:36 UTC (over 19 years ago)

Reply to Considered Harmful [Re: Gimp server startup [OT]]

On Wednesday 01 June 2005 11:47 am, GSR - FR wrote:

Hi,

horkana@maths.tcd.ie (2005-06-01 at 1522.03 +0100):

This is intentional - google for "reply to considered harmful".

This might have been of concern years ago, before people were used to mailing lists which do set the Reply-to header. Nowadays, I'd say that the opposite is true, since setting the Reply-to header seems common practice (at least if I look at the mailing lists I'm following, there are only 2 that don't set the header).

The problem is still the same.
It is better to accidentally mail only one person and need to resend to the list than it is to accidentally send mail to many people.

After seeing this talk many times in many lists I think the issue is "dumb mail apps considered harmful".

Instead of bringing up the thing about reply-to again and again, use mail apps that understand the concept of mailing list. Some apps had that feature for some time already so it must not be so hard to implement, and in some cases it could even be auto detected based in headers (wow, and solve the unsubscribe problem too when you are at it). If the app you like does not, fill a bug. I guess it will be easier than convicing every mailing list admin.

When there is a button or function that is reply list and other reply person, how the list is set does not matter.

I agree 100%. I am using kmail and it handles mailing lists very nicely with only a minimal effort to set it up. I am never confused about who I am replying to. I am sure that there are other examples of email readers that are mailing list smart.

Hal

Andrei Simion
2005-06-01 23:05:43 UTC (over 19 years ago)

Gimp server startup

Sven Neumann wrote:

Hi,

Andrei Simion writes:

What about setting the DISPLAY environment variable for the perl server (if it really needs a display) ?

You mean a DISPLAY variable in each script?

No, I mean setting DISPLAY in the environment you start GIMP and the perl-server from.

Already did that and got the same result.

Thanks, Andrei

Irek S?onina
2005-06-02 10:37:51 UTC (over 19 years ago)

Gimp server startup

Andrei Simion wrote:

Irek S?onina wrote:

/usr/bin/gimp -c -i -s -b '(plug-in-script-fu-server 1 10008 \"/tmp/gimpserverlog\")' '(gimp-quit 1)' 1>/tmp/gimprunlog 2>/tmp/gimperrlog &

Maybe try --display :1.0 -c -s, without no-interface.

Thanks Irek, I'll try your command. The thing is that the 1.3 version of gimp worked just fine with my command. To clear the things out: are you connecting to the Gimp server through some kind of interface or you work with the Gimp in the graphic mode?

I am connecting to a server with python script by Tjabo Kloppenburg sending to a server my script-fu, all without interface and without Xvfb. If you want a script just tell.

-- Irek S?onina

Andrei Simion
2005-06-05 04:44:30 UTC (over 19 years ago)

Gimp server startup

Hi,

Sven Neumann wrote:

Hi,

Andrei Simion writes:

Could you explain me to what extent I have to rewrite the code?

Only very little has changed, there is a good chance that your script will work with no or only very little changes. You will switch from XLFD font names to the easier fontconfig names GIMP is using now. A

Regarding the fonts, where I can find the new font names? I finally managed to get Gimp running. But, when I got a script running I got this: Illegal default font description for perl_fu_newimage2: -*-utopia-bold-r-*-*-70-*-*-*-*-*-*-*

So, the question is: what is the convention for font names?

Regards, Andrei

Sven Neumann
2005-06-06 00:37:05 UTC (over 19 years ago)

Gimp server startup

Hi,

Andrei Simion writes:

Regarding the fonts, where I can find the new font names? I finally managed to get Gimp running. But, when I got a script running I got this:
Illegal default font description for perl_fu_newimage2: -*-utopia-bold-r-*-*-70-*-*-*-*-*-*-*

So, the question is: what is the convention for font names?

Have a look at the Fonts dialog. "Utopia Bold" should do the trick.

Sven

Andrei Simion
2005-06-07 04:07:47 UTC (over 19 years ago)

Gimp server startup

Hi Irek,

Irek S?onina wrote:

Andrei Simion wrote:

Irek S?onina wrote:

/usr/bin/gimp -c -i -s -b '(plug-in-script-fu-server 1 10008 \"/tmp/gimpserverlog\")' '(gimp-quit 1)' 1>/tmp/gimprunlog 2>/tmp/gimperrlog &

Maybe try --display :1.0 -c -s, without no-interface.

Thanks Irek, I'll try your command. The thing is that the 1.3 version of gimp worked just fine with my command. To clear the things out: are you connecting to the Gimp server through some kind of interface or you work with the Gimp in the graphic mode?

I am connecting to a server with python script by Tjabo Kloppenburg sending to a server my script-fu, all without interface and without Xvfb. If you want a script just tell.

Yes. Please send me that script on my private address.

Thanks, Andrei