gedit 3.20.1 for Windows

It wasn’t without time but I am finally proud to say that we have a new version of gedit for Windows. This was a long road getting GTK+ 3 and all the dependencies properly working and there are a lot of people behind this, so thanks to all of them for the hard work.

To download the new installer follow up this link.

This entry was posted in Uncategorized. Bookmark the permalink.

14 Responses to gedit 3.20.1 for Windows

  1. Pingback: gitg 3.20.0 for Windows | Nacho's Blog

  2. Remco says:

    Awesome! One of the essential tools for Windows. (There ought to be a GNOME Survival Kit for Windows)

    The download links on the Gedit website are a bit outdated:

  3. Eno says:

    Thanks for the update.

    Where should I report issues?

    Using gedit 3.20.1 on Windows 7 Pro 64bit crashes it for me with the following popup:
    gedit.exe has stopped working

    Windows can check online for a soultion to the problem
    * Check online for a solution and close the program
    * Close the program

    And the following information on the crash:

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: gedit.exe
    Application Version:
    Application Timestamp: a040a028
    Fault Module Name: libgtk-3-0.dll
    Fault Module Version:
    Fault Module Timestamp: 00000000
    Exception Code: c0000005
    Exception Offset: 00000000002d92b7
    OS Version: 6.1.7601.
    Locale ID: 3081
    Additional Information 1: 883c
    Additional Information 2: 883cdba1362452917d484677364aadee
    Additional Information 3: 036b
    Additional Information 4: 036b85daaf4d9aac5e3f51bb7092e644

    Read our privacy statement online:

    If the online privacy statement is not available, please read our privacy statement offline:

  4. Simeon says:

    I frequently checked for Windows builds but never saw a new release there. I thought gedit abandoned windows.

  5. Stu says:

    Awesome work, I think it’s really important Gedit, Gtk etc work on one of the most widely used platforms on the planet, keep up the good work 🙂

    Look forward to Nautilus working on Windows one day(!)

  6. Stu says:

    It even works in Wine ! – In fact, it fits in so well with my desktop, that you will have to take my word that it is not native Gedit

  7. Felix Schwarz says:

    What does that means for GTK3 on Windows? Are there going to be official binary releases again? That would be awesome…

    • Ignacio Casal Quinteiro says:

      Well, msys2 is providing gtk3 binaries updated to the last stable release see one of my previous posts about this. For msvc you have the gtk-win32 pointed out also on another previous post.

  8. Peugny says:

    I come late after the post of 1st August 2014. My aim is install manually JModelica under Windows 10 and I need python package wxPython (wxWidgets) thus I came into your post ‘building your gtk application’ and the first thing I tried was to build your gedit under msys2. After editing your PKGBUID (see below) I get finally this error:

    make[3]: Leaving directory ‘/home/frede/build_gedit/src/build-x86_64-w64-mingw32/help’
    Makefile:492: recipe for target ‘install-am’ failed
    make[2]: *** [install-am] Error 2
    make[2]: Leaving directory ‘/home/frede/build_gedit/src/build-x86_64-w64-mingw32/help’
    Makefile:3784: recipe for target ‘install-recursive’ failed
    make[1]: *** [install-recursive] Error 1
    make[1]: Leaving directory ‘/home/frede/build_gedit/src/build-x86_64-w64-mingw32’
    Makefile:4084: recipe for target ‘install’ failed
    make: *** [install] Error 2
    ==> ERROR: A failure occurred in package().

    # Maintainer: Alexey Pavlov
    # frederic: here MINGW_PACKAGE_PREFIX defined as empty
    pkgdesc=”A text editor for GNOME (mingw-w64)”
    options=(‘strip’ ‘staticlibs’ ‘!buildflags’)
    #frederic: here url source replaced by directory (by hand)
    prepare() {
    cd “${srcdir}”/${_realname}-${pkgver}
    #autopoint –force
    #AUTOPOINT=’intltoolize –automake –copy’ autoreconf -f -i

    build() {
    [[ -d build-${MINGW_CHOST} ]] && rm -rf build-${MINGW_CHOST}
    mkdir -p build-${MINGW_CHOST}
    cd build-${MINGW_CHOST}

    export PYTHON=${MINGW_PREFIX}/bin/python3
    ../${_realname}-${pkgver}/configure –host=${MINGW_CHOST} –target=${MINGW_CHOST} –build=${MINGW_CHOST} –prefix=${MINGW_PREFIX} –libexecdir=${MINGW_PREFIX}/lib –disable-updater –disable-schemas-compile –enable-python –disable-spell

    package() {
    cd “${srcdir}/build-${MINGW_CHOST}”
    # frederic: follows instruction ‘always remove Win32 executables if the intented pkg is a library’
    #rm “$pkgdir”/usr/${_arch}/bin/*.exe
    make DESTDIR=${pkgdir} install

    install -Dm644 “${srcdir}/${_realname}-${pkgver}/COPYING” “${pkgdir}${MINGW_PREFIX}/share/licenses/${_realname}/COPYING”

  9. devon says:

    Thank you – the Windows builds are appreciated (using it on Win7 64-bit). It looks good but some things are buggy to the point where I can only use it for the most simple editing.

    The Python console keeps hiding itself. The only way I can get it back is to disable all the plugins (I’m using the defaults), restart, and then re-enable them. Afterwards – if Gedit is closed the Python console (and bottom panel) completely disappear. (even from the View menu). I’ve got to repeat the process (sometimes multiple times) before I can get it back again..

    Some plugins appear to be completely missing. externaltools is the biggest one – I might be able to work around the missing panel issue if I could at least launch the console or external scripts but I can’t. 🙁

    Is there any way to get more detailed error information? For example I try to enable the commander plugin but it doesn’t work. (just displays the red X but doesn’t tell me what went wrong)

    Gedit stores really basic user preferences in the Windows registry. I guess it works but wouldn’t it be better to store the user preferences in the user’s profile folder instead (where we put our plugins, styles, and other things we customize).

    Is there any chance of seeing a Windows 32-bit build or is 3.x.x 64-bit only?

    • Ignacio Casal Quinteiro says:

      Hey Devon,

      for now I made the 64bit because of not having enough time.
      The upcoming update will probably fix some of the problems. About the python console, I haven’t tried to use it on windows to be honest. To get some error for the commander plugin try to launch gedit from a command line and see if something is printed.

      About external tools. This plugin is linux only, somebody would have to put some time to make it work on windows as well. Another plugin that needs some more love on windows is the git one which does not currently work due to the cairo python bindings.

Leave a Reply

Your email address will not be published. Required fields are marked *