On Thu, Aug 1, 2013 at 9:19 AM, Michael Schumacher wrote:
>> Enter it as a request for enhancement (RFE) in bugzilla, and then post
>> to the developer list about it
>
> The other way round, please - first discuss it on the list, and then enter an
> enhancement request into Bugzilla.
But not on
> Von: "Liam R E Quin"
> Enter it as a request for enhancement (RFE) in bugzilla, and then post
> to the developer list about it
The other way round, please - first discuss it on the list, and then enter an
enhancement request into Bugzilla.
--
Regards,
Michael
__
On Thu, Aug 1, 2013 at 6:04 PM, Liam R E Quin wrote:
>> I did suggest that the export filename/options should be recorded as
>> part of the XCF project data -- what say you to that?
>
> I think it would be a good idea
It's what Inkscape does with its own SVG files. Indeed, very useful.
> and pro
On Thu, 2013-08-01 at 06:35 -0700, Richard Gitschlag wrote:
>
> You might have overlooked one minor (but critical) element about my
> workflow: I generally only do one image export per GIMP session. So
> EVERY export is "the first time"
Yes, that's true.
> I did suggest that the export fi
> Subject: Re: [Gimp-user] SOLVED: export vs. save menu in gimp2.8 - simple and
> lasting solution
> From: l...@holoweb.net
> To: strata_ran...@hotmail.com
> CC: jvrom...@squirrel.nl; gimp-user-list@gnome.org
> Date: Thu, 1 Aug 2013 09:14:28 -0400
>
> as with control-s a
On Mon, 2013-07-29 at 08:49 -0700, Richard Gitschlag wrote:
> Y'know, I cannot think of any situation in my personal workflow where Ctrl+E
> versus Ctrl+Shift+E creates a tangible difference in behavior.
as with control-s and control-S, there's no difference the first time,
only on subsequent ti
I see there is still some effort in dragging me into your narcissistic
bickering.
You guys use the chroot howto I supplied or go with the new design.
End of story.
Dirk
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List
El 29/07/2013 20:27, "Alexandre Prokoudine"
escribió:
> What, the amazing
> http://lists.debian.org/debian-user/2013/04/msg00265.html thread is
> back? Oh, Dirk :)
Looking at that link maybe Microsoft didn't hire that people. Probably they
just exported them from their staff to save resources (so
On Mon, Jul 29, 2013 at 6:29 AM, Stephen Allen wrote:
> It's a mistake only in the eyes of a vocal few, who never have used GIMP
> in a professional work-flow. It's not a huge change, so either adapt,
> change to a simpler editor, or get used to it. Staying with one version
> forever pretty much i
Richard Gitschlag writes:
>> There's much to be said for the new behaviour. It would be better if
>> Ctrl-E just used the filename and properties from the imported file. The
>> first time it may even show a "File exists, overwrite" dialog.
>> Currently, Ctrl-E and Shift-Ctrl-E open the same expor
On Mon, Jul 29, 2013 at 01:55:16AM +0200, Dirk wrote:
> On 07/29/13 00:29, Bob Long wrote:
> >Paul Cartwright wrote,
> >
> >>On 07/28/2013 02:58 PM, Kasim Ahmic wrote:
> >>>Anyway, if the save vs. export thing causes such a problem, then people
> >>>could just install a plugin that removes the new
> From: jvrom...@squirrel.nl
> To: gimp-user-list@gnome.org
> Date: Mon, 29 Jul 2013 08:21:40 +0200
> Subject: Re: [Gimp-user] SOLVED: export vs. save menu in gimp2.8 - simple
> and lasting solution
>
> Dirk writes:
>
> There's much to be said for the new
On 07/28/2013 09:42 PM, Bob Long wrote:
>> I use command keys like CTRL-S, but not sure how to re-define it to
>> > save-export-clean..
> See if Edit|Keyboard Shortcuts helps!
thank you!
--
Paul Cartwright
___
gimp-user-list mailing list
List address:
Dirk writes:
> The whole situation boils down to the lack of character that is
> necessary for admitting a mistake and reversing this change in the
> workflow.
There's much to be said for the new behaviour. It would be better if
Ctrl-E just used the filename and properties from the imported file
On Mon, Jul 29, 2013 at 3:55 AM, Dirk wrote:
> Needless to say I /still/ clicked on "Save as..." or "Save".
Just use Ctrl+S. It's handy.
> The whole situation boils down to the lack of character that is necessary
> for admitting a mistake and reversing this change in the workflow.
You won't get
Paul Cartwright wrote,
> On 07/28/2013 08:31 PM, Ofnuts wrote:
>> On 07/29/2013 01:55 AM, Dirk wrote:
>>>
>>> Needless to say I /still/ clicked on "Save as..." or "Save".
>>>
>>
>> You *click*? Never learned Ctrl-S or Ctrl-E? (and you can probably
>> redefine the Ctrl-S shortcut to be 'file-export
On 07/28/2013 08:31 PM, Ofnuts wrote:
> On 07/29/2013 01:55 AM, Dirk wrote:
>>
>> Needless to say I /still/ clicked on "Save as..." or "Save".
>>
>
> You *click*? Never learned Ctrl-S or Ctrl-E? (and you can probably
> redefine the Ctrl-S shortcut to be 'file-export')
I use command keys like CTRL-
* Ofnuts [07-28-13 20:32]:
> On 07/29/2013 01:55 AM, Dirk wrote:
> >
> >Needless to say I /still/ clicked on "Save as..." or "Save".
> >
>
> You *click*? Never learned Ctrl-S or Ctrl-E? (and you can probably redefine
> the Ctrl-S shortcut to be 'file-export')
Undoubtedly a windoz uzer. Some of
On 07/29/2013 01:55 AM, Dirk wrote:
Needless to say I /still/ clicked on "Save as..." or "Save".
You *click*? Never learned Ctrl-S or Ctrl-E? (and you can probably
redefine the Ctrl-S shortcut to be 'file-export')
___
gimp-user-list mailing list
L
On 07/29/13 00:29, Bob Long wrote:
Paul Cartwright wrote,
On 07/28/2013 02:58 PM, Kasim Ahmic wrote:
Anyway, if the save vs. export thing causes such a problem, then people could
just install a plugin that removes the new functionality and restores the old
one. That way, your workflow isn't
Paul Cartwright wrote,
> On 07/28/2013 02:58 PM, Kasim Ahmic wrote:
>> Anyway, if the save vs. export thing causes such a problem, then people
>> could just install a plugin that removes the new functionality and restores
>> the old one. That way, your workflow isn't affected and you get all the
On 07/28/2013 02:58 PM, Kasim Ahmic wrote:
> Anyway, if the save vs. export thing causes such a problem, then people could
> just install a plugin that removes the new functionality and restores the old
> one. That way, your workflow isn't affected and you get all the new features
> of 2.8.
go a
Ahh I see. So would this allow the user to have two version of GIMP installed?
Anyway, if the save vs. export thing causes such a problem, then people could
just install a plugin that removes the new functionality and restores the old
one. That way, your workflow isn't affected and you get all t
https://en.wikipedia.org/wiki/Chroot
On 07/28/13 20:35, Kasim Ahmic wrote:
So what exactly does this do? Does it lock GIMP 2.6 onto your machine and not
allow you to upgrade to 2.8, or what?
Sorry, I'm mainly a Windows user :P
Sent from my iPod
On Jul 27, 2013, at 6:10 PM, Dirk wrote:
Hel
chroot changes the root directory for the process (in this case Gimp)
from "/" to another path.
debootstrap installs a minimal linux and Gimp 2.6 into that new root
path. So you are running a distribution inside a distribution. But it is
not like a VM because no hardware is emulated.
The dis
On Sun, Jul 28, 2013 at 10:35 PM, Kasim Ahmic wrote:
> So what exactly does this do? Does it lock GIMP 2.6 onto your machine and not
> allow you to upgrade to 2.8, or what?
Chroot allows running an operating system within an operating system,
in an isolated environment. Typically this is done for
So what exactly does this do? Does it lock GIMP 2.6 onto your machine and not
allow you to upgrade to 2.8, or what?
Sorry, I'm mainly a Windows user :P
Sent from my iPod
On Jul 27, 2013, at 6:10 PM, Dirk wrote:
> Hello,
>
> it has now been months that Gimp developers seem to have decided tha
Hello,
it has now been months that Gimp developers seem to have decided that
their "product vision" in Gimp2.8 (debian/unstable) is more relevant
than the workflow of their users.
People who use Gimp *a lot* keep clicking "Save as" instead of "Export"
because that is what they're used to. Be
28 matches
Mail list logo
