In article <zcWdnQBnP4D3HdnVnZ2dnUVZ_uqdnZ2d@[EMAIL PROTECTED]
>,
Ignoramus27711 <ignoramus27711@[EMAIL PROTECTED]
> wrote:
>On 2008-06-02, John DuBois <spcecdt@[EMAIL PROTECTED]
> wrote:
>> 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.
>
>except gimp-remote does not seem to tell you when gimp is done with
>the image.
That's why I'd have the shell loop do a read, and hit return (in the
terminal
window exposed by closing the image window) to tell gimp-remote to push
the
next image open. That gets it down to ^W to close the current image
window,
and return to open the next, which is pretty good, and with a bit more
work it
could have the ability to back up to the previous image or generally to go
to a
different point in the image list as in xv.
John
--
John DuBois spcecdt@[EMAIL PROTECTED]
KC6QKZ/AE
http://www.armory.com/~spcecdt/


|
15 Posts in Topic:
|
Ignoramus23731 <ignora |
2008-05-30 11:26:00 |
|
Joost Diepenmaat <joos |
2008-05-30 19:06:57 |
|
Michael Soibelman <in- |
2008-05-30 10:21:52 |
|
Ignoramus23731 <ignora |
2008-05-30 12:33:59 |
|
Ignoramus23731 <ignora |
2008-05-30 12:29:45 |
|
Michael Soibelman <in- |
2008-05-30 10:34:28 |
|
spcecdt@[EMAIL PROTECTED] |
2008-05-31 18:37:05 |
|
Ignoramus27711 <ignora |
2008-06-02 08:16:34 |
|
Michael Soibelman <in- |
2008-06-02 08:54:36 |
|
spcecdt@[EMAIL PROTECTED] |
2008-06-02 17:32:26 |
|
Ignoramus27711 <ignora |
2008-06-02 18:21:14 |
|
spcecdt@[EMAIL PROTECTED] |
2008-06-03 22:37:35 |
|
David Hodson <hodsond@ |
2008-06-03 14:27:19 |
|
floyd@[EMAIL PROTECTED]
|
2008-05-31 20:00:47 |
|
spcecdt@[EMAIL PROTECTED] |
2008-06-02 16:59:18 |
|