Re: Quick cropping with GIMP, like in XV

In article <0JU0k.2854$uE5.1152@[EMAIL PROTECTED]
>,
Michael Soibelman  <in-the@[EMAIL PROTECTED]
> wrote:
>Ignoramus27711 wrote:
>> On 2008-05-31, John DuBois <spcecdt@[EMAIL PROTECTED]
> wrote:
>>> The last im****tant xv characteristic that I haven't yet found a way
>>> to emulate is the behavior of only opening one
>>> command-line-specified file at a time, and easily (from the
>>> keyboard) going on to the next image when I'm done with the current
>>> one.  Is there a way of making the gimp behave this way?  That is -
>>> I want to specify the files to operate on on the command line, and I
>>> do *not* want them all opened initially; I may be perusing, and
>>> selectively editing, several hundred images in one round (all
>>> selected according to some criteria on the command line).  In xv,
>>> it's a matter of "hit space to open the next image in place of the
>>> current one"; the closer to that I can get, the better...
>> 
>> You just need a simple shell script
>> 
>> for i in *.jpg; do
>>   gimp $i
>> done
>> 
>> the little overhead here is in starting a new instance of gimp every
>> time.
>> 
>
>Sorry if I'm wrong about this but I'm not a very good programmer !!  Just
>BASIC !1  Seems to me that if you changed this 'gimp $i'  to 'gimp-remote
>$i' you would save a lot of overhead ??  This leaves just one instance of
>Gimp running but opens up each image in its' own window...

Thanks, this is a useful idea.  I don't want to start a new instance of
gimp
for each image, with the startup overhead, losing the history that allows
me to
rerun the last filter, etc.  gimp-remote avoids that, and if I use a shell
loop
that includes a 'read', going on to the next image become a matter of
closing
the image window and then hitting return to tell gimp-remote to push the
next
image open.

	John
-- 
John DuBois  spcecdt@[EMAIL PROTECTED]
  KC6QKZ/AE 
http://www.armory.com/~spcecdt/