Live data from Hacker News

GIMP 2.9.6 Released

gimp.org

81–87 of 87 posts

Re: GIMP 2.9.6 Released

#81
post #29

Earlier quoted context omitted.

Not sure where this is stored on Mac, but on Windows, clear the fontconfig directory in the AppData folder.

That's not really likely to help. The main issue appears to be that since fontconfig (a lib used by GIMP) is only "native" to Linux, for it to know about the TTF files, it has to scan them all and build it's cache at startup. For people with hundreds of fonts installed it can be a real PITA. I avoid it by being careful to not exit GIMP entirely (simply closing all the editing windows) until I am sure I won't need it…

The fontconfig cache is created on all platforms - it's just that this step is usually done when installing the system or adding new fonts from the package manager for your average Linux distro. Granted, it also works much faster there in general.

Adding a few new fonts for a specific project does not cause long delays on any platform.

A compounding issue was that file locking issues prevented successful cache updates on the Windows platforms until recent versions of fontconfig, this lead to a long startup time on every start.

Re: GIMP 2.9.6 Released

#82
post #79

Earlier quoted context omitted.

That's not really likely to help. The main issue appears to be that since fontconfig (a lib used by GIMP) is only "native" to Linux, for it to know about the TTF files, it has to scan them all and build it's cache at startup. For people with hundreds of fonts installed it can be a real PITA. I avoid it by being careful to not exit GIMP entirely (simply closing all the editing windows) until I am sure I won't need it…

It fixed the font loading forever for me on Windows.

Yeah, you most likely got rid of an existing cache, which couldn't be updated due to file locking. That issue is fixed in recent versions of the fontconfig library.

A fairly current one is shipped with the 2.9.6 installer, so many of the infamous issues should be gone.

Re: GIMP 2.9.6 Released

#83
post #62

Earlier quoted context omitted.

> the UI does not seem like it's improved at all. I've always disliked the large widgets (very tall buttons, sliders, etc.). Every now and then I look at some screenshots from the newest GIMP version and there's no indication they're going to change.

You could use a compact Gtk theme to get round this.

But make sure that they don't make sliders too small - you'll lose the ability to do either fine relative or coarse absolute adjustments by dragging their lower or upper half.

Re: GIMP 2.9.6 Released

#85

I've been very impressed with Gimp lately - there was a time that it was clunky and crashy, Windows builds were difficult to find, and usually out of date, and I often felt like I was only persevering with it on principle. In recent years though, it's been wholly solid. Was there a change in project leadership, or something - maybe just a new development workflow? I've known plenty of seemingly-moribund projects spri…

The issues with finding builds for Microsoft Windows platforms was what got me into GIMP development. Not for the releases, because those usually came about in a matter of days, but daily builds (or sometimes hourly) which tracked development exactly.

Re: GIMP 2.9.6 Released

#86
post #46

Earlier quoted context omitted.

>It proably works 99% of the time but that 1% will be right before an important deadline or something. Are you a terrorist i loved to make this joke and it hurts me that you're downvoting me friends

I downvoted nothing. I literally don't understand your comment and ignored it until I posted this.

I upvoted you because you were needlessly sincere. Thanks.

Re: GIMP 2.9.6 Released

#87

Earlier quoted context omitted.

I think you need to look up the meaning of "de facto", since its presence in GP's comment renders your entire complaint moot.

de facto and standard are basically opposites. Except when standard is used as a synonym for "the way things are due to some hegemony or similar situation". My complaint is basically: fuck off with the Adobe in a thread about Gimp. If you think the Adobe program is better or must work with every possible instance of its files, or you just feel good to use a de facto standard, go use the Adobe program. Gimp is its own…

So they're opposites, except in this exact situation? Cool.

> My complaint is basically: fuck off with the Adobe in a thread about Gimp

OK, sure, but maybe you should have A) said something resembling that in the first place instead of attempting some inane linguistic argument, and B) replied to the person who introduced the comparison rather than the one who had a pretty salient response to that.

Post reply on HN