![]() (Not with Jumpcut, though.) I can, however select the text and drag it into other applications (or drag it into one and copy from there into the clipboard). Trying to copy from Pidgin crashes it, if you’re running Quicksilver’s Clipboard history module, apparently.Copying is a bit strange - I use Command-C in the other app to copy, and Ctrl-V in Pidgin to paste.Pidgin crashes when I try to drag-and-drop buddies into contacts.There is a way to integrate Pidgin with an OSX menubar.Some exotic unicode characters aren’t displayed properly.(I also have gtk-key-theme-name = "Emacs" there.) Now you can just run Pidgin directly (as ~/.local/bin/pidgin), and it works fine! It even has the tray icon! You might want jhbuild buildone dbus and jhbuild buildone dbus-glib before doing configure etc.] Make sure that works from within jhbuild shell (even if it works in your shell). [Extra information for D-Bus: If you have D-Bus through Fink and want to use it, note that configure uses pkg-config -libs "dbus-1 >= 0.35 dbus-glib-1 >= 0.35"įor checking for D-Bus. Of course, the “–prefix” is optional it will install Pidgin in /usr/local/bin otherwise. configure -prefix=$HOME/.local -without-x -enable-gtkstatusicon -disable-gestures Get the Pidgin source, and get the patch from this ticket, and compile Pidgin with Wow, GTK on the Mac, natively… thanks, folks who brought us Gtk+ for Mac OS X! To test this, try the following:Īll should work. You should now have “GTK+ Mac OS X” installed. In my case, everything went fine (except for one minor error, where I picked “ignore error and continue” from the options it gave). I suspect I built a couple of modules more than once feel free to remove meta-gtk-osx-core from the second build command, for example. Of course, most of that is redundant, but I had disk space to spare, and pygtk to try out. Jhbuild build meta-gtk-osx-core meta-gtk-osx-python meta-gtk-osx-themes gossip Then, make sure ~/bin is in your $PATH, and: It is possible to change this, but I remember having run into trouble during an earlier attempt doing so, so I didn’t touch anything this time.ĭownload this file, and save it as ~/.jhbuildrc. Note that this installs jhbuild in ~/bin. Old instructions follow, mainly because I’m too lazy to delete them, but also in case someone does not want to use MacPorts or something: If you plan to script Pidgin using D-Bus, you could also do, before Step 1: sudo port install dbus-python25 If you would like to help debug them, checkout the project from svn- svn checkout I think-and/or file bugs/patches at the bug tracker.) ( Note: The pidgin-macosx from Sourceforge may be at a older version than the MacPorts version. Step 1: sudo port install pidgin +quartz +no_x11 Step 0: Install MacPorts, if you haven’t got it already. If you’re using MacPorts: For something which has had fewer changes from the original Pidgin, you can install it through MacPorts: dmg file from pidgin-macosx on Sourceforge, and double click on the Pidgin application. ![]() One-step simple way: All you have to do is download the. And maybe I can take a little credit for small improvements here and there, and nagging people into making certain changes :-)) (And of course, the Pidgin developers for writing Pidgin, and Richard Hult from Imendio AB for GTK+OSX. ![]() Installing Pidgin on Mac OS X is now as simple as installing any other Mac OS X application, thanks to a train of effort from many people, starting with Anders Hasselqvist (“nevil”) for writing the patch with the gtkstatusicon implementation, Thomas Reifferscheid (reiffert) for including it on MacPorts, and finally Albert Zeyer for building it with Xcode and the GTK framework and making a. This is very simple to do and requires only one step, described below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |