SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If it wouldn't be a hassle, would it be possible to add
to the emacs.SlackBuild script? During a rare moment of lucidity, I thought it might be a smart idea to fire up an emacs daemon in XFCE4, much like the Thunar daemon, then invoke emacsclient whenever I want to play with a text file (C, Perl, etc.). Taken by surprise, this scheme was baffled with the following error message:
Warning: due to a long standing Gtk+ bug http://bugzilla.gnome.org/show_bug.cgi?id=85715
Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.
Sew! I got the Slackware Current source and and script files, dropped the configuration option into emacs.SlackBuilds, and almost forgot to change the version number so it wouldn't get deleted during an upgrade. I learned that the upgradepkg script doesn't compare version numbers or dates for files in /var/adm/packages. Suffering from congenital indolence, as I oftentimes do (born lazy), I rsync'd the fresh packages then `upgradepkg */*.txz` from the slackware64 directory. Next time, I'll diff the ChangeLog and upgrade only those new packages. The lazy way upgraded the new package with the old one, thus hosing my efforts to make that GTK+ bug go away (the bug was opened in 2002, then recently reopened, but no entries after 2010).
It's really not a big deal, so if you don't want to change things, that's ok with me.
Thank you very much for your help! Color me emacs noob. Much like the Wordperfect/MsWord issue of the mid-eighties, although all those command keystrokes make things quicker, I find it a daunting task to learn them. I only stumbled on emacs in XFCE4 as an alternative to vim because recent changes to gvim invoke some kind of visual editor mode when you try to highlight-copy-paste. I can live with compiling a local copy that with that x-toolkit config option. I just add it to the existing build script, so no worries.
I appreciate that you hunted down that solution for me!